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.

[ 2013.045110] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 2013.045134] ata1.00: Entering standby power mode
[ 2013.626491] xhci_hcd 0000:00:14.0: xHC error in resume, USBSTS 0x411, Reinit
[ 2013.626493] usb usb2: root hub lost power or was reset
[ 2013.626495] usb usb3: root hub lost power or was reset
[ 2013.626497] usb usb4: root hub lost power or was reset
[ 2013.626499] xhci_hcd 0000:05:00.0: xHC error in resume, USBSTS 0x401, Reinit
[ 2013.626500] usb usb1: root hub lost power or was reset
[ 2013.626503] usb 1-9.2: WARN: invalid context state for evaluate context command.
[ 2013.626504] usb 1-9.1: WARN: invalid context state for evaluate context command.
[ 2013.626505] usb 1-13.2: WARN: invalid context state for evaluate context command.
[ 2013.626506] usb 1-13.1: WARN: invalid context state for evaluate context command.
[ 2015.557571] usb 1-9: WARN: invalid context state for evaluate context command.
[ 2015.557574] usb 1-13: WARN: invalid context state for evaluate context command.
[ 2021.036911] mei_me 0000:00:16.0: wait hw ready failed
[ 2021.037117] mei_me 0000:00:16.0: hw_start failed ret = -62
[ 2021.037493] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING fw status = 00002144 36550106 00000020 00000404 00000000 40000000 00000000 00000000
[ 2021.037494] mei_me 0000:00:16.0: H_RST is set = 0x00000031
[ 2021.041171] random: crng reseeded on system resumption
[ 2021.041171] Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.

Am on latest zen kernel

Last edited by Histole (2025-10-03 00:01:19)

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

I managed to get logs:

journalctl -b -1 -k --no-pager | grep -A50 -B10 "sysrq"
Oct 03 19:05:29 pc kernel: 
Oct 03 19:05:29 pc kernel: Showing busy workqueues and worker pools:
Oct 03 19:05:29 pc kernel: workqueue events_bh_highpri: flags=0x11
Oct 03 19:05:29 pc kernel:   pwq 1: cpus=0 node=0 flags=0x5 bh-hi active=1 refcnt=2
Oct 03 19:05:29 pc kernel:     in-flight: bh-hi:usb_giveback_urb_bh
Oct 03 19:05:29 pc kernel: workqueue mm_percpu_wq: flags=0x8
Oct 03 19:05:29 pc kernel:   pwq 2: cpus=0 node=0 flags=0x0 nice=0 active=1 refcnt=3
Oct 03 19:05:29 pc kernel:     pending: lru_add_drain_per_cpu BAR(125)
Oct 03 19:05:29 pc kernel: pool 1: cpus=0 node=0 flags=0x5 bh-hi hung=0s workers=1
Oct 03 19:05:29 pc systemd-journald[419]: /dev/kmsg buffer overrun, some messages lost.
Oct 03 19:05:32 pc kernel: sysrq: Show Blocked State
Oct 03 19:05:34 pc kernel: sysrq: Show Memory
Oct 03 19:05:34 pc kernel: Mem-Info:
Oct 03 19:05:34 pc kernel: active_anon:573743 inactive_anon:0 isolated_anon:0
                            active_file:482571 inactive_file:180196 isolated_file:0
                            unevictable:29 dirty:1447 writeback:0
                            slab_reclaimable:17451 slab_unreclaimable:43891
                            mapped:269521 shmem:24450 pagetables:9426
                            sec_pagetables:257 bounce:0
                            kernel_misc_reclaimable:0
                            free:6703232 free_pcp:21414 free_cma:0
Oct 03 19:05:34 pc kernel: Node 0 active_anon:2294972kB inactive_anon:0kB active_file:1930284kB inactive_file:720784kB unevictable:116kB isolated(anon):0kB isolated(file):0kB mapped:1078084kB dirty:5788kB writeback:0kB shmem:97800kB shmem_thp:0kB shmem_pmdmapped:0kB anon_thp:399360kB writeback_tmp:0kB kernel_stack:16736kB pagetables:37704kB sec_pagetables:1028kB all_unreclaimable? no Balloon:0kB
Oct 03 19:05:34 pc kernel: Node 0 DMA free:11260kB boost:0kB min:28kB low:40kB high:52kB reserved_highatomic:0KB free_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15988kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
Oct 03 19:05:34 pc kernel: lowmem_reserve[]: 0 2163 31979 31979 31979
Oct 03 19:05:34 pc kernel: Node 0 DMA32 free:2211772kB boost:0kB min:4316kB low:6396kB high:8476kB reserved_highatomic:0KB free_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:2283388kB managed:2215888kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB
Oct 03 19:05:34 pc kernel: lowmem_reserve[]: 0 0 29815 29815 29815
Oct 03 19:05:34 pc kernel: Node 0 Normal free:24589896kB boost:0kB min:63236kB low:93756kB high:124276kB reserved_highatomic:0KB free_highatomic:0KB active_anon:2294972kB inactive_anon:0kB active_file:1930284kB inactive_file:720784kB unevictable:116kB writepending:5788kB present:31162368kB managed:30530816kB mlocked:116kB bounce:0kB free_pcp:85656kB local_pcp:19864kB free_cma:0kB
Oct 03 19:05:34 pc kernel: lowmem_reserve[]: 0 0 0 0 0
Oct 03 19:05:34 pc kernel: Node 0 DMA: 1*4kB (U) 1*8kB (U) 1*16kB (U) 1*32kB (U) 1*64kB (U) 1*128kB (U) 1*256kB (U) 1*512kB (U) 0*1024kB 1*2048kB (M) 2*4096kB (M) = 11260kB
Oct 03 19:05:34 pc kernel: Node 0 DMA32: 5*4kB (M) 5*8kB (M) 8*16kB (UM) 8*32kB (UM) 6*64kB (UM) 5*128kB (UM) 6*256kB (UM) 8*512kB (UM) 7*1024kB (UM) 5*2048kB (UM) 534*4096kB (M) = 2211772kB
Oct 03 19:05:34 pc kernel: Node 0 Normal: 19273*4kB (UME) 12934*8kB (UME) 5818*16kB (UME) 2170*32kB (UME) 911*64kB (UME) 260*128kB (UME) 76*256kB (UM) 23*512kB (UM) 13*1024kB (UM) 13*2048kB (UM) 5880*4096kB (UM) = 24590324kB
Oct 03 19:05:34 pc kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
Oct 03 19:05:34 pc kernel: Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
Oct 03 19:05:34 pc kernel: 687172 total pagecache pages
Oct 03 19:05:34 pc kernel: 0 pages in swap cache
Oct 03 19:05:34 pc kernel: Free swap  = 4194300kB
Oct 03 19:05:34 pc kernel: Total swap = 4194300kB
Oct 03 19:05:34 pc kernel: 8365436 pages RAM
Oct 03 19:05:34 pc kernel: 0 pages HighMem/MovableOnly
Oct 03 19:05:34 pc kernel: 174920 pages reserved
Oct 03 19:05:34 pc kernel: 0 pages cma reserved
Oct 03 19:05:34 pc kernel: 0 pages hwpoisoned
Oct 03 19:05:43 pc kernel: usb 1-7: USB disconnect, device number 11
Oct 03 19:05:43 pc kernel: usb 1-8: USB disconnect, device number 3

Is this a USB issue? I notice if I disconnect everything except keyboard, and I suspend, then wake, it wakes to the desktop but the keyboard is unresponsive unless re plugged in.

Last edited by Histole (2025-10-03 23:12:54)

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 · Yesterday 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

https://0x0.st/KMhT.txt

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 (Yesterday 03:38:31)

seth · Yesterday 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 (Yesterday 14:06:39)

Histole · Yesterday 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 · Yesterday 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 · Yesterday 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.

Log after blacklisting MEI:
https://0x0.st/KuzE.log

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 (Yesterday 15:34:27)

seth · Yesterday 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 · Today 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.

New logs:
https://0x0.st/Ku8J.log

seth · Today 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 · Today 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 · Today 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 · Today 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?

https://0x0.st/Kubm.txt

I did remove the blacklist for MEI, as it did not look like it made a difference.

Last edited by Histole (Today 17:28:51)

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 Yesterday 03:37:45

Re: Issue waking from sleep

#11 Yesterday 14:05:38

Re: Issue waking from sleep

#12 Yesterday 14:12:58

Re: Issue waking from sleep

#13 Yesterday 14:16:44

Re: Issue waking from sleep

#14 Yesterday 15:34:03

Re: Issue waking from sleep

#15 Yesterday 18:53:38

Re: Issue waking from sleep

#16 Today 04:18:10

Re: Issue waking from sleep

#17 Today 08:53:36

Re: Issue waking from sleep

#18 Today 15:15:14

Re: Issue waking from sleep

#19 Today 15:28:31

Re: Issue waking from sleep

#20 Today 17:28:28

Re: Issue waking from sleep

Board footer