Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 721064 - iwlwifi: Queue 10 is active on fifo 1 and stuck for 10000 ms.
Summary: iwlwifi: Queue 10 is active on fifo 1 and stuck for 10000 ms.
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-05 09:14 UTC by Armitage
Modified: 2020-07-13 11:22 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Full dmesg output. (iwlwifi-error.log,84.47 KB, text/x-log)
2020-05-05 09:15 UTC, Armitage
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Armitage 2020-05-05 09:14:32 UTC
The connection is randomly lost and restarted. It seems that there's a problem with sys-kernel/linux-firmware-20200421 and sys-kernel/gentoo-sources-5.4.38 (sys-kernel/gentoo-sources-5.4.28 is also affected).

The problem can be solved by loading the iwlwifi module with the 11n_disable=1 option, but then the connection is limited to 20Mb/s.

The wireless card is:

# lspci -kkk -vvv | grep Net
00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30)

The firmwares that iwlwifi loads:

# modinfo iwlwifi | grep firmware
firmware:       iwlwifi-100-5.ucode
firmware:       iwlwifi-1000-5.ucode
firmware:       iwlwifi-135-6.ucode
firmware:       iwlwifi-105-6.ucode
firmware:       iwlwifi-2030-6.ucode
firmware:       iwlwifi-2000-6.ucode
firmware:       iwlwifi-5150-2.ucode
firmware:       iwlwifi-5000-5.ucode
firmware:       iwlwifi-6000g2b-6.ucode
firmware:       iwlwifi-6000g2a-6.ucode
firmware:       iwlwifi-6050-5.ucode
firmware:       iwlwifi-6000-6.ucode
firmware:       iwlwifi-7265D-29.ucode
firmware:       iwlwifi-7265-17.ucode
firmware:       iwlwifi-3168-29.ucode
firmware:       iwlwifi-3160-17.ucode
firmware:       iwlwifi-7260-17.ucode
firmware:       iwlwifi-8265-36.ucode
firmware:       iwlwifi-8000C-36.ucode
firmware:       iwlwifi-9260-th-b0-jf-b0-46.ucode
firmware:       iwlwifi-9000-pu-b0-jf-b0-46.ucode
firmware:       iwlwifi-ty-a0-gf-a0-50.ucode
firmware:       iwlwifi-so-a0-gf-a0-50.ucode
firmware:       iwlwifi-so-a0-hr-b0-50.ucode
firmware:       iwlwifi-so-a0-jf-b0-50.ucode
firmware:       iwlwifi-cc-a0-50.ucode
firmware:       iwlwifi-QuQnj-b0-jf-b0-50.ucode
firmware:       iwlwifi-QuZ-a0-jf-b0-50.ucode
firmware:       iwlwifi-QuZ-a0-hr-b0-50.ucode
firmware:       iwlwifi-Qu-b0-jf-b0-50.ucode
firmware:       iwlwifi-Qu-c0-hr-b0-50.ucode
firmware:       iwlwifi-QuQnj-a0-hr-a0-50.ucode
firmware:       iwlwifi-QuQnj-b0-hr-b0-50.ucode
firmware:       iwlwifi-QuQnj-f0-hr-a0-50.ucode
firmware:       iwlwifi-Qu-a0-jf-b0-50.ucode
firmware:       iwlwifi-Qu-a0-hr-a0-50.ucode

The dmesg output is:

[   69.707761] iwlwifi 0000:00:14.3: Queue 10 is active on fifo 1 and stuck for 10000 ms. SW [50, 69] HW [50, 69] FH TRB=0x0c010a041
[   69.707871] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[   69.707937] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[   69.707938] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 6
[   69.707938] iwlwifi 0000:00:14.3: Loaded firmware version: 46.6bf1df06.0
[   69.707939] iwlwifi 0000:00:14.3: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[   69.707939] iwlwifi 0000:00:14.3: 0x00802AF0 | trm_hw_status0
[   69.707940] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[   69.707940] iwlwifi 0000:00:14.3: 0x004882DA | branchlink2
[   69.707941] iwlwifi 0000:00:14.3: 0x0047932A | interruptlink1
[   69.707941] iwlwifi 0000:00:14.3: 0x0047932A | interruptlink2
[   69.707942] iwlwifi 0000:00:14.3: 0x0001ACAA | data1
[   69.707942] iwlwifi 0000:00:14.3: 0xFF000000 | data2
[   69.707943] iwlwifi 0000:00:14.3: 0xF0000008 | data3
[   69.707943] iwlwifi 0000:00:14.3: 0x91803B7E | beacon time
[   69.707943] iwlwifi 0000:00:14.3: 0x840BC453 | tsf low
[   69.707944] iwlwifi 0000:00:14.3: 0x00000458 | tsf hi
[   69.707944] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[   69.707945] iwlwifi 0000:00:14.3: 0x03C114C5 | time gp2
[   69.707945] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[   69.707946] iwlwifi 0000:00:14.3: 0x0000002E | uCode version major
[   69.707946] iwlwifi 0000:00:14.3: 0x6BF1DF06 | uCode version minor
[   69.707947] iwlwifi 0000:00:14.3: 0x00000312 | hw version
[   69.707947] iwlwifi 0000:00:14.3: 0x18C89008 | board version
[   69.707947] iwlwifi 0000:00:14.3: 0x0A32001C | hcmd
[   69.707948] iwlwifi 0000:00:14.3: 0x80022002 | isr0
[   69.707948] iwlwifi 0000:00:14.3: 0x00000000 | isr1
[   69.707949] iwlwifi 0000:00:14.3: 0x08001802 | isr2
[   69.707949] iwlwifi 0000:00:14.3: 0x00417CC8 | isr3
[   69.707949] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[   69.707950] iwlwifi 0000:00:14.3: 0x00A2019C | last cmd Id
[   69.707950] iwlwifi 0000:00:14.3: 0x0001ACAA | wait_event
[   69.707951] iwlwifi 0000:00:14.3: 0x00000080 | l2p_control
[   69.707951] iwlwifi 0000:00:14.3: 0x00002020 | l2p_duration
[   69.707952] iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
[   69.707952] iwlwifi 0000:00:14.3: 0x00000080 | l2p_addr_match
[   69.707953] iwlwifi 0000:00:14.3: 0x0000000D | lmpm_pmg_sel
[   69.707953] iwlwifi 0000:00:14.3: 0x08081425 | timestamp
[   69.707953] iwlwifi 0000:00:14.3: 0x0000C8E4 | flow_handler
[   69.707986] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[   69.707986] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 7
[   69.707987] iwlwifi 0000:00:14.3: 0x20000066 | NMI_INTERRUPT_HOST
[   69.707987] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[   69.707988] iwlwifi 0000:00:14.3: 0xC008885E | umac branchlink2
[   69.707988] iwlwifi 0000:00:14.3: 0xC00843E8 | umac interruptlink1
[   69.707989] iwlwifi 0000:00:14.3: 0xC00843E8 | umac interruptlink2
[   69.707989] iwlwifi 0000:00:14.3: 0x01000000 | umac data1
[   69.707990] iwlwifi 0000:00:14.3: 0xC00843E8 | umac data2
[   69.707990] iwlwifi 0000:00:14.3: 0xDEADBEEF | umac data3
[   69.707990] iwlwifi 0000:00:14.3: 0x0000002E | umac major
[   69.707991] iwlwifi 0000:00:14.3: 0x6BF1DF06 | umac minor
[   69.707991] iwlwifi 0000:00:14.3: 0x03C114B0 | frame pointer
[   69.707992] iwlwifi 0000:00:14.3: 0xC088627C | stack pointer
[   69.707992] iwlwifi 0000:00:14.3: 0x00A2019C | last host cmd
[   69.707992] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
[   69.708007] iwlwifi 0000:00:14.3: Fseq Registers:
[   69.708015] iwlwifi 0000:00:14.3: 0xFEE2EE7F | FSEQ_ERROR_CODE
[   69.708023] iwlwifi 0000:00:14.3: 0x00000000 | FSEQ_TOP_INIT_VERSION
[   69.708032] iwlwifi 0000:00:14.3: 0x3FF9B596 | FSEQ_CNVIO_INIT_VERSION
[   69.708040] iwlwifi 0000:00:14.3: 0x0000A384 | FSEQ_OTP_VERSION
[   69.708049] iwlwifi 0000:00:14.3: 0x0E878020 | FSEQ_TOP_CONTENT_VERSION
[   69.708057] iwlwifi 0000:00:14.3: 0xD24559D7 | FSEQ_ALIVE_TOKEN
[   69.708065] iwlwifi 0000:00:14.3: 0xE25CADB7 | FSEQ_CNVI_ID
[   69.708073] iwlwifi 0000:00:14.3: 0xAB8D2781 | FSEQ_CNVR_ID
[   69.708082] iwlwifi 0000:00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP
[   69.708092] iwlwifi 0000:00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP
[   69.708103] iwlwifi 0000:00:14.3: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   69.708144] iwlwifi 0000:00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   69.708153] iwlwifi 0000:00:14.3: Collecting data: trigger 2 fired.
[   69.708157] ieee80211 phy0: Hardware restart was requested

Reproducible: Always

Steps to Reproduce:
1. Compile the kernel and install linux-firmware on ASUS ZenBook.
2. Install the speedtest-cli tool.
3. Reboot and run a speedtest: the connection will be restarted while doing the speed test.
Actual Results:  
The connection was lost and the dmesg shows the output that I pasted on the description.

Expected Results:  
The connection shouldn't be lost.

I updated the system BIOS to the last version provided by the manufacturer and the result is the same.

Extra information about the wireless card model that is shown in dmesg:

iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9560, REV=0x318
Comment 1 Armitage 2020-05-05 09:15:35 UTC
Created attachment 636182 [details]
Full dmesg output.
Comment 2 Jonas Stein gentoo-dev 2020-05-06 22:38:48 UTC
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. 

I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3].
I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4].
Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product.

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://forums.gentoo.org/
[3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
[4] https://www.gentoo.org/support/
Comment 3 Armitage 2020-05-08 10:31:08 UTC
It seems that the problem was solved by disabling the wireless card power save in both module and udev.

Steps that I followed to fix the issue:

- Create the file /etc/udev/rules.d/81-wifi-powersave.rules with the content:

ACTION=="add", SUBSYSTEM=="net", KERNEL=="wl*", RUN+="/usr/bin/iw dev $name set power_save off"

- Create the file /etc/modprobe.d/iwlwifi.conf with the content:

option iwlwifi power_save=0
Comment 4 Armitage 2020-06-28 17:45:56 UTC
(In reply to Jonas Stein from comment #2)
> It is sad to read that you have problems with the software. The situation
> seems to be a bit more complicate and requires some analysis.
> We can not help you efficiently via bug tracker. The bug tracker aims rather
> on specific problems in .ebuilds and less on individual systems. 
> 
> I have had very good experience on the gentoo IRC [1] with questions like
> this. Of course there are also forums and mailing lists [2,3].
> I hope you understand, that I will close the bug here therefore and wish you
> good luck on one of the mentioned channels [4].
> Please reopen the ticket in order to provide an indication for an specific
> error in an ebuild or any gentoo related product.
> 
> [1] https://www.gentoo.org/get-involved/irc-channels/
> [2] https://forums.gentoo.org/
> [3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
> [4] https://www.gentoo.org/support/

I could reproduce again the issue after resuming from suspend. I followed your instructions and asked to the IRC, but we didn't find any solution. 

Today I found that patch, which I'm testing:

https://lore.kernel.org/linux-wireless/iwlwifi.20200323151304.a491f6c5ae4b.I6829a46b89e4e701f80a0e4033f4dd41ee44ed12@changeid/

And it seems to work. The power control should also be disabled with that patch (otherwise I can reproduce the issue).

I will test it for a while and let you know if it works and is stable. The patch is not present on sys-kernel/gentoo-sources-5.4.48 (the stable version) so if it works maybe I could make a request so the patch is officially included by the Gentoo team.
Comment 5 Armitage 2020-06-28 18:22:47 UTC
It was a false positive, I could reproduce the issue again.
Comment 6 Armitage 2020-06-29 09:56:50 UTC
I tried acpi_osi='Windows 2009' on kernel parameters and the issue was also reproduced. Then I tried acpi_osi='Windows 2015' and it seems to be working fine. I will test it for a while and let you know if that's stable solution for me or if it was a false positive.
Comment 7 Armitage 2020-06-29 16:39:53 UTC
It was a false positive. An I would like to reopen the bug in order to have support to solve it, since I can't get it solved by myself after a lot of research and lots of tests. So I mark it as "unconfirmed" hoping that someone can give that support.
Comment 8 Jonas Stein gentoo-dev 2020-06-30 14:57:02 UTC
you need individual support first.

check 
[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://forums.gentoo.org/
[3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
[4] https://www.gentoo.org/support/

when you know what is broken, report in a new ticket.
Comment 9 Armitage 2020-07-13 09:05:51 UTC
The problem seems to be fixed after disabling Network Stack and IPv4 PXE and IPv6 PXE on System BIOS.

Enabling those options makes no sense in my configuration so the solution is valid for me.

I also added amsdu_size=3 as iwlwifi module parameter.

After 1 hour using the laptop the issue was not reproduced (before the BIOS configuration change, I could reproduce the problems in a few minutes).

I still didn't test if the problem can be reproduced after suspending to ram.
Comment 10 Armitage 2020-07-13 11:22:32 UTC
The issue was not reproduced after suspending to ram so I consider the issue as solved.

Solution: disable Network Stack and PXE on the system BIOS. If the problem persists, add the amsdu_size=3 parameter while loading iwlwifi module.