You are not logged in.

Pages: 1

#1 2025-02-17 18:10:44

Humblenoise4
Member
Registered: 2024-12-21
Posts: 8

iwlwifi causes everything to stop working

After updating to kernel 6.13.1, I started having this issue where suddenly everything stops working. More specifically, all of my apps start closing 1 by 1 and I can't really do anything other than power off my laptop. Even just doing ls in my terminal (before it closes lol) returns an input/output error.

I have updated to 6.13.2, but the issue still persists. This happens like between once or twice a day and once every other day.

I have attached the output of journalctl (for the time where a crash happened) for one of the sessions where the crash happened. It seems like the issue has something to do with iwlwifi? If that is the case, it might be related to this other issue I had made another thread about, which I never really figured out how to solve properly. Someone suggested kind of a hacky solution that I could do every time I booted and I've basically been doing that since (see the thread for more info).

If it helps with anything, the model of my laptop is HP OMEN Laptop 15-en0xxx with the Intel AX200 WiFi chip. Thanks!

Feb 17 14:52:47.961660 myhost kernel: Freezing user space processes completed (elapsed 0.004 seconds)
Feb 17 14:52:47.961841 myhost kernel: OOM killer disabled.
Feb 17 14:52:47.961919 myhost kernel: Freezing remaining freezable tasks
Feb 17 14:52:47.962370 myhost kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Feb 17 14:52:47.962444 myhost kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Feb 17 14:52:47.962518 myhost kernel: ACPI: EC: interrupt blocked
Feb 17 14:52:47.962585 myhost kernel: ACPI: PM: Preparing to enter system sleep state S3
Feb 17 14:52:47.962664 myhost kernel: ACPI: EC: event blocked
Feb 17 14:52:47.962718 myhost kernel: ACPI: EC: EC stopped
Feb 17 14:52:47.962793 myhost kernel: ACPI: PM: Saving platform NVS memory
Feb 17 14:52:47.962858 myhost kernel: Disabling non-boot CPUs ...
Feb 17 14:52:47.962932 myhost kernel: smpboot: CPU 11 is now offline
Feb 17 14:52:47.963001 myhost kernel: smpboot: CPU 10 is now offline
Feb 17 14:52:47.963062 myhost kernel: smpboot: CPU 9 is now offline
Feb 17 14:52:47.963129 myhost kernel: smpboot: CPU 8 is now offline
Feb 17 14:52:47.963203 myhost kernel: smpboot: CPU 7 is now offline
Feb 17 14:52:47.963295 myhost kernel: smpboot: CPU 6 is now offline
Feb 17 14:52:47.963374 myhost kernel: smpboot: CPU 5 is now offline
Feb 17 14:52:47.963436 myhost kernel: smpboot: CPU 4 is now offline
Feb 17 14:52:47.963514 myhost kernel: smpboot: CPU 3 is now offline
Feb 17 14:52:47.963915 myhost kernel: smpboot: CPU 2 is now offline
Feb 17 14:52:47.964072 myhost kernel: smpboot: CPU 1 is now offline
Feb 17 14:52:47.964145 myhost kernel: Spectre V2 : Update user space SMT mitigation: STIBP off
Feb 17 14:52:47.964224 myhost kernel: ACPI: PM: Low-level resume complete
Feb 17 14:52:47.964272 myhost kernel: ACPI: EC: EC started
Feb 17 14:52:47.964343 myhost kernel: ACPI: PM: Restoring platform NVS memory
Feb 17 14:52:47.964388 myhost kernel: AMD-Vi: Virtual APIC enabled
Feb 17 14:52:47.964440 myhost kernel: AMD-Vi: Virtual APIC enabled
Feb 17 14:52:47.964487 myhost kernel: LVT offset 0 assigned for vector 0x400
Feb 17 14:52:47.964554 myhost kernel: Enabling non-boot CPUs ...
Feb 17 14:52:47.964640 myhost kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Feb 17 14:52:47.964684 myhost kernel: ACPI: FW issue: working around C-state latencies out of order
Feb 17 14:52:47.964792 myhost kernel: Spectre V2 : Update user space SMT mitigation: STIBP always-on
Feb 17 14:52:47.964879 myhost kernel: CPU1 is up
Feb 17 14:52:47.964960 myhost kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Feb 17 14:52:47.965037 myhost kernel: ACPI: FW issue: working around C-state latencies out of order
Feb 17 14:52:47.965106 myhost kernel: CPU2 is up
Feb 17 14:52:47.965178 myhost kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Feb 17 14:52:47.965235 myhost kernel: ACPI: FW issue: working around C-state latencies out of order
Feb 17 14:52:47.965295 myhost kernel: CPU3 is up
Feb 17 14:52:47.965348 myhost kernel: smpboot: Booting Node 0 Processor 4 APIC 0x4
Feb 17 14:52:47.965410 myhost kernel: ACPI: FW issue: working around C-state latencies out of order
Feb 17 14:52:47.965458 myhost kernel: CPU4 is up
Feb 17 14:52:47.965518 myhost kernel: smpboot: Booting Node 0 Processor 5 APIC 0x5
Feb 17 14:52:47.965578 myhost kernel: ACPI: FW issue: working around C-state latencies out of order
Feb 17 14:52:47.965653 myhost kernel: CPU5 is up
Feb 17 14:52:47.965715 myhost kernel: smpboot: Booting Node 0 Processor 6 APIC 0x8
Feb 17 14:52:47.965780 myhost kernel: ACPI: FW issue: working around C-state latencies out of order
Feb 17 14:52:47.965831 myhost kernel: CPU6 is up
Feb 17 14:52:47.965902 myhost kernel: smpboot: Booting Node 0 Processor 7 APIC 0x9
Feb 17 14:52:47.965960 myhost kernel: ACPI: FW issue: working around C-state latencies out of order
Feb 17 14:52:47.966013 myhost kernel: CPU7 is up
Feb 17 14:52:47.966068 myhost kernel: smpboot: Booting Node 0 Processor 8 APIC 0xa
Feb 17 14:52:47.966130 myhost kernel: ACPI: FW issue: working around C-state latencies out of order
Feb 17 14:52:47.966195 myhost kernel: CPU8 is up
Feb 17 14:52:47.966272 myhost kernel: smpboot: Booting Node 0 Processor 9 APIC 0xb
Feb 17 14:52:47.966357 myhost kernel: ACPI: FW issue: working around C-state latencies out of order
Feb 17 14:52:47.966411 myhost kernel: CPU9 is up
Feb 17 14:52:47.966472 myhost kernel: smpboot: Booting Node 0 Processor 10 APIC 0xc
Feb 17 14:52:47.966533 myhost kernel: ACPI: FW issue: working around C-state latencies out of order
Feb 17 14:52:47.966627 myhost kernel: CPU10 is up
Feb 17 14:52:47.966701 myhost kernel: smpboot: Booting Node 0 Processor 11 APIC 0xd
Feb 17 14:52:47.966776 myhost kernel: ACPI: FW issue: working around C-state latencies out of order
Feb 17 14:52:47.966845 myhost kernel: CPU11 is up
Feb 17 14:52:47.966912 myhost kernel: ACPI: PM: Waking up from system sleep state S3
Feb 17 14:52:47.966987 myhost kernel: ACPI: EC: interrupt unblocked
Feb 17 14:52:47.967060 myhost kernel: ACPI: EC: event unblocked
Feb 17 14:52:47.967119 myhost kernel: [drm] PCIE GART of 1024M enabled.
Feb 17 14:52:47.967179 myhost kernel: [drm] PTB located at 0x000000F41FC00000
Feb 17 14:52:47.967239 myhost kernel: amdgpu 0000:07:00.0: amdgpu: PSP is resuming...
Feb 17 14:52:47.967930 myhost kernel: xhci_hcd 0000:01:00.2: xHC error in resume, USBSTS 0x401, Reinit
Feb 17 14:52:47.968454 myhost kernel: usb usb1: root hub lost power or was reset
Feb 17 14:52:47.968977 myhost kernel: usb usb2: root hub lost power or was reset
Feb 17 14:52:47.969429 myhost kernel: iwlwifi 0000:03:00.0: iwl_mvm_check_rt_status failed, device is gone during suspend
Feb 17 14:52:47.969971 myhost kernel: nvme nvme1: D3 entry latency set to 8 seconds
Feb 17 14:52:47.970351 myhost kernel: nvme nvme0: D3 entry latency set to 10 seconds
Feb 17 14:52:47.970729 myhost kernel: nvme nvme0: 12/0/0 default/read/poll queues
Feb 17 14:52:47.971191 myhost kernel: iwlwifi 0000:03:00.0: HW error, resetting before reading
Feb 17 14:52:47.971854 myhost kernel: nvme nvme1: 12/0/0 default/read/poll queues
Feb 17 14:52:47.972303 myhost kernel: iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
Feb 17 14:52:47.972882 myhost kernel: iwlwifi 0000:03:00.0: Transport status: 0x00000042, valid: -328284396
Feb 17 14:52:47.973388 myhost kernel: iwlwifi 0000:03:00.0: Loaded firmware version: 77.0b4c06ad.0 cc-a0-77.ucode
Feb 17 14:52:47.973933 myhost kernel: iwlwifi 0000:03:00.0: 0x318800AB | ADVANCED_SYSASSERT          
Feb 17 14:52:47.974417 myhost kernel: iwlwifi 0000:03:00.0: 0x0680E07D | trm_hw_status0
Feb 17 14:52:47.974971 myhost kernel: iwlwifi 0000:03:00.0: 0xABA688A3 | trm_hw_status1
Feb 17 14:52:47.975506 myhost kernel: iwlwifi 0000:03:00.0: 0x01A603C6 | branchlink2
Feb 17 14:52:47.976160 myhost kernel: iwlwifi 0000:03:00.0: 0x843B44CE | interruptlink1
Feb 17 14:52:47.976820 myhost kernel: iwlwifi 0000:03:00.0: 0xF5B74773 | interruptlink2
Feb 17 14:52:47.977351 myhost kernel: iwlwifi 0000:03:00.0: 0x81EBFB5D | data1
Feb 17 14:52:47.977989 myhost kernel: iwlwifi 0000:03:00.0: 0x7CF7BFBD | data2
Feb 17 14:52:47.978651 myhost kernel: iwlwifi 0000:03:00.0: 0x7FD09E7B | data3
Feb 17 14:52:47.979285 myhost kernel: iwlwifi 0000:03:00.0: 0xF11868FF | beacon time
Feb 17 14:52:47.979961 myhost kernel: iwlwifi 0000:03:00.0: 0xFD9FEFC5 | tsf low
Feb 17 14:52:47.980614 myhost kernel: iwlwifi 0000:03:00.0: 0x6A2FFBCF | tsf hi
Feb 17 14:52:47.981158 myhost kernel: iwlwifi 0000:03:00.0: 0x7FFE24FB | time gp1
Feb 17 14:52:47.981767 myhost kernel: iwlwifi 0000:03:00.0: 0xAB6AED9D | time gp2
Feb 17 14:52:47.982411 myhost kernel: iwlwifi 0000:03:00.0: 0xF77FEFAD | uCode revision type
Feb 17 14:52:47.983068 myhost kernel: iwlwifi 0000:03:00.0: 0x937EEF49 | uCode version major
Feb 17 14:52:47.983691 myhost kernel: iwlwifi 0000:03:00.0: 0x7FEF9DFB | uCode version minor
Feb 17 14:52:47.984314 myhost kernel: iwlwifi 0000:03:00.0: 0x6FFEAFB6 | hw version
Feb 17 14:52:47.984988 myhost kernel: iwlwifi 0000:03:00.0: 0xE5CFBA1C | board version
Feb 17 14:52:47.985662 myhost kernel: iwlwifi 0000:03:00.0: 0xBA8FFF6F | hcmd
Feb 17 14:52:47.986319 myhost kernel: iwlwifi 0000:03:00.0: 0xDCE09D9D | isr0
Feb 17 14:52:47.987039 myhost kernel: iwlwifi 0000:03:00.0: 0xBD93ABFD | isr1
Feb 17 14:52:47.987695 myhost kernel: iwlwifi 0000:03:00.0: 0xAEF78A9B | isr2
Feb 17 14:52:47.988248 myhost kernel: iwlwifi 0000:03:00.0: 0x97AB2B5E | isr3
Feb 17 14:52:47.988922 myhost kernel: iwlwifi 0000:03:00.0: 0x983FBD08 | isr4
Feb 17 14:52:47.989529 myhost kernel: iwlwifi 0000:03:00.0: 0xEFDEFFB4 | last cmd Id
Feb 17 14:52:47.990185 myhost kernel: iwlwifi 0000:03:00.0: 0xB3FF1FD7 | wait_event
Feb 17 14:52:47.990844 myhost kernel: iwlwifi 0000:03:00.0: 0xB925FBD8 | l2p_control
Feb 17 14:52:47.991509 myhost kernel: iwlwifi 0000:03:00.0: 0xFEC5EECF | l2p_duration
Feb 17 14:52:47.992196 myhost kernel: iwlwifi 0000:03:00.0: 0x3E33E9F7 | l2p_mhvalid
Feb 17 14:52:47.992824 myhost kernel: iwlwifi 0000:03:00.0: 0xF795BD9C | l2p_addr_match
Feb 17 14:52:47.993498 myhost kernel: iwlwifi 0000:03:00.0: 0x7D6D2EBF | lmpm_pmg_sel
Feb 17 14:52:47.994147 myhost kernel: iwlwifi 0000:03:00.0: 0xB7859FE7 | timestamp
Feb 17 14:52:47.994752 myhost kernel: iwlwifi 0000:03:00.0: 0xFBBFFCBE | flow_handler
Feb 17 14:52:47.995314 myhost kernel: iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
Feb 17 14:52:47.995864 myhost kernel: iwlwifi 0000:03:00.0: Transport status: 0x00000042, valid: -44435459
Feb 17 14:52:47.996393 myhost kernel: iwlwifi 0000:03:00.0: 0x6EBF369D | ADVANCED_SYSASSERT
Feb 17 14:52:47.997025 myhost kernel: iwlwifi 0000:03:00.0: 0x37BD6FF5 | umac branchlink1
Feb 17 14:52:47.997549 myhost kernel: iwlwifi 0000:03:00.0: 0x5ABA5FF9 | umac branchlink2
Feb 17 14:52:47.998106 myhost kernel: iwlwifi 0000:03:00.0: 0xDFFD3FFF | umac interruptlink1
Feb 17 14:52:47.998664 myhost kernel: iwlwifi 0000:03:00.0: 0xB29262FF | umac interruptlink2
Feb 17 14:52:47.999252 myhost kernel: iwlwifi 0000:03:00.0: 0x3CACF7A9 | umac data1
Feb 17 14:52:47.999810 myhost kernel: iwlwifi 0000:03:00.0: 0x88539147 | umac data2
Feb 17 14:52:48.000312 myhost kernel: iwlwifi 0000:03:00.0: 0xEFBD7C73 | umac data3
Feb 17 14:52:48.000846 myhost kernel: iwlwifi 0000:03:00.0: 0x83E688F1 | umac major
Feb 17 14:52:48.001335 myhost kernel: iwlwifi 0000:03:00.0: 0xE77C75D6 | umac minor
Feb 17 14:52:48.001874 myhost kernel: iwlwifi 0000:03:00.0: 0xEC71C216 | frame pointer
Feb 17 14:52:48.002398 myhost kernel: iwlwifi 0000:03:00.0: 0x73F3F836 | stack pointer
Feb 17 14:52:48.002910 myhost kernel: iwlwifi 0000:03:00.0: 0xC31CA577 | last host cmd
Feb 17 14:52:48.003421 myhost kernel: iwlwifi 0000:03:00.0: 0x47F3F17D | isr status reg
Feb 17 14:52:48.003949 myhost kernel: iwlwifi 0000:03:00.0: IML/ROM dump:
Feb 17 14:52:48.004523 myhost kernel: iwlwifi 0000:03:00.0: 0x00000000 | IML/ROM error/state
Feb 17 14:52:48.005057 myhost kernel: iwlwifi 0000:03:00.0: 0x00000000 | IML/ROM data1
Feb 17 14:52:48.005546 myhost kernel: iwlwifi 0000:03:00.0: 0x00000000 | IML/ROM WFPM_AUTH_KEY_0
Feb 17 14:52:48.006062 myhost kernel: iwlwifi 0000:03:00.0: Fseq Registers:
Feb 17 14:52:48.006553 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_ERROR_CODE
Feb 17 14:52:48.007095 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_TOP_INIT_VERSION
Feb 17 14:52:48.007614 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVIO_INIT_VERSION
Feb 17 14:52:48.008117 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_OTP_VERSION
Feb 17 14:52:48.008613 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_TOP_CONTENT_VERSION
Feb 17 14:52:48.009122 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_ALIVE_TOKEN
Feb 17 14:52:48.009631 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVI_ID
Feb 17 14:52:48.010148 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CNVR_ID
Feb 17 14:52:48.010687 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVI_AUX_MISC_CHIP
Feb 17 14:52:48.011210 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVR_AUX_MISC_CHIP
Feb 17 14:52:48.011727 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
Feb 17 14:52:48.012205 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
Feb 17 14:52:48.012726 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_PREV_CNVIO_INIT_VERSION
Feb 17 14:52:48.013265 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_WIFI_FSEQ_VERSION
Feb 17 14:52:48.013798 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_BT_FSEQ_VERSION
Feb 17 14:52:48.014292 myhost kernel: iwlwifi 0000:03:00.0: 0xA5A5A5A2 | FSEQ_CLASS_TP_VERSION
Feb 17 14:52:48.014791 myhost kernel: iwlwifi 0000:03:00.0: UMAC CURRENT PC: 0xa5a5a5a2
Feb 17 14:52:48.015266 myhost kernel: iwlwifi 0000:03:00.0: LMAC1 CURRENT PC: 0xa5a5a5a2
Feb 17 14:52:48.015780 myhost kernel: iwlwifi 0000:03:00.0: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
Feb 17 14:52:48.016284 myhost kernel: usb 3-4: reset full-speed USB device number 3 using xhci_hcd
Feb 17 14:52:48.016807 myhost kernel: ata2: SATA link down (SStatus 0 SControl 300)
Feb 17 14:52:48.016866 myhost kernel: ata1: SATA link down (SStatus 0 SControl 300)
Feb 17 14:52:48.016917 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:2 (0x1001)
Feb 17 14:52:48.016978 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:1 (0x1001)
Feb 17 14:52:48.017038 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:4 (0x1001)
Feb 17 14:52:48.017089 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:6 (0x1001)
Feb 17 14:52:48.017138 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:7 (0x1001)
Feb 17 14:52:48.017192 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:8 (0x1001)
Feb 17 14:52:48.017247 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:3 (0x1001)
Feb 17 14:52:48.017298 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:9 (0x1001)
Feb 17 14:52:48.017348 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:10 (0x1001)
Feb 17 14:52:48.017405 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:12 (0x1001)
Feb 17 14:52:48.017454 myhost kernel: usb 3-3: reset high-speed USB device number 2 using xhci_hcd
Feb 17 14:52:48.017991 myhost kernel: amdgpu 0000:07:00.0: amdgpu: reserve 0x400000 from 0xf41f800000 for PSP TMR
Feb 17 14:52:48.018529 myhost kernel: amdgpu 0000:07:00.0: amdgpu: RAS: optional ras ta ucode is not available
Feb 17 14:52:48.019052 myhost kernel: amdgpu 0000:07:00.0: amdgpu: RAP: optional rap ta ucode is not available
Feb 17 14:52:48.019551 myhost kernel: amdgpu 0000:07:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Feb 17 14:52:48.020081 myhost kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resuming...
Feb 17 14:52:48.020581 myhost kernel: amdgpu 0000:07:00.0: amdgpu: dpm has been disabled
Feb 17 14:52:48.021101 myhost kernel: amdgpu 0000:07:00.0: amdgpu: SMU is resumed successfully!
Feb 17 14:52:48.021632 myhost kernel: [drm] kiq ring mec 2 pipe 1 q 0
Feb 17 14:52:48.021697 myhost kernel: [drm] DMUB hardware initialized: version=0x0101002B
Feb 17 14:52:48.021756 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
Feb 17 14:52:48.022270 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Feb 17 14:52:48.022799 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Feb 17 14:52:48.023300 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
Feb 17 14:52:48.023820 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
Feb 17 14:52:48.024326 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
Feb 17 14:52:48.024845 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
Feb 17 14:52:48.025341 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
Feb 17 14:52:48.025869 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
Feb 17 14:52:48.026374 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
Feb 17 14:52:48.026915 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
Feb 17 14:52:48.027422 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
Feb 17 14:52:48.027954 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
Feb 17 14:52:48.028445 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
Feb 17 14:52:48.028968 myhost kernel: amdgpu 0000:07:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
Feb 17 14:52:48.029460 myhost kernel: OOM killer enabled.
Feb 17 14:52:48.029520 myhost kernel: Restarting tasks ... 
Feb 17 14:52:48.029590 myhost kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
Feb 17 14:52:48.029679 myhost kernel: Bluetooth: hci0: Device revision is 1
Feb 17 14:52:48.029743 myhost kernel: Bluetooth: hci0: Secure boot is enabled
Feb 17 14:52:48.029793 myhost kernel: Bluetooth: hci0: OTP lock is enabled
Feb 17 14:52:48.029842 myhost kernel: Bluetooth: hci0: API lock is enabled
Feb 17 14:52:48.029885 myhost kernel: Bluetooth: hci0: Debug lock is disabled
Feb 17 14:52:48.029939 myhost kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Feb 17 14:52:48.029999 myhost kernel: done.
Feb 17 14:52:48.030060 myhost kernel: random: crng reseeded on system resumption
Feb 17 14:52:48.030118 myhost kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Feb 17 14:52:48.030170 myhost kernel: Bluetooth: hci0: Boot Address: 0x24800
Feb 17 14:52:48.030230 myhost kernel: Bluetooth: hci0: Firmware Version: 132-3.24
Feb 17 14:52:48.030279 myhost kernel: PM: suspend exit
Feb 17 14:52:48.866638 myhost kernel: Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
Feb 17 14:52:49.008776 myhost kernel: r8169 0000:02:00.0 eno1: Link is Down
Feb 17 14:52:49.237653 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:2 (0x1001)
Feb 17 14:52:49.237885 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:1 (0x1001)
Feb 17 14:52:49.237957 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:4 (0x1001)
Feb 17 14:52:49.238023 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:6 (0x1001)
Feb 17 14:52:49.238082 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:7 (0x1001)
Feb 17 14:52:49.238132 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:8 (0x1001)
Feb 17 14:52:49.238221 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:3 (0x1001)
Feb 17 14:52:49.238361 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:9 (0x1001)
Feb 17 14:52:49.238456 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:10 (0x1001)
Feb 17 14:52:49.238540 myhost kernel: ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:12 (0x1001)
Feb 17 14:52:49.712682 myhost kernel: Bluetooth: hci0: Waiting for firmware download to complete
Feb 17 14:52:49.712942 myhost kernel: Bluetooth: hci0: Firmware loaded in 1701566 usecs
Feb 17 14:52:49.712993 myhost kernel: Bluetooth: hci0: Waiting for device to boot
Feb 17 14:52:49.728675 myhost kernel: Bluetooth: hci0: Device booted in 14879 usecs
Feb 17 14:52:49.728941 myhost kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
Feb 17 14:52:49.733630 myhost kernel: Bluetooth: hci0: Applying Intel DDC parameters completed
Feb 17 14:52:49.736639 myhost kernel: Bluetooth: hci0: Firmware revision 0.3 build 132 week 3 2024
Feb 17 14:52:49.743677 myhost kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
Feb 17 14:52:53.002754 myhost kernel: wlo1: authenticate with 40:e3:d6:57:8e:80 (local address=e0:d4:e8:33:c3:f9)
Feb 17 14:52:53.003644 myhost kernel: wlo1: send auth to 40:e3:d6:57:8e:80 (try 1/3)
Feb 17 14:52:53.030929 myhost kernel: wlo1: authenticated
Feb 17 14:52:53.032630 myhost kernel: wlo1: associate with 40:e3:d6:57:8e:80 (try 1/3)
Feb 17 14:52:53.136696 myhost kernel: wlo1: associate with 40:e3:d6:57:8e:80 (try 2/3)
Feb 17 14:52:53.137663 myhost kernel: wlo1: RX AssocResp from 40:e3:d6:57:8e:80 (capab=0x431 status=0 aid=3)
Feb 17 14:52:53.146647 myhost kernel: wlo1: associated

Offline

#2 2025-02-18 08:39:33

seth
Member
Registered: 2012-09-03
Posts: 61,589

Re: iwlwifi causes everything to stop working

Feb 17 14:52:47.962585 myhost kernel: ACPI: PM: Preparing to enter system sleep state S3
Feb 17 14:52:47.967239 myhost kernel: amdgpu 0000:07:00.0: amdgpu: PSP is resuming...
Feb 17 14:52:47.971191 myhost kernel: iwlwifi 0000:03:00.0: HW error, resetting before reading
Feb 17 14:52:48.030279 myhost kernel: PM: suspend exit
Feb 17 14:52:53.146647 myhost kernel: wlo1: associated

That journal snippet shows you sending the system to sleep for a second, the iwlwifi firmware crashes on wake but recovers and you connect to the AP.
There's no indication or reason of "apps start closing 1 by 1" while "returns an input/output error" suggests you're loosing the root partition.

1st off, in case there's a parallel windows installation, see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

There're suspend related caveats reg. nvme's and APST and recently a bunch of sub-par SSDs where over-optimistically afforded DIPM ALPM, but the journal does not (and in case you're loosing the partition you're storing it on: cannot) indicate any of this.

hacky solution that I could do every time I booted and I've basically been doing that

Are you currently doing that and in case you don't: does your wifi break but you get to keep the root partition?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2025-02-18 10:41:03

Humblenoise4
Member
Registered: 2024-12-21
Posts: 8

Re: iwlwifi causes everything to stop working

seth wrote:

That journal snippet shows you sending the system to sleep for a second, the iwlwifi firmware crashes on wake but recovers and you connect to the AP. There's no indication or reason of "apps start closing 1 by 1" while "returns an input/output error" suggests you're loosing the root partition.

Huh, okay that's odd that there aren't signs of anything off in the logs. Those are the only logs from around the time of the issue.

seth wrote:

1st off, in case there's a parallel windows installation, see the 3rd link below. Mandatory. Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I do run a dual-boot (with Windows and Linux being on separate drives), but Windows fast-start was already disabled a long time ago. At least, I had disabled it in the Control Panel, but I have just done it again in the other way using the command line that the Wiki suggested, just in case they don't do the exact same thing.

seth wrote:

Are you currently doing that and in case you don't: does your wifi break but you get to keep the root partition?

Yeah, so I am still doing it. If I don't do it, my WiFi stops working if I suspend my laptop and then wake it up again. As far as your second question goes, I don't really know, I haven't tested it. It's not the easiest thing to test because, although the WiFi issue is very easy to reproduce (I just have to reboot and suspend my laptop), the other issue sort of just happens randomly like once a day. So in order to test it, I'd have to ensure that it wouldn't suspend for a full day or two, which I might try (or alternatively, use my laptop without WiFi for a day or two, but that's a lot less convenient). But could it really be the case that removing the network card and triggering a rescan could cause my system to break like a full day later?

Maybe I should also mention that although the WiFi issue happens immediately after waking up from suspend, the other issue happens, as far as I can tell, completely randomly. Like, I'll just be using my laptop normally and suddenly my programs will just start closing one by one.

Offline

#4 2025-02-18 12:59:44

seth
Member
Registered: 2012-09-03
Posts: 61,589

Re: iwlwifi causes everything to stop working

just in case they don't do the exact same thing

I suppose they do, but windows has an ugly habit to re-activate the feature w/ updates (in case you set that by accident, I guess roll)

I'd have to ensure that it wouldn't suspend for a full day or two

This is only gonna be relevant on resume from sleeps, I assume (as that seems when the issue emerged?)

rescan could cause my system to break like a full day later?

Unlikely, but it's the event in your journal snippet and your subject links these things as well.
According to a clock on your wall: when was the last time the major problem occurred?

Keep "dmesg -W" running in some terminal, maybe you can spot the error there the next time it happens.
My money is on disk related power saving features, either https://wiki.archlinux.org/title/Solid_ … leshooting or https://wiki.archlinux.org/title/Solid_ … leshooting (but your journal snippet doesn't reveal anything about the root device)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2025-02-18 21:06:31

Humblenoise4
Member
Registered: 2024-12-21
Posts: 8

Re: iwlwifi causes everything to stop working

seth wrote:

This is only gonna be relevant on resume from sleeps, I assume (as that seems when the issue emerged?).

I'm not really sure of this. I mean, certainly this is the case for the WiFi issue and I threw it out there that the issues might be related to each other, but truly, I have no idea.

What I am sure about is that the issue does not necessarily occur immediately after waking up from suspend. I know the snippet of the logs that I sent says that there was a suspend, but then I suppose that it could be the case that those logs are from at least a few minutes before the actual issue happened and for whatever reason, there are no logs about what actually happened (the logs I sent were the last ones from the session where it happened). I say this, because I remember what I was doing when the issue happened; I was in the middle of writing some code, so it couldn't have happened immediately after waking up from suspend.

It also happened before once in the middle of a conversation with someone, where I was actively using my laptop to show them some stuff, so again, definitely not something that exclusively happens right after waking up from suspend. Not that I'm saying that it's definitely not a suspend issue because it doesn't happen right after; I have no idea about what the characteristic time for a suspend issue is tongue

seth wrote:

According to a clock on your wall: when was the last time the major problem occurred?

It hasn't happened since the time of the logs (and the time of the logs is definitely not completely off, I mean, I started looking at the logs from the previous session immediately after powering off and powering back on my laptop so I know it was definitely close to the time that is says on the logs. But as mentioned, it could definitely be that it happened a few minutes after what the logs say, I did not keep track of time that closely.

seth wrote:

Keep "dmesg -W" running in some terminal, maybe you can spot the error there the next time it happens.
My money is on disk related power saving features, either https://wiki.archlinux.org/title/Solid_ … leshooting or https://wiki.archlinux.org/title/Solid_ … leshooting (but your journal snippet doesn't reveal anything about the root device)

These links seem promising, given that they mention HP laptops with AMD CPUs and also Samsung NVME drives, all three of which describe the system I'm running. I'll try some of the suggestions in these links and keep a lookout for any issues. I think the longest I have gone without the issue occurring is like 3-4 days, so it might take a while to confirm if any of these solutions worked.

Thank you very much!

EDIT: I also took a stab at trying to fix the WiFi issue again and indeed, it seems that I have fixed it now. The fix I found was actually posted by you, so thanks for that also!

Last edited by Humblenoise4 (2025-02-18 22:24:11)

Offline

Pages: 1

Board footer

Powered by FluxBB