Centrino Advanced-N 6205 wifi doesn't resume (hard blocked)

[Matt Zimmerman]

Every day, when I wake up my ThinkPad x220 from sleep, its wifi doesn't come back. "rfkill list" shows:

1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: yes

and dmesg shows:

[32330.371510] iwlwifi 0000:03:00.0: RF_KILL bit toggled to disable radio.

toggling the hardware kill switch has no effect. Reloading the module doesn't resolve the problem. Suspending and resuming again doesn't resolve the problem. The only way I've found to get back online is to reboot.

Oddly, I haven't been able to reproduce this by suspending and then resuming immediately. It seems to happen when the machine is left suspended for a period of time, like overnight.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-26-generic 3.2.0-26.41
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19
Uname: Linux 3.2.0-26-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mdz 2236 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf2620000 irq 52'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:14f1506e,17aa21da,00100000 HDA:80862805,80860101,00100000'
   Controls : 26
   Simple ctrls : 8
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown'
   Mixer name : 'ThinkPad EC (unknown)'
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card29.Amixer.values:
 Simple mixer control 'Console',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Fri Jul 13 10:02:50 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: LENOVO 4286CTO
ProcEnviron:
 TERM=xterm
 LC_COLLATE=C
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-26-generic root=UUID=b4f82fbf-ca0b-4df1-86f6-2c4a94b99732 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-26-generic N/A
 linux-backports-modules-3.2.0-26-generic N/A
 linux-firmware 1.79
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2012-03-14 (120 days ago)
dmi.bios.date: 05/31/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET47WW (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4286CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8DET47WW(1.17):bd05/31/2011:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4286CTO
dmi.product.version: ThinkPad X220
dmi.sys.vendor: LENOVO

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

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'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-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/v3.5-rc6-quantal/

[Matt Zimmerman (mdz)]

I have installed 3.5.0-030500rc6 and will let you know what happens the next
time I wake it up after an overnight sleep.

--
 - mdz

[Matt Zimmerman (mdz)]

Behavior is exactly the same with 3.5.0-030500rc6

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Joseph Salisbury (jsalisbury)]

Also, it would be good to know if this is a regression. If it is, we can bisect down to the commit that caused it. Was there a previous kernel that did not have this bug?

[madbiologist (me-again)]

I noticed that you have a:

Network controller [0280]: Intel Corporation Centrino Advanced-N 6205 [8086:0085] (rev 34)
 Subsystem: Intel Corporation Centrino Advanced-N 6205 AGN [8086:1311]

, so as per bug #1039856, updating to linux-firmware 1.79.1 might help.

[Matt Zimmerman (mdz)]

@madbiologist I'm now running linux-firmware 1.95 and I still see the same problem. I'm buying a new wifi card in hopes of avoiding the problem.

[Matt Zimmerman (mdz)]

Still happening on 13.04 with 3.8.0-23-generic #34-Ubuntu

[Joseph Salisbury (jsalisbury)]

@Matt Zimmerman,

Did you replace your wifi card, or is this still the original one?

Also, the v3.10-rc4 kernel is now available. It might be worth a test to see if it's fixed in mainline. The v3.10-rc4 kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc4-saucy/

Also, do you happen to know if this issue is a regression? Was there a prior release that did not exhibit this bug?

[Matt Zimmerman (mdz)]

This is still the original one.

Interestingly though, I now also have a different laptop at work which has the same wifi chip but is an entirely different model of laptop (ThinkPad X1 Carbon). It does not seem to exhibit this problem. So I suspect it has to do with the RF kill switch or the suspend/resume functionality, rather than the wifi driver itself.

It seems to be triggered whenever the laptop is in a suspend state for a long period of time (longer than overnight). If it's suspended for a few days, it will happen reliably when I wake it up. The wake up sequence is abnormal in this case: the power button LED is no longer pulsing, it doesn't wake when the lid is opened, and I have to press the power button to wake it up.

When I do, the power-on sequence is slightly different (e.g. the built-in lamp which illuminates the keyboard area briefly turns on, which usually doesn't happen during resume but does happen during cold boot).

[Joseph Salisbury (jsalisbury)]

Does either system have an encrypted home and/or swap?

It sounds like the system may be going into hibernation or other S-state. Can you reproduce this issue then attach the output from:

cat /proc/acpi/wakeup

If you dont mind, please also attach the files:
/var/log/pm-suspend.log
/var/log/syslog

[Matt Zimmerman (mdz)]

The system in question uses encrypted home with ecryptfs. I'll collect the info you requested the next time it happens. Thanks.

[penalvch (penalvch)]

Matt Zimmerman, as per http://download.lenovo.com/express/ddfm.html an update is available for your BIOS (1.38). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, 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

Thank you for your understanding.

[Matt Zimmerman (mdz)]

Indeed, there have been a lot of updates. I will update the BIOS and report back.

[Matt Zimmerman (mdz)]

It's been two weeks since I upgraded my BIOS to 1.39, and the problem has not recurred. If it happens again I will reopen. Thanks!