8086:4238 iwlwifi: Queue 11 stuck for 2000 ms

[Andreas Schildbach]

About once a day, Wifi stops working for me. The indicator still tells that I'm connected, but all connections fail. When I look at the syslog, I always see this error at the time of the failure:

Jun 7 10:07:50 darkly kernel: [69198.866204] iwlwifi 0000:03:00.0: Queue 11 stuck for 2000 ms.
Jun 7 10:07:50 darkly kernel: [69198.866212] iwlwifi 0000:03:00.0: Current read_ptr 35 write_ptr 186
Jun 7 10:07:50 darkly kernel: [69198.866216] iwlwifi 0000:03:00.0: On demand firmware reload
Jun 7 10:07:50 darkly kernel: [69198.866736] ieee80211 phy0: Hardware restart was requested
Jun 7 10:07:50 darkly kernel: [69198.866922] iwlwifi 0000:03:00.0: L1 Enabled; Disabling L0S
Jun 7 10:07:50 darkly kernel: [69198.873824] iwlwifi 0000:03:00.0: Radio type=0x0-0x3-0x1

Reconnecting or disabling and enabling wireless does not repair my connection. I have to reboot in order to use my Wifi again.

This is with precise on a Lenovo T410s, I'm pretty sure that this bug was not present in oneiric.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.39
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-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: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: aschildbach 2257 F.... pulseaudio
CRDA:
 country DE:
  (2400 - 2483 @ 40), (N/A, 20)
  (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
  (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
  (5470 - 5725 @ 40), (N/A, 26), DFS
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf2520000 irq 45'
   Mixer name : 'Intel IbexPeak HDMI'
   Components : 'HDA:14f15069,17aa21a4,00100302 HDA:80862804,17aa21b5,00100000'
   Controls : 26
   Simple ctrls : 8
Card29.Amixer.info:
 Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 6UHT32WW-1.13'
   Mixer name : 'ThinkPad EC 6UHT32WW-1.13'
   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: Thu Jun 7 10:22:24 2012
HibernationDevice: RESUME=UUID=d4396379-f5b7-488e-a24a-f11c0d609719
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
MachineType: LENOVO 29123AG
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=12513dc6-8daf-432e-b479-2fd42ad6d3d8 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-24-generic N/A
 linux-backports-modules-3.2.0-24-generic N/A
 linux-firmware 1.79
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2012-04-28 (39 days ago)
dmi.bios.date: 05/10/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6UET64WW (1.44 )
dmi.board.name: 29123AG
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:bvr6UET64WW(1.44):bd05/10/2011:svnLENOVO:pn29123AG:pvrThinkPadT410s:rvnLENOVO:rn29123AG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 29123AG
dmi.product.version: ThinkPad T410s
dmi.sys.vendor: LENOVO

[penalvch (penalvch)]

Andreas Schildbach, thank you for reporting this bug and helping make Ubuntu better. If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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'.

Please let us know your results. Thanks in advance.

[Andreas Schildbach (schildbach)]

This also happens with kernel 3.2.0-25-generic.

[luca (llucax)]

I tested it with mainline kernel 3.4.0 for precise and seems to be still happening. There are no newer kernels to test with precise though.

[penalvch (penalvch)]

luca, please do not toggle this report. If you are having a problem in Ubuntu, please file a new report by executing the following via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

[Matthias Gehre (m-gehre)]

This also happens on ubuntu's 3.2.0-27-generic.

[penalvch (penalvch)]

Matthias Gehre, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette

If you do file a new report, please feel free to subscribe me to it. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Andreas Schildbach (schildbach)]

Re-opening because this bug is still happening quite often.

[Andreas Schildbach (schildbach)]

Found this bugreport confirming the issue in Fedora as well:
https://bugzilla.redhat.com/show_bug.cgi?id=805285

[Andreas Schildbach (schildbach)]

In OpenSUSE, this bug is marked as CRITICAL:
https://bugzilla.novell.com/show_bug.cgi?id=768567

They also indicate that kernel 3.4.3 fixes the issue.

[Andreas Schildbach (schildbach)]

This also happens with linux-image-3.4.0-030400-generic 3.4.0-030400.201205210521 downloaded from http://kernel.ubuntu.com/~kernel-ppa/mainline

Did not find a build for kernel 3.4.3 unfortunately.

Did not find a way to add tag "kernel-bug-exists-upstream".

[arsenix (arsenix)]

One testimonial here. Got new router recently (TPlink tl-wr1043nd), which worked excellently with my Ultimate-N 6300 wifi card in my HP Elitebook 8540w. I was using 802.11n and rocking good speeds etc. Yesterday I got home after using the network for around 5 weeks non-stop without issue and I could not maintain a connection for more than a few seconds, getting the "Queue 11 stuck at 2000ms" and then having the wifi completely inop until unload/reload module... at which point it would work again for a few seconds and crap out again.

After fooling around, rebooting etc... I rebooted the router. Everything was back to normal. Works awesome again, 802.11n speeds etc. To clarify as well, every other computer in my house (which run a mix of OS's) were working fine before I rebooted it. GF was streaming hulu etc with no issues.

I'm not sure what this tell us... but there definitely is some interplay with the router with this issue. Let me know if more information on my setup would be useful.

[penalvch (penalvch)]

Andreas Schildbach, thank you for testing the mainline. Could you please provide the information following https://wiki.ubuntu.com/Kernel/LinuxWireless#Bug_Report_Minimum_Requirement_Information ?

[Andreas Schildbach (schildbach)]

The Wireless AP is an AVM FRITZ!Box Fon WLAN 7390 running FRITZ!OS 05.22.

My various Android devices connected to the same AP do not appear to have this problem.

Distance: about 5m
Obstructions: none, apart from myself

I have no other AP to test with.

I'd say yes, this is a regression. Cannot remember to have these problems with previous Ubuntu versions.

[penalvch (penalvch)]

Andreas Schildbach, so you did not have this problem in Oneiric?

[Andreas Schildbach (schildbach)]

I believe not.

[penalvch (penalvch)]

Andreas Schildbach, ok.

Regarding https://wiki.ubuntu.com/Kernel/LinuxWireless#Bug_Report_Minimum_Requirement_Information :
+ Does compat-wireless provide a WORKAROUND or solution following https://wiki.ubuntu.com/Kernel/LinuxWireless#Compat-wireless_in_Ubuntu ?
+ Does ndiswrapper provide a WORKAROUND or solution following https://help.ubuntu.com/community/WifiDocs/Driver/Ndiswrapper ?

Thank you for your understanding.

[arsenix (arsenix)]

I was traveling this week and had to connect to a lot of foreign wireless networks. Almost all of them were extremely unstable. Usually they stop working immediately after connecting, and sometimes unloading/reloading the module will allow it to work for a while before it happens again. It appears my home wireless access point is the exception in stability.

I updated to the 3.2.0-29-generic kernel (from -27) but saw no change.

I tried installing linux-backports-modules-cw-29, no improvement. Actually after more sustained use it seemed worse with compat-wireless installed, and I experienced a hard system crash at one point.

I'm not sure I want to go down the ndiswrapper rabbit hole... that seems counterproductive. I will try it if requested and if it might make my machine more useful.

This is a terrible bug... my computer is almost useless. Any workarounds would be greatly appreciated

[arsenix (arsenix)]

I also tried using wd_disable=1, but this offered no improvement. It also seemed like after using this option the failure became unrecoverable without a reboot. Currently when it stops working I can reload the module to get it back, but with wd_disable it seemed I had to reboot. Time before failure was not extended.

[penalvch (penalvch)]

arsenix, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette

When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[arsenix (arsenix)]

New bug opened at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1039205

[Didi (d10r)]

I had the same issue, after installing the quantal kernel (3.5.0-19-generic x86_64) it seems to have disappeared.
The router is a Fritzbox 7390 with firmware version 84.05.21

[Andreas Schildbach (schildbach)]

Yes indeed, after upgrading to quantal, the issue disappeared for me as well.

[penalvch (penalvch)]

Andreas Schildbach, thank you for testing this in Quantal. Did you need a backport to a release prior to Quantal, or may we close this as Status Invalid?

[Andreas Schildbach (schildbach)]

I do not need a backport. Why not close it as "fixed"?

[penalvch (penalvch)]

Andreas Schildbach, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Ayrat (airat-halimov)]

2Christopher: I read wiki and according to it the bug cannot be invalidated due to "upgrade" (notice "upgrade" and not "update" as you mentioned in your previous post).
But the bug status is "confirmed" since it was confirmed by several other people (at least, by arsenix).
Regards.

[penalvch (penalvch)]

Ayrat, that's not how bug triaging works. Hence, please do not toggle this report further. For more on this, please see the Ubuntu Bug Control, and Ubuntu Bug Squad article https://wiki.ubuntu.com/Bugs/Responses .

If you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Vladimir Psenicka (vladimir-psenicka)]

I have same problem with Lubuntu 13.04. Bug still exists, even with upstream kernel 3.10

[penalvch (penalvch)]

Vladmir Psenicka, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.