8086:088e [Dell XPS 13 L322X] Centrino Advanced-N 6235 wireless connection crash with "iwlwifi: fail to flush all tx fifo queues"

This change was made by a bot.

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

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.9-rc4-raring/

I installed ubuntu quantal 12.10 to test wireless, and also with kernel 3.5 I have connection drops that force me to restart the laptop.
I found that if I simply restart I get the wifi crash in the first 60 seconds of network activity. It seems that powering off, waiting 10 seconds, and rebooting delays the connection drop.
The time before the connection drops is also correlated with the amount of data transferred on newtwork and with the signal strength.
Each time the connection crash the first log entry in dmesg is
[] iwlwifi 0000:01:00.0: fail to flush all tx fifo queues

Now I installed the kernel 3.9.0-030900rc4-generic on quantal.
The wireless crashed again, forcing to reboot, but only a couple of times in several hours under high network load.
The bug is still present but now the wireless is usable. I get a different, very verbose, dmesg output, so it could be possible that this is a different bug with the same effect, and the first bug is fixed.
Tomorrow I will test on a network with a weaker signal strength.

This happens to me too on a Dell XPS 14z, same Centrino wireless card and same error message in dmesg.

kernel-bug-exists-upstream

Hi, I am also having this problem on a Samsung Series 5 laptop with Centrino Advanced-N 6235 wireless chip.

I have tried both the 3.8.8 kernel and 3.9 kernel, and the problem still exists: The wireless disconnects at a some point between 2 and 5 mins after boot up (although occassionally can last for 30 mins).

I'm sorry I don't know how to add a tag to this bug, but it is definitely not fixed in upstream kernel.

Is there any other debugging I can help with in any way? Please let me know as I would dearly like to have this problem resolved.

Thanks

I'm having the same issues. Dell XPS 13 developer edition, upgraded to 13.04. My router is a Netgear WNDR3800 running OpenWRT.

Running mainline kernel 3.9, I'm seeing the attached in my syslog. Let me know if there's any help I can provide to fix this. Otherwise, I'll probably be returning this laptop.

I asked Dell to replace the wireless card with something different, specifying known problems between Centrino wireless and Linux.
Now with an Atheros AR9462 I haven't had problems anymore.
This could be an option for those having a Dell XPS 13 developer edition like me.

Hi all,

I have the same problem and posted my findings in the wrong thread (https://bugs.launchpad.net/dell-sputnik/+bug/1091372). I don't know the correct way to transfer my comments, so I'll just copy them over here. Sorry for the confusion:

Hi all,

I am also experiencing constant disconnects on my one week old dell XPS 13 (BIOS A06). I have been trying two different kernels:

- 3.2.0-41-generic #66+kamal16~DellXPS-Ubuntu
- 3.8.0-19.30~precise1

srcversion of the module for the 3.2.0 kernel is
$ modinfo iwlwifi
srcversion: 99F715B156678F68AE86AC4

and for the 3.8.0 kernel:
809985E6954BA6AA05902AC

The two driver versions seem to have different issues, however. The bug in the 3.2. version always reports something about a stuck Queue in dmesg (see bug #1009878 ) while the 3.8. kernel says something described in bug #1159145.

Collecting the information from several forum posts, I always disable 11n mode, hardware encryption and enable the watchdog for stuck queues. I double check these iwlwifi module parameters by cat'ing the corresponding entries in /sys/module/iwlwifi/parameters/. Also I disabled power management for the card by inserting into /etc/pm/power.d/wireless:

#!/bin/sh
/sbin/iwconfig wlan0 power off
exit 0

and checking it with:
$ iwconfig wlan0
wlan0 IEEE 802.11abg ESSID:"Rahi_Net"
          Mode:Managed Frequency:2.412 GHz Access Point: 00:0F:66:24:D9:D9
          Bit Rate=54 Mb/s Tx-Power=15 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality=70/70 Signal level=-38 dBm
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:710 Missed beacon:0

It seems really to be the case, that the 6235 chip from Intel has issues, which are ignored by them. See this forum entry at the Intel support site:
http://communities.intel.com/thread/31090?start=0&tstart=0

A ticket was filed by Red Hat to the linuxwireless bugzilla (official intel development site). As it seems, the buzilla site was taken down "due to security reasons". See bottom of this page:
http://wireless.kernel.org/en/users/Drivers/iwlwifi

Also Dell customers complained without success:
http://en.community.dell.com/techcenter/os-applications/f/4613/t/19464992.aspx?PageIndex=1

It doesn't seem to me, that there will be a solution anytime soon. My question is: does this problem only occur on some XPS 13 notebooks? It seems that the problem with the 6235 chip is very long known, so why did Dell use this chipset in its "Ubuntu Notebook"? And did this really go through QA at Canonical, Dell _and_ Intel? Seems that quite a big number of people are having this issue.

Anyhow I'd like to help, if anyone has questions. The sad thing is, I really don't know how to provoke this bug. Will keep you posted. BTW: does anyone know how I can update the BIOS to A08? The freedos USB boot disk way does not work for me. Running the executable freezes the machine. Also I cannot extract the hdr from the exe.

Update:

I talked to the Dell support today, to get to speak to ProSupport. Turns out I am required to have purchased specifically the "developer edition" and not a random Dell XPS 13, else my Ubuntu issues don't justify a refund. Nice.

But the support people were helpfull in that they found out, that the "developer edition" is advertised to have a different wifi chipset compared to the windows versions. The Ubuntu ones have the 6230 and not the 6235:

http://www.dell.com/us/business/p/xps-13-linux/pd
http://www.dell.com/us/business/p/xps-13-l321x-mlk/pd

These chips are really different:

http://www.intel.com/content/www/us/en/processors/centrino/centrino-advanced-n-6230-brief.html
http://www.intel.com/content/www/us/en/processors/centrino/centrino-advanced-n-wimax-6235-brief.html

WRT the last comment, I have the developer edition (L322X) and lspci reports that I have:

  Intel Corporation Centrino Advanced-N 6235

just as in the original report.

Update:

In the process of returning the notebook (which I will do, because I now officially hate Dell), I encountered a thread on the intel community site, where users report connection drops on *drum roll*: Windows 8.

http://communities.intel.com/thread/31090

Either Intel is shipping some broken chips or the firmware is buggy. Anyhow I ordered a Windows rescue USB device from Dell, installed Windows 8, installed the newest wireless driver and the connection drops also.

Does anyone here who encounters this problem have the possibility to install Windows 8 and check whether the wireless is also not working? At least now I won't be treated like a criminal by Dell support for installing Ubuntu.

Hi

yes I have the very same problem. I bought a "standard" XPS13 from Dell, because they didn't have the developper edition with a US keyboard in my country.

The wireless works well for about 5mn and then drops. Then everything is very very slow (unusable in fact). I have installed kubuntu 13.04 and am running 3.8.0-22-generic #33-Ubuntu SMP Thu May 16 15:17:14 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux.

Everything else is as described above (power management off etc).

I am sure I understood the post above: is there a solution (patch or..) to this problem or not?

Sorry, last post, please read "I am NOT sure I understood the post above: is there a solution (patch or..) to this problem or not?"

thanks

Hi guys,

You need to seriously consider the possibility that your Centrino chip is faulty at the hardware level.

I too had these symptoms:
* Wireless would drop and become unusable, usually under 5 minutes
* The only way to recover wireless is by rebooting
* The points above happen to both Windows and Linux

Not wanting to waste any more time, I called Dell support and armwrestled them to replace my wireless chip. Sure enough after the replacement the problem disappears on both Windows and Linux (Kubuntu 13.04).

My XPS 13 is a normal non-Linux edition. If you've been given a piece of faulty hardware, you should demand a replacement, regardless of whether you have a XPS 13 Developer edition.

Best of luck.

Hi

thanks for the frank comment. I may go that way. But before:

- I have used (with the previous kernel: as I just updated it) the wireless for about 2 days at work, and all seemed ok. I am wondering if this is not just a weird interaction with my router and home material. However, I am not sure how to test that. Since I will be testing other wireless facilities in the coming weeks, I'll give it a go (and do some regular internet tests) and see if this is specific to my home router. I have had some issues in the past with another older Dell for which the chip was just a different one (obviously).

I'll keep this post updated with my findings for next week.
cheers

After replacing my adapter (with an identical model), the drop after a few minutes and other problems originally reported went away. So, I guess, that's what I'd recommend, too.

However, I still have problems with high ping times. The "solution" to that is to disable power management in the iwlwifi driver.

When I asked why Dell ships an Ubuntu laptop with a wireless adapter known to have issues, the reply was along the lines of: to earn the "Ultrabook" moniker it must ship with a Centrino adapter. Just FYI.

Thanks Zukerman, that is very helpful to know your experience replacing the adapter.

We should all try using Windows for a good few days and see if the problem persists, and if so then I think it would be safe to conclude it is hardware after all.

I won't be able to go back to Windows for another week or so, but after I do I will test and report back what I find on my machine.

It would be helpful if others can also try Windows, report back, replace adapter, and then report back again

Hi All,
I have the same issue of disconnecting wifi on my Dell XPS machine. I do not have windows and I am not able to test it there.
I have created a bug report for this with the kernel stack trace. I am not sure if this is the same issue. I have a slightly different dmesg outout which also shows the stack trace of the crash. I seriously hope its a software issue!

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1226728

I also have the problem with a Intel WiFi Link 5100 AGN

[ 1161.053781] iwlwifi 0000:12:00.0: fail to flush all tx fifo queues Q 2
[ 1161.053794] iwlwifi 0000:12:00.0: Current SW read_ptr 104 write_ptr 125
[ 1161.053825] iwl data: 00000000: 00 00 00 00 00 00 00 00 00 ff ff 00 00 00 00 00 ................
[ 1161.053842] iwlwifi 0000:12:00.0: FH TRBs(0) = 0x00000000
[ 1161.053861] iwlwifi 0000:12:00.0: FH TRBs(1) = 0x80102077
[ 1161.053875] iwlwifi 0000:12:00.0: FH TRBs(2) = 0x00000000
[ 1161.053890] iwlwifi 0000:12:00.0: FH TRBs(3) = 0x80300010
[ 1161.053904] iwlwifi 0000:12:00.0: FH TRBs(4) = 0x00000000
[ 1161.053919] iwlwifi 0000:12:00.0: FH TRBs(5) = 0x00000000
[ 1161.053933] iwlwifi 0000:12:00.0: FH TRBs(6) = 0x00000000
[ 1161.053947] iwlwifi 0000:12:00.0: FH TRBs(7) = 0x00704062
[ 1161.054006] iwlwifi 0000:12:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [17,17]
[ 1161.054065] iwlwifi 0000:12:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [0,0]
[ 1161.054124] iwlwifi 0000:12:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [104,125]
[ 1161.054183] iwlwifi 0000:12:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054243] iwlwifi 0000:12:00.0: Q 4 is active and mapped to fifo 7 ra_tid 0x0000 [99,99]
[ 1161.054304] iwlwifi 0000:12:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054365] iwlwifi 0000:12:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054427] iwlwifi 0000:12:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054486] iwlwifi 0000:12:00.0: Q 8 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054545] iwlwifi 0000:12:00.0: Q 9 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054605] iwlwifi 0000:12:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054665] iwlwifi 0000:12:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054723] iwlwifi 0000:12:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054782] iwlwifi 0000:12:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054841] iwlwifi 0000:12:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054901] iwlwifi 0000:12:00.0: Q 15 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.054960] iwlwifi 0000:12:00.0: Q 16 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.055019] iwlwifi 0000:12:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.055079] iwlwifi 0000:12:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1161.055138] iwlwifi 0000:12:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[ 1223.471978] wlan0: deauthenticating from c0:ea:e4:4d:7b:47 by local choice (reason=3)
[ 1225.481040] iwlwifi 0000:12:00.0: fail to flush all tx fifo queues Q 2
[ 1225.481046] iwlwifi 0000:12:00.0: Current SW read_ptr 194 write_ptr 81
[ 1225.481074] iwl data: 00000000: fc ff 03 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
[ 1225.481089] iwlwifi 0000:12:00.0: FH TRBs(0) = 0x00000000
[ 1225.481104] iwlwifi 0000:12:00.0: FH TRBs(1) = 0x801020d1
[ 1225.481121] iwlwifi 0000:12:00.0: FH TRBs(2) = 0x0000...

When I load the Module with modprobe iwlwifi 11n_disable=1 Iit looks like its gone...

https://lkml.org/lkml/2013/5/22/119

Bug is still present on mainline kernel 3.12.0-031200rc4-generic

Marco, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1159145/comments/8 regarding you no longer used the card reported against. 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.

I find it weird that this was marked as invalid when quite a bunch of people reported that they were still seeing it and that it was still present in mainline kernel. I'm moving it to Confirmed.

Also, it's likely that this is the same as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1281170

Here is a case we are working on with the same wireless driver: http://askubuntu.com/questions/502545/i-keep-wifi-connection-but-lose-internet-access

The problem is still there on 14.04.

Hi Luis and others, what model of wireless chip do you have?
If its an Intel Advanced-N 6235, please find my experience below of this problem SOLVED:
I had exactly the same issue as described in this bug, with a 6235 wireless chip in my laptop.
After a while, I became increasingly suspicious that it was a hardware issue, not software/kernel/driver.
I bought a newer replacement 6235 chip, popped in my laptop, and the problem is now solved.
This was on U 13.04, and I'm now on 14.04, and it has been running perfectly ever since.
So there is definitely no problems with the kernel or driver in Ubuntu for this chip. I can't comment for other chips, but if you have a 6235 chip, I would strongly suggest purchasing a new replacement, fitting it, and you will find your issues resolved.

Moving to Invalid. There is no problem with Ubuntu drivers/kernel and the Advanced-N 6235 chip. This was the chip for the bug report of the OP. If anyone has similar trouble with a different chip, they should open a NEW bug report specifically for that chip.