FS#63418 - LTS Kernel Module iwlwifi is Failed to Load

Attached to Project: Arch Linux
Opened by Daniel Bershatsky (daskol) - Friday, 09 August 2019, 08:25 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 10 August 2019, 18:50 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture x86_64
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Brief diagnostics shows the following.

$ lspci -v
01:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
Subsystem: Intel Corporation Wireless 8260
Flags: bus master, fast devsel, latency 0, IRQ 129
Memory at e1100000 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number xxxxx
Capabilities: [14c] Latency Tolerance Reporting
Capabilities: [154] L1 PM Substates
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi


$ dmesg | grep -i iwlwifi
авг 09 10:57:28 lolita kernel: iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
авг 09 10:57:28 lolita kernel: iwlwifi 0000:01:00.0: loaded firmware version 36.8fd77bb3.0 op_mode iwlmvm
авг 09 10:57:28 lolita kernel: iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
авг 09 10:57:30 lolita kernel: iwlwifi 0000:01:00.0: SecBoot CPU1 Status: 0x3090003, CPU2 Status: 0x0
авг 09 10:57:30 lolita kernel: iwlwifi 0000:01:00.0: Failed to start INIT ucode: -110
авг 09 10:57:30 lolita kernel: iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 10 August 2019, 18:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  All modules have been rebuilt for 4.19.66 update.
Comment by Santiago Torres (sangy) - Friday, 09 August 2019, 14:57 GMT
Care to share the version of the lts-kernel you have loaded? Also, it would help to know if this didn't happen with earlier versions of the kernel or so.
Comment by Daniel Bershatsky (daskol) - Friday, 09 August 2019, 16:11 GMT
Current version of LTS kernel is 4.19.65-1. The previous ones work perfectly.
Comment by loqs (loqs) - Friday, 09 August 2019, 16:59 GMT
Have you confirmed downgrading to linux-lts 4.19.61-1 and the issue is no longer present?
There was no release between 4.19.61-1 and 4.19.65-1 so that increases the number of changes.
If it is introduced by some commit between 4.19.61-1 and 4.19.65-1 please bisect that range
contact upstream referencing the causal commit.

Loading...