iwl4965 crashes randomly

[Michael Kiermaier]

On my Lenovo X61s, WLAN randomly stops working, typically after a few hours of running time. I don't know any remedy but to reboot.
This behavior started maybe 2 or 3 months ago. My maching is usually kept up to date, so the problem might be caused by some kernel update at that time.

The relevant part in dmesg (attached) starts with
[ 5812.412141] iwl4965 0000:03:00.0: Error sending C_POWER_TBL: time out after 500ms.
[ 5812.412156] iwl4965 0000:03:00.0: set power fail, ret = -110
[ 5813.424145] iwl4965 0000:03:00.0: Error sending C_ADD_STA: time out after 500ms.
[ 5813.424162] wls3: HW problem - can not stop rx aggregation for **:**:**:**:**:** tid 0
[ 5813.924092] iwl4965 0000:03:00.0: Error sending C_ADD_STA: time out after 500ms.
[ 5813.924107] wls3: HW problem - can not stop rx aggregation for **:**:**:**:**:** tid 5
[ 5814.052099] iwl4965 0000:03:00.0: Queue 4 stuck for 2500 ms.
[ 5814.052124] iwl4965 0000:03:00.0: On demand firmware reload
[ 5814.424142] iwl4965 0000:03:00.0: Error sending C_ADD_STA: time out after 500ms.
[ 5814.424168] wls3: HW problem - can not stop rx aggregation for **:**:**:**:**:** tid 6
[ 5814.424421] iwl4965 0000:03:00.0: Master Disable Timed Out, 100 usec
[ 5814.424468] ieee80211 phy0: Hardware restart was requested
[ 5814.448160] iwl4965 0000:03:00.0: idx 0 not used in uCode key table.
[ 5814.948182] iwl4965 0000:03:00.0: Error sending C_ADD_STA: time out after 500ms.
[ 5814.948201] wls3: failed to remove key (0, **:**:**:**:**:**) from hardware (-110)
[ 5818.964158] iwl4965 0000:03:00.0: START_ALIVE timeout after 4000ms.

WORKAROUND: Turn off WiFi power management:
sudo iw dev X set power_save off

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-38-generic 4.4.0-38.57
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mki 2093 F.... pulseaudio
CurrentDesktop: XFCE
Date: Tue Sep 27 13:29:36 2016
HibernationDevice: RESUME=/dev/mapper/vgubuntu-swap
InstallationDate: Installed on 2016-06-05 (113 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3)
MachineType: LENOVO 76693JG
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic root=/dev/mapper/vgubuntu-system ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-38-generic N/A
 linux-backports-modules-4.4.0-38-generic N/A
 linux-firmware 1.157.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7NETC2WW (2.22 )
dmi.board.name: 76693JG
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:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn76693JG:pvrThinkPadX61s:rvnLENOVO:rn76693JG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 76693JG
dmi.product.version: ThinkPad X61s
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Michael Kiermaier, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

It is most helpful that after testing of the latest upstream kernel is complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test the latest mainline kernel as it becomes available.

Thank you for your help.

[Keri Alleyne (keri.alleyne)]

I believe that this bug also affects me. I seem to be experiencing random WLAN failures on a Panasonic CF-52 laptop. The WLAN usually recovers automatically but not always. There appear to be multiple iwl4965 error messages in dmesg similar to those observed by the original poster. I can include these details if necessary.

Thanks.

[Michael Kiermaier (michael-kiermaier)]

@Christopher M. Penalver:

The newest kernel 4.9-rc5-generic gives a kernel panic at boot.
"stack guard page was hit at ..."

What to do now?

[penalvch (penalvch)]

Keri Alleyne, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Michael Kiermaier (michael-kiermaier)]

Christopher M. Penalver, I had tested 4.9-r5, which gives a kernel panic at boot. Now I've tested the latest mainline kernel 4.9. Kernel panic at boot, too.
How should I proceed?

[Michael Kiermaier (michael-kiermaier)]

Christopher M. Penalver, I continued testing:
4.8.15-040815-generic gives a kernel panic at boot, too.
4.7.10-040710-generic boots just fine, but the original Problem is still there (WLAN not working after some while).

[penalvch (penalvch)]

Michael Kiermaier, to advise, 4.9-rc5 isn't 4.9.

[Michael Kiermaier (michael-kiermaier)]

Christopher M. Penalver, as written, I've tested 4.9-rc5 a few weeks ago **and 4.9 today**.

[penalvch (penalvch)]

Michael Kiermaier, to clarify:
1) If you boot into a Ubuntu kernel from 3 months ago when this problem didn't happen, is it still reproducible? Please advise which version specifically.
2) Does disabling power management provide a WORKAROUND via:
sudo iw dev X set power_save off

Where X is the NIC name found via:
iwconfig

[Michael Kiermaier (michael-kiermaier)]

Christopher M. Penalver,
thank you.
1) will need some time as I don't remember when exactly the problem has started.

I see that you added the tag "kernel-bug-exists-upstream-4.9". To make sure: I didn't experience the reported problem on 4.9. Simply because I cannot boot into it due to a kernel panic at boot time.
No idea if that kernel is related to the original problem or not.

However, I reproduced the reported problem on 4.7.10-040710-generic.

[Launchpad Janitor (janitor)]

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

[Michael Kiermaier (michael-kiermaier)]

Christopher M. Penalver,

on 2)
The problem does not occur after
sudo iw dev X set power_save off

What's the best way to make this permament?

[penalvch (penalvch)]

Michael Kiermaier, the way to make the issue go away permanent is to determine why disabling power management is necessary in the first place.

Hence, to keep this relevant to upstream, one would want to periodically check for, and test the latest mainline kernel (now 4.10) as it is released.

Could you please advise?