Issue waking from sleep

Histole · 2025-10-03 00:00:54

Ran into this issue today, I can't figure out what caused it, but after waking from sleep I see these errors on the screen, and I can't go to another TTY, its frozen, I have to force shutdown the computer. Never happened before it would always boot up just fine from sleep. But today this issue appeared, and it's repeatable, happens every time.

Am on latest zen kernel

Last edited by Histole (2026-06-16 18:10:07)

seth · 2025-10-03 14:59:17

blacklist mei_me - did you recently update the system? Or the firmware?
Is there a parallel OS (windows)?

I have to force shutdown the computer.

Avoid that at all costs to hopefully preserve the journal, in doubt activate and use the https://wiki.archlinux.org/title/Keyboa … el_(SysRq)

Histole · 2025-10-03 15:23:41

seth wrote:

blacklist mei_me - did you recently update the system? Or the firmware?
Is there a parallel OS (windows)?]

I was on windows recently yes, I did not update any drivers or anything that I know of. Really odd behaviour, do you think it has to do with the usb errors freaking out? I'll try to get a full log and paste it here.

Thank you.

seth · 2025-10-03 18:31:51

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

The usb errors might just be down to

[ 2013.626499] xhci_hcd 0000:05:00.0: xHC error in resume, USBSTS 0x401, Reinit

Histole · 2025-10-03 23:10:03

seth wrote:

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I already have this disabled.

The usb errors might just be down to
[ 2013.626499] xhci_hcd 0000:05:00.0: xHC error in resume, USBSTS 0x401, Reinit

Last edited by Histole (2026-06-16 18:10:40)

Histole · 2025-10-03 23:43:03

It looks like after changing my mirrorlist to 08/10/25 and running

sudo pacman -Syyuu

the issue goes away.

Really wish arch was more stable at times. Something broke possibly in an update?

Last edited by Histole (2025-10-03 23:43:46)

killertofus · 2025-10-04 00:36:36

Use -Syu not -Syyuu as it can increase load on server bandwidth and should only be done in some situation when you suspect something wrong with db.

Histole · 2025-10-04 00:40:46

killertofus wrote:

Use -Syu not -Syyuu as it can increase load on server bandwidth and should only be done in some situation when you suspect something wrong with db.

Will do.

seth · 2025-10-04 08:51:53

@killertofus, the OP did https://wiki.archlinux.org/title/Arch_L … cific_date in which case -Syyuu is strictly necessary.
@Histole, the idea was to use sysrq+REISUB out of the failign wakeup and then post the journal of the previous boot (the one w/ the troublesome wakeup)

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

Histole · 2025-10-06 03:37:45

seth wrote:

@killertofus, the OP did https://wiki.archlinux.org/title/Arch_L … cific_date in which case -Syyuu is strictly necessary.
@Histole, the idea was to use sysrq+REISUB out of the failign wakeup and then post the journal of the previous boot (the one w/ the troublesome wakeup)
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

Managed to recover from the hardlock this time, I pressed the power button and for some reason it let me log back in. I just got the dmesg.

Last edited by Histole (2026-06-16 18:09:53)

seth · 2025-10-06 14:05:38

[Edit: the code blocks are the complete system messages after triggering sleep, wakeup and hitting the mei_me errors]

[12354.184938] PM: suspend entry (deep)
[12354.573719] Filesystems sync: 0.388 seconds
[12354.711558] Freezing user space processes
[12354.712660] Freezing user space processes completed (elapsed 0.001 seconds)
[12354.712662] OOM killer disabled.
[12354.712663] Freezing remaining freezable tasks
[12354.713623] Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
[12354.713654] printk: Suspending console(s) (use no_console_suspend to debug)
[12354.726531] e1000e: EEE TX LPI TIMER: 00000011
[12354.736801] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[12354.739517] ata1.00: Entering standby power mode
[12354.982007] ACPI: EC: interrupt blocked
[12355.018493] ACPI: PM: Preparing to enter system sleep state S3
[12355.225265] ACPI: EC: event blocked
[12355.225271] ACPI: EC: EC stopped
[12355.225273] ACPI: PM: Saving platform NVS memory
[12355.225448] Disabling non-boot CPUs ...
[12355.230669] smpboot: CPU 15 is now offline
[12355.236442] smpboot: CPU 14 is now offline
[12355.240596] smpboot: CPU 13 is now offline
[12355.246816] smpboot: CPU 12 is now offline
[12355.250727] smpboot: CPU 11 is now offline
[12355.255235] smpboot: CPU 10 is now offline
[12355.259658] smpboot: CPU 9 is now offline
[12355.265661] smpboot: CPU 8 is now offline
[12355.269533] smpboot: CPU 7 is now offline
[12355.273131] smpboot: CPU 6 is now offline
[12355.276665] smpboot: CPU 5 is now offline
[12355.280321] smpboot: CPU 4 is now offline
[12355.283457] smpboot: CPU 3 is now offline
[12355.286697] smpboot: CPU 2 is now offline
[12355.290188] smpboot: CPU 1 is now offline
[12355.294728] ACPI: PM: Low-level resume complete
[12355.294770] ACPI: EC: EC started
[12355.294770] ACPI: PM: Restoring platform NVS memory
[12355.295567] Enabling non-boot CPUs ...
[12355.295607] smpboot: Booting Node 0 Processor 1 APIC 0x2
[12355.299140] CPU1 is up
[12355.299165] smpboot: Booting Node 0 Processor 2 APIC 0x4
[12355.300426] CPU2 is up
[12355.300450] smpboot: Booting Node 0 Processor 3 APIC 0x6
[12355.301731] CPU3 is up
[12355.301755] smpboot: Booting Node 0 Processor 4 APIC 0x8
[12355.303069] CPU4 is up
[12355.303107] smpboot: Booting Node 0 Processor 5 APIC 0xa
[12355.304431] CPU5 is up
[12355.304455] smpboot: Booting Node 0 Processor 6 APIC 0xc
[12355.305817] CPU6 is up
[12355.305840] smpboot: Booting Node 0 Processor 7 APIC 0xe
[12355.307226] CPU7 is up
[12355.307249] smpboot: Booting Node 0 Processor 8 APIC 0x1
[12355.308087] CPU8 is up
[12355.308114] smpboot: Booting Node 0 Processor 9 APIC 0x3
[12355.308836] CPU9 is up
[12355.308860] smpboot: Booting Node 0 Processor 10 APIC 0x5
[12355.309605] CPU10 is up
[12355.309632] smpboot: Booting Node 0 Processor 11 APIC 0x7
[12355.310396] CPU11 is up
[12355.310419] smpboot: Booting Node 0 Processor 12 APIC 0x9
[12355.311197] CPU12 is up
[12355.311221] smpboot: Booting Node 0 Processor 13 APIC 0xb
[12355.312045] CPU13 is up
[12355.312068] smpboot: Booting Node 0 Processor 14 APIC 0xd
[12355.312906] CPU14 is up
[12355.312930] smpboot: Booting Node 0 Processor 15 APIC 0xf
[12355.313788] CPU15 is up

[12355.317474] ACPI: PM: Waking up from system sleep state S3
[12355.327775] ACPI: EC: interrupt unblocked
[12355.342501] ACPI: EC: event unblocked
[12355.343548] xhci_hcd 0000:00:14.0: xHC error in resume, USBSTS 0x411, Reinit
[12355.343550] usb usb1: root hub lost power or was reset
[12355.343551] usb usb2: root hub lost power or was reset
[12355.343801] xhci_hcd 0000:05:00.0: xHC error in resume, USBSTS 0x401, Reinit
[12355.343803] usb usb3: root hub lost power or was reset
[12355.343804] usb usb4: root hub lost power or was reset
[12355.421086] nvme nvme1: D3 entry latency set to 10 seconds
[12355.421339] nvme nvme0: D3 entry latency set to 8 seconds
[12355.423654] nvme nvme1: 16/0/0 default/read/poll queues
[12355.439241] nvme nvme0: 16/0/0 default/read/poll queues
[12355.492988] usb 1-11: WARN: invalid context state for evaluate context command.
[12355.549229] usb 3-1: WARN: invalid context state for evaluate context command.
[12355.604937] usb 1-11: reset full-speed USB device number 6 using xhci_hcd
[12355.663272] ata6: SATA link down (SStatus 4 SControl 300)
[12355.663327] ata4: SATA link down (SStatus 4 SControl 300)
[12355.663346] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[12355.663358] ata3: SATA link down (SStatus 4 SControl 300)
[12355.663372] ata5: SATA link down (SStatus 4 SControl 300)
[12355.663385] ata2: SATA link down (SStatus 4 SControl 300)
[12355.663522] sd 0:0:0:0: [sda] Starting disk
[12355.663655] ata1.00: configured for UDMA/133
[12355.721933] usb 3-1: reset full-speed USB device number 5 using xhci_hcd
[12355.728077] usb 1-8: WARN: invalid context state for evaluate context command.
[12355.839944] usb 1-8: reset full-speed USB device number 5 using xhci_hcd
[12356.370208] usb 1-14: WARN: invalid context state for evaluate context command.
[12356.482087] usb 1-14: reset full-speed USB device number 8 using xhci_hcd
[12356.605393] usb 1-7: WARN: invalid context state for evaluate context command.
[12356.717092] usb 1-7: reset full-speed USB device number 3 using xhci_hcd
[12356.952113] usb 1-2: reset high-speed USB device number 2 using xhci_hcd
[12357.188109] usb 1-13: reset high-speed USB device number 7 using xhci_hcd
[12357.435063] usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
[12357.533153] usb 1-13.2: WARN: invalid context state for evaluate context command.
[12357.595103] usb 1-13.2: reset full-speed USB device number 10 using xhci_hcd
[12357.742152] usb 1-13.1: reset high-speed USB device number 9 using xhci_hcd
[12357.826530] usb 1-13.3: WARN: invalid context state for evaluate context command.
[12357.899157] usb 1-13.3: reset full-speed USB device number 11 using xhci_hcd
[12358.053175] usb 1-13.1.4: WARN: invalid context state for evaluate context command.
[12358.115100] usb 1-13.1.4: reset full-speed USB device number 12 using xhci_hcd
[12359.382840] e1000e 0000:00:1f.6 eno2: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

[12362.770246] mei_me 0000:00:16.0: wait hw ready failed
[12362.770273] mei_me 0000:00:16.0: hw_start failed ret = -62 fw status = 80002144 36850106 00000020 00004804 00000000 40000000
[12362.770325] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING fw status = 80002144 36850106 00000020 00004804 00000000 40000000
[12362.770342] mei_me 0000:00:16.0: H_RST is set = 0x80080831
[12362.772517] OOM killer enabled.
[12362.772524] Restarting tasks: Starting
[12362.777991] Restarting tasks: Done
[12362.778214] random: crng reseeded on system resumption
[12362.778235] PM: suspend exit
[12362.778468] Bluetooth: hci0: Found device firmware: intel/ibt-17-16-1.sfi
[12362.778535] Bluetooth: hci0: Boot Address: 0x40800
[12362.778537] Bluetooth: hci0: Firmware Version: 201-12.24
[12362.778538] Bluetooth: hci0: Firmware already loaded
[12362.780517] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
[12362.838601] Bluetooth: MGMT ver 1.23
[12364.185145] e1000e 0000:00:1f.6 eno2: NIC Link is Down
[12364.782809] mei_me 0000:00:16.0: wait hw ready failed
[12364.782850] mei_me 0000:00:16.0: hw_start failed ret = -62 fw status = 80002144 36850106 00000020 00004804 00000000 40000000
[12364.782889] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING fw status = 80002144 36850106 00000020 00004804 00000000 40000000
[12364.782907] mei_me 0000:00:16.0: H_RST is set = 0x80080831
[12366.792646] mei_me 0000:00:16.0: wait hw ready failed
[12366.792680] mei_me 0000:00:16.0: hw_start failed ret = -62 fw status = 80002144 36850106 00000020 00004804 00000000 40000000
[12366.792713] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING fw status = 80002144 36850106 00000020 00004804 00000000 40000000
[12366.792728] mei_me 0000:00:16.0: reset: reached maximal consecutive resets: disabling the device
[12366.792750] mei_me 0000:00:16.0: device disabled = -19
[12367.820384] e1000e 0000:00:1f.6 eno2: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

seth wrote:

blacklist mei_me

Other than that

[12355.492988] usb 1-11: WARN: invalid context state for evaluate context command.
[12355.549229] usb 3-1: WARN: invalid context state for evaluate context command.
[12355.728077] usb 1-8: WARN: invalid context state for evaluate context command.
[12356.370208] usb 1-14: WARN: invalid context state for evaluate context command.
[12356.605393] usb 1-7: WARN: invalid context state for evaluate context command.
[12357.533153] usb 1-13.2: WARN: invalid context state for evaluate context command.
[12357.826530] usb 1-13.3: WARN: invalid context state for evaluate context command.
[12358.053175] usb 1-13.1.4: WARN: invalid context state for evaluate context command.

looks a bit concerning but affects a lot of devices

Last edited by seth (2025-10-06 14:06:39)

Histole · 2025-10-06 14:12:58

seth wrote:

blacklist mei_me

You're suggesting to blacklist the mei? Would this cause more issues? Will be honest, not too sure what the logs are saying. Don't understand them at all.

seth · 2025-10-06 14:16:44

https://wiki.archlinux.org/index.php?ti … rch=mei_me actually has this as workaround on various systemd, the thing is https://en.wikipedia.org/wiki/Intel_Management_Engine and not strictly required for proper function.
In the rare case this might lead to an unbootable system: make sure to only transiently edit the kernel commandline at the bootloader for the tests ("cat /proc/meminfo; lsmod | grep mei" will show whether it worked) - the blacklisting would automatically be dropped w/ a reboot.

Histole · 2025-10-06 15:34:03

seth wrote:

https://wiki.archlinux.org/index.php?ti … rch=mei_me actually has this as workaround on various systemd, the thing is https://en.wikipedia.org/wiki/Intel_Management_Engine and not strictly required for proper function.
In the rare case this might lead to an unbootable system: make sure to only transiently edit the kernel commandline at the bootloader for the tests ("cat /proc/meminfo; lsmod | grep mei" will show whether it worked) - the blacklisting would automatically be dropped w/ a reboot.

Even after blacklisting MEI, seems that it still occurs. Though if I press the power button while the errors are up on the screen, it shows my login screen.
I did try out a base fedora install and this didn't occur. Clean installed Arch and this persists. If I roll back my mirrorlist to August it seemingly goes away. I really have no idea what the issue is here.

Thank you though for the help.

Last edited by Histole (2026-06-16 18:09:27)

seth · 2025-10-06 18:53:38

There's something new, though:

[ 1828.853366] NVRM: GPU at PCI:0000:01:00: GPU-9241288b-0f2c-cec6-2dc5-ccae8af929fc
[ 1828.853387] NVRM: Xid (PCI:0000:01:00): 69, pid=1336, name=Discord, Class Error: channel 0x00000025, Class 0000902d, Offset 0000023c, Data 00000000, ErrorCode 00000004

which can be a HW or driver error

[    9.428556] NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  580.82.09  Release Build  (root@)

Do you also have problems w/ the non-open nvidia kernel module?

Histole · 2025-10-07 04:18:10

seth wrote:

[    9.428556] NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  580.82.09  Release Build  (root@)  
Do you also have problems w/ the non-open nvidia kernel module?

Yes, it acts the same on the non open nvidia module. Here is another log, the errors keep changing. Though this time it was a softer lockup, it resums froms leep, shows those messages on the screen, then I press a key on the keyboard and I'm at my desktop.

Last edited by Histole (2026-06-16 18:08:39)

seth · 2025-10-07 08:53:36

[10901.832541] tpm tpm0: TPM_LOC_STATE_x.Relinquish timed out
[10901.832554] tpm tpm0: tpm_relinquish_locality: : error -62
[10912.086225] tpm tpm0: cmdReady timed out
…

Those are a lot of timeouts from tpm, is it actually the correlct url?
tpm is built-in, "module_blacklist=mei_me,tpm" might still work but in doubt disable the TPM in the UEFI settings

Histole · 2025-10-07 15:15:14

seth wrote:

[10901.832541] tpm tpm0: TPM_LOC_STATE_x.Relinquish timed out
[10901.832554] tpm tpm0: tpm_relinquish_locality: : error -62
[10912.086225] tpm tpm0: cmdReady timed out
…
Those are a lot of timeouts from tpm, is it actually the correlct url?
tpm is built-in, "module_blacklist=mei_me,tpm" might still work but in doubt disable the TPM in the UEFI settings

Should be the right log? I was a bit stunned as well, I just did dmesg > dmesg.log and uploaded it.

So do you have any ideas as to the root issue?

seth · 2025-10-07 15:28:31

I was more concerned that you might have posted the wrong URL
So we've had the MEI, the nvidia GPU and the TPM… can you post the complete journal of the previous (affected) boot?

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

(You might have to decrease "-1" for older journals if you've rebooted several times after the wakeup failure)

Might be ASPM, "pcie_aspm=off" - but that's a really wild guess because it looks like it's not a single device that's causing trouble.

Histole · 2025-10-07 17:28:28

seth wrote:

So we've had the MEI, the nvidia GPU and the TPM… can you post the complete journal of the previous (affected) boot?

Last edited by Histole (2026-06-16 18:08:54)

seth · 2025-10-07 19:33:56

Can we see a journal w/ mei_me blacklisted? It certainly flares up.
TPM timeouts start ~50s after the system woke up.

Oct 07 13:24:16 pc kwin_wayland[829]: kwin_wayland_drm: Atomic modeset test failed! Permission denied
Oct 07 13:24:16 pc kwin_wayland[829]: kwin_wayland_drm: Setting dpms mode failed!
Oct 07 13:24:16 pc kwin_wayland[829]: kwin_wayland_drm: Atomic modeset test failed! Permission denied
Oct 07 13:24:16 pc kwin_wayland[829]: kwin_wayland_drm: Setting dpms mode failed!
Oct 07 13:24:16 pc kwin_wayland[829]: kwin_wayland_drm: Atomic modeset test failed! Permission denied
Oct 07 13:24:16 pc kwin_wayland[829]: kwin_wayland_drm: Setting dpms mode failed!
Oct 07 13:24:16 pc kwin_wayland[829]: kwin_wayland_drm: Atomic modeset test failed! Permission denied
Oct 07 13:24:16 pc kwin_wayland[829]: kwin_wayland_drm: Setting dpms mode failed!

Do you run into similar problems w/ a plasma/X11 session?

Histole · 2025-10-07 20:48:31

seth wrote:

Can we see a journal w/ mei_me blacklisted? It certainly flares up.
TPM timeouts start ~50s after the system woke up.
Do you run into similar problems w/ a plasma/X11 session?

Last edited by Histole (2026-06-16 18:09:10)

seth · 2025-10-07 21:02:40

Oct 07 16:44:36 pc kernel: xhci_hcd 0000:00:14.0: xHC error in resume, USBSTS 0x411, Reinit
Oct 07 16:44:36 pc kernel: usb usb1: root hub lost power or was reset
Oct 07 16:44:36 pc kernel: usb usb2: root hub lost power or was reset
Oct 07 16:44:36 pc kernel: xhci_hcd 0000:05:00.0: xHC error in resume, USBSTS 0x401, Reinit
Oct 07 16:44:36 pc kernel: usb usb3: root hub lost power or was reset
Oct 07 16:44:36 pc kernel: usb usb4: root hub lost power or was reset
…
Oct 07 16:44:48 pc kernel: sysrq: Show Blocked State
Oct 07 16:44:48 pc kernel: task:openrgb         state:D stack:0     pid:2053  tgid:2052  ppid:2009   flags:0x00004002
Oct 07 16:44:48 pc kernel: Call Trace:
Oct 07 16:44:48 pc kernel:  <TASK>
Oct 07 16:44:48 pc kernel:  __schedule+0x3cc/0x12f0
Oct 07 16:44:48 pc kernel:  ? lock_timer_base+0x74/0x90
Oct 07 16:44:48 pc kernel:  schedule+0x27/0xf0
Oct 07 16:44:48 pc kernel:  schedule_timeout+0x9c/0x170
Oct 07 16:44:48 pc kernel:  ? usb_start_wait_urb+0xca/0x190
Oct 07 16:44:48 pc kernel:  ? __pfx_process_timeout+0x10/0x10
Oct 07 16:44:48 pc kernel:  msleep+0x2b/0x40
Oct 07 16:44:48 pc kernel:  usb_control_msg+0x12f/0x150
Oct 07 16:44:48 pc kernel:  usbhid_raw_request+0xb2/0x180 [usbhid 9594c5813b9cb21e1fdf1b1f9ed9135547fc471a]
Oct 07 16:44:48 pc kernel:  hidraw_get_report+0xd7/0x170
Oct 07 16:44:48 pc kernel:  hidraw_ioctl+0x2d9/0x3c0
Oct 07 16:44:48 pc kernel:  __x64_sys_ioctl+0x91/0xd0
Oct 07 16:44:48 pc kernel:  do_syscall_64+0x7b/0x190
Oct 07 16:44:48 pc kernel:  ? irqentry_exit_to_user_mode+0x2c/0x1b0
Oct 07 16:44:48 pc kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Oct 07 16:44:48 pc kernel: RIP: 0033:0x7344f351674d
Oct 07 16:44:48 pc kernel: RSP: 002b:00007344f08bd460 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Oct 07 16:44:48 pc kernel: RAX: ffffffffffffffda RBX: 0000000000410000 RCX: 00007344f351674d
Oct 07 16:44:48 pc kernel: RDX: 00007344f08bd6e0 RSI: 00000000c0414807 RDI: 000000000000000f
Oct 07 16:44:48 pc kernel: RBP: 00007344f08bd4b0 R08: 0000000000000000 R09: 0000000000000000
Oct 07 16:44:48 pc kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00007344e8070be0
Oct 07 16:44:48 pc kernel: R13: 00007344f08bd6e0 R14: 00007344e8070be0 R15: 000000000000010e
Oct 07 16:44:48 pc kernel:  </TASK>
Oct 07 16:44:57 pc kernel: sysrq: Show backtrace of all active CPUs
Oct 07 16:44:57 pc kernel: NMI backtrace for cpu 0
Oct 07 16:44:57 pc kernel: CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Tainted: P          IOE      6.12.50-1-lts #1 cecdae19e7ea1fbdba4754ff43561536db351b58
Oct 07 16:44:57 pc kernel: Tainted: [P]=PROPRIETARY_MODULE, [I]=FIRMWARE_WORKAROUND, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Oct 07 16:44:57 pc kernel: Hardware name: ASUS System Product Name/ROG MAXIMUS XI CODE, BIOS 2004 11/02/2021
Oct 07 16:44:57 pc kernel: Call Trace:
Oct 07 16:44:57 pc kernel:  <IRQ>
Oct 07 16:44:57 pc kernel:  dump_stack_lvl+0x5d/0x80
Oct 07 16:44:57 pc kernel:  nmi_cpu_backtrace.cold+0x18/0x65
Oct 07 16:44:57 pc kernel:  ? __pfx_nmi_raise_cpu_backtrace+0x10/0x10
Oct 07 16:44:57 pc kernel:  nmi_trigger_cpumask_backtrace+0xf3/0x110
Oct 07 16:44:57 pc kernel:  __handle_sysrq.cold+0xac/0xff
Oct 07 16:44:57 pc kernel:  sysrq_filter+0xd2/0x5b0
Oct 07 16:44:57 pc kernel:  input_handle_events_filter+0x42/0x90
Oct 07 16:44:57 pc kernel:  input_pass_values+0x134/0x170
Oct 07 16:44:57 pc kernel:  input_event_dispose+0x156/0x160
Oct 07 16:44:57 pc kernel:  input_event+0x59/0x70
Oct 07 16:44:57 pc kernel:  hidinput_report_event+0x37/0x50
Oct 07 16:44:57 pc kernel:  hid_report_raw_event+0xba/0x4c0
Oct 07 16:44:57 pc kernel:  __hid_input_report+0x14d/0x200
Oct 07 16:44:57 pc kernel:  hid_input_report+0x15/0x20
Oct 07 16:44:57 pc kernel:  hid_irq_in+0x1a1/0x1d0 [usbhid 9594c5813b9cb21e1fdf1b1f9ed9135547fc471a]
Oct 07 16:44:57 pc kernel:  __usb_hcd_giveback_urb+0x9d/0x120
Oct 07 16:44:57 pc kernel:  usb_giveback_urb_bh+0xc4/0x150
Oct 07 16:44:57 pc kernel:  process_one_work+0x17c/0x340
Oct 07 16:44:57 pc kernel:  bh_worker+0x1ac/0x210
Oct 07 16:44:57 pc kernel:  ? sched_clock_cpu+0xf/0x200
Oct 07 16:44:57 pc kernel:  tasklet_hi_action+0x13/0x30
Oct 07 16:44:57 pc kernel:  handle_softirqs+0xdb/0x290
Oct 07 16:44:57 pc kernel:  __irq_exit_rcu+0x9c/0xc0
Oct 07 16:44:57 pc kernel:  common_interrupt+0x85/0xa0
Oct 07 16:44:57 pc kernel:  </IRQ>
Oct 07 16:44:57 pc kernel:  <TASK>
Oct 07 16:44:57 pc kernel:  asm_common_interrupt+0x26/0x40
Oct 07 16:44:57 pc kernel: RIP: 0010:cpuidle_enter_state+0xbb/0x410

Oct 07 16:44:48 pc kernel: task:openrgb         state:D stack:0     pid:2053  tgid:2052  ppid:2009   flags:0x00004002

Some USB device illumination, https://archlinux.org/packages/extra/x86_64/openrgb/

Histole · 2025-10-07 21:21:24

seth wrote:

Oct 07 16:44:48 pc kernel: task:openrgb         state:D stack:0     pid:2053  tgid:2052  ppid:2009   flags:0x00004002
Some USB device illumination, https://archlinux.org/packages/extra/x86_64/openrgb/

Running

pacman -Rns openrgb

fixes the issue, it correctly resumes from sleep. Seems to be repeatable. Though now I am confused, running

ps aux | grep openrgb

shows no processes of openrgb, so how is it showing up in the logs I had uploaded? I'm puzzled.

I wonder if an update of openrgb broke it on my system? As the August mirrorlist works. Though regardless, it shouldn't be running at all. I just set my profile, close the program such that it is not running in the background. Does anything specific come to mind?

Thank you for the help, glad to have found the issue.

seth · 2025-10-07 21:33:34

It's gonna be invoked by /usr/lib/udev/rules.d/60-openrgb.rules

I wonder if an update of openrgb broke it on my system?

Seems plausible - try to downgrade it in isolation and or remove the udev rule, don't forget to reload udev: https://wiki.archlinux.org/title/Udev#Loading_new_rules

Arch Linux

#1 2025-10-03 00:00:54

Issue waking from sleep

#2 2025-10-03 14:59:17

Re: Issue waking from sleep

#3 2025-10-03 15:23:41

Re: Issue waking from sleep

#4 2025-10-03 18:31:51

Re: Issue waking from sleep

#5 2025-10-03 23:10:03

Re: Issue waking from sleep

#6 2025-10-03 23:43:03

Re: Issue waking from sleep

#7 2025-10-04 00:36:36

Re: Issue waking from sleep

#8 2025-10-04 00:40:46

Re: Issue waking from sleep

#9 2025-10-04 08:51:53

Re: Issue waking from sleep

#10 2025-10-06 03:37:45

Re: Issue waking from sleep

#11 2025-10-06 14:05:38

Re: Issue waking from sleep

#12 2025-10-06 14:12:58

Re: Issue waking from sleep

#13 2025-10-06 14:16:44

Re: Issue waking from sleep

#14 2025-10-06 15:34:03

Re: Issue waking from sleep

#15 2025-10-06 18:53:38

Re: Issue waking from sleep

#16 2025-10-07 04:18:10

Re: Issue waking from sleep

#17 2025-10-07 08:53:36

Re: Issue waking from sleep

#18 2025-10-07 15:15:14

Re: Issue waking from sleep

#19 2025-10-07 15:28:31

Re: Issue waking from sleep

#20 2025-10-07 17:28:28

Re: Issue waking from sleep

#21 2025-10-07 19:33:56

Re: Issue waking from sleep

#22 2025-10-07 20:48:31

Re: Issue waking from sleep

#23 2025-10-07 21:02:40

Re: Issue waking from sleep

#24 2025-10-07 21:21:24

Re: Issue waking from sleep

#25 2025-10-07 21:33:34

Re: Issue waking from sleep

Board footer