Created attachment 1650129 [details] iwlwifi_log Description of problem: Since the 5.4.7-200.fc31.x86_64 kernel update, the Intel Corporation Killer Wi-Fi 6 AX1650i wifi card is not working anymore. On the logs, it seems that some firmware are missing: kernel: iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 kernel: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-Qu-b0-hr-b0-49.ucode failed with error -2 I'm attaching the log file with all the iwlwifi mentions. Version-Release number of selected component (if applicable): kernel-5.4.7-200.fc31.x86_64 linux-firmware-whence-20191022-103.fc31.noarch linux-firmware-20191022-103.fc31.noarch How reproducible: It happens at every boot with this kernel. Wifi is working fine under kernel-5.3.16-300.fc31.x86_64 Expected results: Wifi working Additional info:
This looks like a problem in the kernel, not with the firmware. Intel hasn't released -49 or -50 upstream yet. A cursory look seems to show the kernel probably needs: commit db5cce1afc8d2475d2c1c37c2a8267dd0e151526 Author: Anders Kaseorg <andersk> Date: Mon Dec 2 17:09:20 2019 -0500 Revert "iwlwifi: assign directly to iwl_trans->cfg in QuZ detection" This reverts commit 968dcfb4905245dc64d65312c0d17692fa087b99. Both that commit and commit 809805a820c6445f7a701ded24fdc6bbc841d1e4 attempted to fix the same bug (dead assignments to the local variable cfg), but they did so in incompatible ways. When they were both merged, independently of each other, the combination actually caused the bug to reappear, leading to a firmware crash on boot for some cards. https://bugzilla.kernel.org/show_bug.cgi?id=205719 Signed-off-by: Anders Kaseorg <andersk> Acked-by: Luca Coelho <luciano.coelho> Signed-off-by: Kalle Valo <kvalo>
Hello, I am still having this same issue on 5.4.10-200.fc31.x86_64 with a Killer Wi-Fi 6 AX1650i. Someone over on Fedora-users said this was fixed in 5.4.8-200.fc31 but that doesn't seem to be the case? I get the same kernel errors as the poster above: iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-Qu-b0-hr-b0-49.ucode failed with error -2 Version-Release number of selected component (if applicable): kernel-5.4.10-200.fc31.x86_64 linux-firmware-whence-20191022-103.fc31.noarch linux-firmware-20191022-103.fc31.noarch Reproducible: Every 5.4.x kernel boot in F31. Killer Wifi works on 5.3.x series kernels.
I think the same issue still exists on the 5.5.2-200 test kernel. Happy to open a new bug if this is different. [ 9.225684] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) [ 9.230302] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-Qu-b0-hr-b0-52.ucode failed with error -2 [ 9.230320] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-Qu-b0-hr-b0-51.ucode failed with error -2 [ 9.230334] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-Qu-b0-hr-b0-50.ucode failed with error -2 [ 9.230346] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-Qu-b0-hr-b0-49.ucode failed with error -2 [ 9.231741] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17 [ 9.231743] iwlwifi 0000:00:14.3: Found debug destination: EXTERNAL_DRAM [ 9.231743] iwlwifi 0000:00:14.3: Found debug configuration: 0 [ 9.231863] iwlwifi 0000:00:14.3: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm [ 9.460953] iwlwifi 0000:00:14.3: Detected Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x338 [ 9.466772] iwlwifi 0000:00:14.3: Applying debug destination EXTERNAL_DRAM [ 9.466957] iwlwifi 0000:00:14.3: Allocated 0x00400000 bytes for firmware monitor. [ 10.496242] iwlwifi 0000:00:14.3: Collecting data: trigger 15 fired. [ 10.496612] iwlwifi 0000:00:14.3: Start IWL Error Log Dump: [ 10.496613] iwlwifi 0000:00:14.3: Status: 0x00000000, count: -1115362398 [ 10.496614] iwlwifi 0000:00:14.3: Loaded firmware version: 48.4fa0041f.0 [ 10.496615] iwlwifi 0000:00:14.3: 0x95FFBAF4 | ADVANCED_SYSASSERT [ 10.496616] iwlwifi 0000:00:14.3: 0x4015D34B | trm_hw_status0 [ 10.496616] iwlwifi 0000:00:14.3: 0xDB01962F | trm_hw_status1 [ 10.496617] iwlwifi 0000:00:14.3: 0xFE8D15B7 | branchlink2 [ 10.496618] iwlwifi 0000:00:14.3: 0x779FD3B1 | interruptlink1 [ 10.496618] iwlwifi 0000:00:14.3: 0xB1CE405E | interruptlink2 [ 10.496619] iwlwifi 0000:00:14.3: 0x2AFD952A | data1 [ 10.496619] iwlwifi 0000:00:14.3: 0xB6A2F797 | data2 [ 10.496620] iwlwifi 0000:00:14.3: 0xC65B571B | data3 [ 10.496621] iwlwifi 0000:00:14.3: 0x1A2EA94B | beacon time [ 10.496621] iwlwifi 0000:00:14.3: 0x2E75CB46 | tsf low [ 10.496622] iwlwifi 0000:00:14.3: 0xDE75FF23 | tsf hi [ 10.496622] iwlwifi 0000:00:14.3: 0xC323B9CF | time gp1 [ 10.496623] iwlwifi 0000:00:14.3: 0x161B71BA | time gp2 [ 10.496624] iwlwifi 0000:00:14.3: 0xAF43D17B | uCode revision type [ 10.496624] iwlwifi 0000:00:14.3: 0xA8BBEFDE | uCode version major [ 10.496625] iwlwifi 0000:00:14.3: 0x5FEF209B | uCode version minor [ 10.496625] iwlwifi 0000:00:14.3: 0xF09F783D | hw version [ 10.496626] iwlwifi 0000:00:14.3: 0x5E8AB87B | board version [ 10.496627] iwlwifi 0000:00:14.3: 0x9AF14555 | hcmd [ 10.496627] iwlwifi 0000:00:14.3: 0x76C8FF1E | isr0 [ 10.496628] iwlwifi 0000:00:14.3: 0x5EBD9A69 | isr1 [ 10.496628] iwlwifi 0000:00:14.3: 0x711C05E1 | isr2 [ 10.496629] iwlwifi 0000:00:14.3: 0xC456919C | isr3 [ 10.496629] iwlwifi 0000:00:14.3: 0xF1EF168D | isr4 [ 10.496630] iwlwifi 0000:00:14.3: 0xD1DE697C | last cmd Id [ 10.496631] iwlwifi 0000:00:14.3: 0x463A16E1 | wait_event [ 10.496631] iwlwifi 0000:00:14.3: 0x3A1C582E | l2p_control [ 10.496632] iwlwifi 0000:00:14.3: 0x1AD708B0 | l2p_duration [ 10.496632] iwlwifi 0000:00:14.3: 0x7E7CCBD7 | l2p_mhvalid [ 10.496633] iwlwifi 0000:00:14.3: 0xD7B33C25 | l2p_addr_match [ 10.496634] iwlwifi 0000:00:14.3: 0xF69391AE | lmpm_pmg_sel [ 10.496634] iwlwifi 0000:00:14.3: 0x1B06DF59 | timestamp [ 10.496635] iwlwifi 0000:00:14.3: 0x7F55A585 | flow_handler [ 10.496773] iwlwifi 0000:00:14.3: Start IWL Error Log Dump: [ 10.496773] iwlwifi 0000:00:14.3: Status: 0x00000000, count: 7 [ 10.496774] iwlwifi 0000:00:14.3: 0x201013F1 | ADVANCED_SYSASSERT [ 10.496775] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1 [ 10.496775] iwlwifi 0000:00:14.3: 0xC008D49C | umac branchlink2 [ 10.496776] iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink1 [ 10.496777] iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2 [ 10.496777] iwlwifi 0000:00:14.3: 0x00000003 | umac data1 [ 10.496778] iwlwifi 0000:00:14.3: 0x02000300 | umac data2 [ 10.496779] iwlwifi 0000:00:14.3: 0x01300504 | umac data3 [ 10.496779] iwlwifi 0000:00:14.3: 0x00000030 | umac major [ 10.496780] iwlwifi 0000:00:14.3: 0x4FA0041F | umac minor [ 10.496781] iwlwifi 0000:00:14.3: 0x0000614C | frame pointer [ 10.496781] iwlwifi 0000:00:14.3: 0xC0887F58 | stack pointer [ 10.496782] iwlwifi 0000:00:14.3: 0x00000000 | last host cmd [ 10.496782] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg [ 10.496799] iwlwifi 0000:00:14.3: Fseq Registers: [ 10.496802] iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_ERROR_CODE [ 10.496805] iwlwifi 0000:00:14.3: 0x00290033 | FSEQ_TOP_INIT_VERSION [ 10.496807] iwlwifi 0000:00:14.3: 0x80070043 | FSEQ_CNVIO_INIT_VERSION [ 10.496810] iwlwifi 0000:00:14.3: 0x0000A481 | FSEQ_OTP_VERSION [ 10.496813] iwlwifi 0000:00:14.3: 0x00000002 | FSEQ_TOP_CONTENT_VERSION [ 10.496815] iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN [ 10.496818] iwlwifi 0000:00:14.3: 0x02000300 | FSEQ_CNVI_ID [ 10.496821] iwlwifi 0000:00:14.3: 0x01300504 | FSEQ_CNVR_ID [ 10.496823] iwlwifi 0000:00:14.3: 0x02000300 | CNVI_AUX_MISC_CHIP [ 10.496828] iwlwifi 0000:00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP [ 10.496853] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 10.496877] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 10.496938] iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0x609a, CPU2 Status: 0x3 [ 10.496940] iwlwifi 0000:00:14.3: Failed to start RT ucode: -110 [ 10.496942] iwlwifi 0000:00:14.3: Firmware not running - cannot dump error [ 10.508329] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110
Still not working in kernel-5.4.17-200.fc31.x86_64 Have to use good old kernel-5.3.16-300.fc31.x86_64 for working wifi.
I tried 5.5.3-200.fc31 and still no luck.
Fixed in Ubuntu ? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859287
This issue appears to be fixed in kernel 5.6.0-0.rc2.git0.1.fc32.x86_64 . (tested with Fedora32 branch Fedora-Workstation-Live-x86_64-32-20200219.n.0.iso) Is a backport viable ?
> Is a backport viable ? It depends on the patch set required, I looked in the ubuntu bug and couldn't see a reference to the upstream bug, and I didn't yet find the applicable reference on the wireless list. If you've got a direct link it might be useful. The iwl patch deltas between releases is generally quite large.
(In reply to Peter Robinson from comment #8) > applicable reference on the wireless list. If you've got a direct link it > might be useful. The iwl patch deltas between releases is generally quite > large. Thanks for the effort, Peter. Unfortunately, bisecting kernel releases is out of my league. Apparently, kernel 5.6.0-0.rc0.git5.1.fc32.x86_64 already provided for a fix : https://www.spinics.net/lists/fedora-testing/msg139308.html
Created attachment 1664437 [details] "modprobe iwlwifi" dmesg output Still an issue in the latest kernel-5.5.5-200.fc31 (see attachment).
(In reply to Didier from comment #9) > (In reply to Peter Robinson from comment #8) > > > applicable reference on the wireless list. If you've got a direct link it > > might be useful. The iwl patch deltas between releases is generally quite > > large. > > Thanks for the effort, Peter. > Unfortunately, bisecting kernel releases is out of my league. > > Apparently, kernel 5.6.0-0.rc0.git5.1.fc32.x86_64 already provided for a fix Yes, but there's 40 odd patches for iwl in the 5.6 merge window and a quick read nothing looked obvious, and I've not seen an explicit commit referenced on lists as fixing it. Not so much about bisecting, but rather seeing if there's a reference on mailing lists to the fix.
I'd like to present the F31 version (based on the koji F32 version) of kernel-5.6.0-0.rc3.git0.1 in https://copr.fedorainfracloud.org/coprs/ifas/kernel-56/ , but notwithstanding a successful build (contrary to kernel-5.6.0-0.rc2.git0.1), the rpm's seem to have gone missing : https://download.copr.fedorainfracloud.org/results/ifas/kernel-56/fedora-31-x86_64/01251934-kernel/
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 31 kernel bugs. Fedora 31 has now been rebased to 5.5.7-200.fc31. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 32, and are still experiencing this issue, please change the version to Fedora 32. If you experience different issues, please open a new bug report for those.
Can confirm this bug still exists in 5.5.7-200.fc31
Still not working in kernel-5.5.7-200.fc31.x86_64.
I am currently running 5.6.0-0.rc3.git0.1.fc31.x86_64 from https://copr.fedorainfracloud.org/coprs/ifas/kernel-56, and 5.6.0-0.rc4.git0.1.fc31 has been successfully rebuilt for F31 too. (Going back to 5.3 is not an option due to bug#1746319).
5.6.0-0.rc5.git0.1 for F31 : https://repos.fedorapeople.org/repos/thl/kernel-vanilla-mainline/fedora-31/x86_64/
Not working on kernel-5.5.8-200
+ kernel-5.5.11-200
Fixed in kernel-5.6.4-300.fc31.x86_64 . linux-firmware : 20200316-106.fc31.noarch iwl7260-firmware : 25.30.13.0-106.fc31.noarch
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.