Wireless is disabled by rfkill after suspend with linux-image-generic-lts-wily

Bug #1518259 reported by Andrei Borzenkov
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I am running Ubunutu 14.04 on Dell Latitude E5450; Ubuntu came preinstalled on this notebook. After installing kernel linux-image-4.2.0-18-generic wireless is not available after resuming from suspend to RAM; in logs I see

Nov 20 13:04:46 bor-Latitude-E5450 NetworkManager[1389]: <info> WiFi now disabled by radio killswitch

This problem did not exist with original kernel linux-image-3.13.0-xx from 14.04 and updates.

Probably related - original kernel is using iwlwifi driver

Package: iwlwifi-3.16.2-dkms
Status: install ok installed
Priority: optional
Section: misc
Installed-Size: 65,6 MB
Maintainer: Ubuntu Developers <email address hidden>
Version: 1.0
Depends: dkms (>= 1.95)
Original-Maintainer: Dynamic Kernel Modules Support Team <email address hidden>

This driver does not compile for kernel 4.2.

bor@bor-Latitude-E5450:~$ lsb_release -rd
Description: Ubuntu 14.04.3 LTS
Release: 14.04
---
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bor 1910 F.... pulseaudio
 /dev/snd/pcmC1D0p: bor 1910 F...m pulseaudio
 /dev/snd/controlC1: bor 1910 F.... pulseaudio
CurrentDesktop: Unity
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=df2037e2-aa56-4079-9f35-49d94d595d93
InstallationDate: Installed on 2015-07-02 (141 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25
MachineType: Dell Inc. Latitude E5450
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic root=UUID=d06b07a3-04bf-46e1-8cae-5f2592c69192 ro quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 video.use_native_backlight=1 crashkernel=384M-:128M vt.handoff=7
ProcVersionSignature: Ubuntu 4.2.0-18.22~14.04.1-generic 4.2.3
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-18-generic N/A
 linux-backports-modules-4.2.0-18-generic N/A
 linux-firmware 1.127.18
Tags: trusty
Uname: Linux 4.2.0-18-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/19/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 06J17N
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA07:bd05/19/2015:svnDellInc.:pnLatitudeE5450:pvr01:rvnDellInc.:rn06J17N:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5450
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote :

Probably kernel regression; here is similar thread for the same hardware:
https://bbs.archlinux.org/viewtopic.php?id=203404

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1518259

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: trusty
Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : BootDmesg.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : CRDA.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : IwConfig.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : Lspci.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : Lsusb.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : ProcEnviron.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : ProcModules.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : PulseList.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : RfKill.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : UdevDb.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : UdevLog.txt

apport information

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.3 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote :

Yes, the same issue in
linux-image-4.3.0-040300-generic 4.3.0-040300.201511020949

Additional note - the problem happens every second i.e.

boot - suspend - resume - no WiFi/Bluetooth
enable via rfkill - suspend - resume - OK
suspend - resume - no WiFi/Bluetooth
etc

Also not only wireless but also Bluetooth gets disabled

bor@bor-Latitude-E5450:~$ rfkill list
0: dell-wifi: Wireless LAN
 Soft blocked: yes
 Hard blocked: no
1: dell-bluetooth: Bluetooth
 Soft blocked: yes
 Hard blocked: no
2: phy0: Wireless LAN
 Soft blocked: yes
 Hard blocked: yes
8: hci0: Bluetooth
 Soft blocked: yes
 Hard blocked: no

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote :

The bug seems to be in (or at least caused by) dell-rbtn driver. Blacklisting this driver "fixes" it.

Revision history for this message
Andrei Borzenkov (arvidjaar-s) wrote :

Patch https://lkml.org/lkml/2015/11/21/57 seems to fix it. I cannot reproduce the issue after applying it (on top of 4.2.0-19 from GIT).

penalvch (penalvch)
tags: added: bios-outdated-a10
Revision history for this message
penalvch (penalvch) wrote :

Andrei Borzenkov, as per http://www.dell.com/support/home/us/en/04/product-support/product/latitude-e5450-laptop/drivers an update to your computer's buggy and outdated BIOS is available (A10). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it address the issue?

If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid.

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.