Hi all. I’m running kernel 5.3.18-lp152.63-default on a Lenovo Thinkpad E15. I’ve found that sometimes, my Intel wireless adapter is not working when I boot the machine.
lspci -v says:
00:14.3 Network controller: Intel Corporation Comet Lake PCH-LP CNVi WiFi
Subsystem: Intel Corporation Wi-Fi 6 AX201 160MHz
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at b1318000 (64-bit, non-prefetchable) [size=16]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
Capabilities: [100] Latency Tolerance Reporting
Capabilities: [164] Vendor Specific Information: ID=0010 Rev=0 Len=014 <?>
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
dmesg shows:
8.488340] iwlwifi 0000:00:14.3: 0x00000000 | uCode version minor
8.488341] iwlwifi 0000:00:14.3: 0x00000000 | hw version
8.488343] iwlwifi 0000:00:14.3: 0x00000000 | board version
8.488344] iwlwifi 0000:00:14.3: 0x00000000 | hcmd
8.488345] iwlwifi 0000:00:14.3: 0x00000000 | isr0
8.488346] iwlwifi 0000:00:14.3: 0x00000000 | isr1
8.488348] iwlwifi 0000:00:14.3: 0x00000000 | isr2
8.488349] iwlwifi 0000:00:14.3: 0x00000000 | isr3
8.488350] iwlwifi 0000:00:14.3: 0x00000000 | isr4
8.488351] iwlwifi 0000:00:14.3: 0x00000000 | last cmd Id
8.488352] iwlwifi 0000:00:14.3: 0x00000000 | wait_event
8.488354] iwlwifi 0000:00:14.3: 0x00000000 | l2p_control
8.488355] iwlwifi 0000:00:14.3: 0x00000000 | l2p_duration
8.488356] iwlwifi 0000:00:14.3: 0x00000000 | l2p_mhvalid
8.488357] iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
8.488358] iwlwifi 0000:00:14.3: 0x00000000 | lmpm_pmg_sel
8.488360] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
8.488361] iwlwifi 0000:00:14.3: 0x00000000 | flow_handler
8.488396] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
8.488398] iwlwifi 0000:00:14.3: Status: 0x00000000, count: 7
8.488400] iwlwifi 0000:00:14.3: 0x20000066 | NMI_INTERRUPT_HOST
8.488401] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
8.488402] iwlwifi 0000:00:14.3: 0xC008D49C | umac branchlink2
8.488404] iwlwifi 0000:00:14.3: 0x8048DBD2 | umac interruptlink1
8.488405] iwlwifi 0000:00:14.3: 0x8048DBD2 | umac interruptlink2
8.488406] iwlwifi 0000:00:14.3: 0x01000000 | umac data1
8.488407] iwlwifi 0000:00:14.3: 0x8048DBD2 | umac data2
8.488409] iwlwifi 0000:00:14.3: 0x00000000 | umac data3
8.488410] iwlwifi 0000:00:14.3: 0x00000030 | umac major
8.488411] iwlwifi 0000:00:14.3: 0x4FA0041F | umac minor
8.488413] iwlwifi 0000:00:14.3: 0x000F8220 | frame pointer
8.488414] iwlwifi 0000:00:14.3: 0xC0886284 | stack pointer
8.488415] iwlwifi 0000:00:14.3: 0x0000FFFF | last host cmd
8.488416] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
8.488434] iwlwifi 0000:00:14.3: Fseq Registers:
8.488437] iwlwifi 0000:00:14.3: 0x20000000 | FSEQ_ERROR_CODE
8.488440] iwlwifi 0000:00:14.3: 0x80290030 | FSEQ_TOP_INIT_VERSION
8.488443] iwlwifi 0000:00:14.3: 0x80070043 | FSEQ_CNVIO_INIT_VERSION
8.488446] iwlwifi 0000:00:14.3: 0x0000A481 | FSEQ_OTP_VERSION
8.488449] iwlwifi 0000:00:14.3: 0x00000002 | FSEQ_TOP_CONTENT_VERSION
8.488452] iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
8.488455] iwlwifi 0000:00:14.3: 0x20000302 | FSEQ_CNVI_ID
8.488458] iwlwifi 0000:00:14.3: 0x01300504 | FSEQ_CNVR_ID
8.488461] iwlwifi 0000:00:14.3: 0x20000302 | CNVI_AUX_MISC_CHIP
8.488467] iwlwifi 0000:00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP
8.488472] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
8.488477] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
8.488494] iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0x5f20, CPU2 Status: 0x3
8.488496] iwlwifi 0000:00:14.3: Failed to start RT ucode: -110
8.488499] iwlwifi 0000:00:14.3: Firmware not running - cannot dump error
8.500671] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110
A reboot usually sorts it out. I’ve seen other posts suggesting that the firmware is the problem, but it’s weird that it works some of the time in that case. I’m also not sure what would happen if I installed the firmware myself, instead of using what openSUSE provides.
Any idea here folks? Does this need to be reported upstream?[/size]