Arch Linux

caoimhin

Member

Registered: 2015-02-09

Posts: 4

iwlwifi failed to flush fifo queues

This has been happening pretty consistently.  When I'm on wifi, when the traffic volume is higher than usual (e.g., when I'm on a Google Hangout call), I observe this with

journalctl -f

Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: fail to flush all tx fifo queues Q 2
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Current SW read_ptr 121 write_ptr 126
Feb 09 10:42:31 sargas kernel: iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: FH TRBs(0) = 0x00000000
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: FH TRBs(1) = 0xc0110094
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: FH TRBs(2) = 0x8020101d
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: FH TRBs(3) = 0x8030006c
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: FH TRBs(4) = 0x00000000
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: FH TRBs(5) = 0x00000000
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: FH TRBs(6) = 0x00000000
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: FH TRBs(7) = 0x007090af
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [109,109]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [30,30]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [121,126]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 4 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 8 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 9 is active and mapped to fifo 7 ra_tid 0x0000 [176,176]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 15 is active and mapped to fifo 5 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 16 is active and mapped to fifo 1 ra_tid 0x0000 [133,22]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 17 is inactive and mapped to fifo 2 ra_tid 0x0005 [12,12]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas kernel: iwlwifi 0000:01:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
Feb 09 10:42:31 sargas NetworkManager[254]: <warn>  Connection disconnected (reason -4)

then the connection drops which made the hangout call choppy.  A few seconds later, it came back on:

Feb 09 10:42:31 sargas kernel: cfg80211: Calling CRDA to update world regulatory domain
Feb 09 10:42:31 sargas NetworkManager[254]: <info>  (wlp1s0): supplicant interface state: completed -> disconnected
Feb 09 10:42:31 sargas NetworkManager[254]: <info>  (wlp1s0): supplicant interface state: disconnected -> scanning
Feb 09 10:42:32 sargas kernel: wlp1s0: authenticate with 10:bf:48:e7:11:2b
Feb 09 10:42:32 sargas kernel: wlp1s0: send auth to 10:bf:48:e7:11:2b (try 1/3)
Feb 09 10:42:32 sargas NetworkManager[254]: <info>  (wlp1s0): supplicant interface state: scanning -> associating
Feb 09 10:42:32 sargas kernel: wlp1s0: authenticated
Feb 09 10:42:32 sargas kernel: wlp1s0: associate with 10:bf:48:e7:11:2b (try 1/3)
Feb 09 10:42:32 sargas kernel: wlp1s0: RX AssocResp from 10:bf:48:e7:11:2b (capab=0x411 status=0 aid=7)
Feb 09 10:42:32 sargas kernel: wlp1s0: associated
Feb 09 10:42:32 sargas NetworkManager[254]: <info>  (wlp1s0): supplicant interface state: associating -> associated
Feb 09 10:42:32 sargas NetworkManager[254]: <info>  (wlp1s0): supplicant interface state: associated -> 4-way handshake
Feb 09 10:42:32 sargas NetworkManager[254]: <info>  (wlp1s0): supplicant interface state: 4-way handshake -> completed

but not for long the whole process restarts itself...

I'm on kernel 3.18.5:

$ uname -a
Linux sargas 3.18.5-1-ARCH #1 SMP PREEMPT Fri Jan 30 07:31:50 CET 2015 x86_64 GNU/Linux

and my wireless card is Intel 7260:

$ lspci | grep Wire
01:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b)

and here's the kernel modules loaded for wifi:

$ lsmod | grep wifi
iwlwifi               156878  1 iwlmvm
cfg80211              453926  3 iwlwifi,mac80211,iwlmvm

Does this ring a bell?  How do I go about debugging it or fix it?

Thanks all

faundron

Member

Registered: 2008-04-21

Posts: 4

Re: iwlwifi failed to flush fifo queues

Same thing here with HP elitebook 850

Linux 3.18.6-1-ARCH
Intel wireless 7260 (rev 73)

volker_holthaus

Member

Registered: 2013-07-05

Posts: 11

Re: iwlwifi failed to flush fifo queues

Same here

Linux 3.18.6-1-ARCH
Intel Corporation Wireless 7260 (rev 73)

tobias_

Member

Registered: 2012-09-01

Posts: 25

Re: iwlwifi failed to flush fifo queues

Does "options iwlwifi 11n_disable=1" as modprobe.d config help?

These bugs plague iwlwifi for many years(!) now, and even in the most recent AC 7265 I see this bug.

Last edited by tobias_ (2015-03-13 13:34:45)