I have encountered a similar issue where my monitor would never turn back on after suspend. I resolved the issue by accident after running sudo dmesg and seeing warnings about CPU vulnerabilities. I fixed those and voila! We have very different CPUs though. Mine is an Intel Xeon from 2016.
Interesting, I took a look at dmesg, and the only results that contain the word “fail” are:
[ 8.440871] usb 3-1.1.2: 6:4: failed to get current value for ch 0 (-22)
Which appears to be my Samson Go-Mic, but that’s working fine as an input, and I’m not using the output.
And:
[ 10.424295] Bluetooth: hci0: command 0x1001 tx timeout
[ 10.424307] Bluetooth: hci0: BCM: Reading local version info failed (-110)
Which looks like my Bluetooth dongle, which appears to be working fine outside of this error. Maybe it’s the Bluetooth in the HTC Vive hub that’s plugged in? But I think that’s here: [ 10.424295] Bluetooth: hci0: command 0x1001 tx timeout [ 10.424307] Bluetooth: hci0: BCM: Reading local version info failed (-110)
A little more info from a test:
I enabled SSH on my failing Fedora system using systemctl start sshd.service before I had the wakeup issue. After having the wakeup issue on my Fedora machine, I attempted to ssh into it from another system. The Fedora machine would successfully ask for my ssh password, then hang while trying to start ssh. Or if given the wrong password, the ssh login would return failure.
You should try using journalctl as (unlike dmesg) it preserves data from previous boots. You should be able to find details from previous wakeup attempts and your ssh login attempts. If you are not familiar with journalctl, see Beginner’s Guide to Analyzing Logs in Linux With journalctl Command.
I’ve noticed that when giving the sleep command, it can take much longer to fall asleep and when it’s slow to fall asleep, that’s when I’ll have the wake failure.
Thanks for the tip @gnwiii !
According to journalctl --list-boots -r my latest session before the hang ended at Tue 2025-07-29 17:18:58
I went ahead and used journalctl -r -p 4
Result:
Jul 29 17:18:58 Brigi irqbalance[1273]: Cannot change IRQ 98 affinity: Permission denied
Jul 29 17:18:58 Brigi irqbalance[1273]: IRQ 91 affinity is now unmanaged
Jul 29 17:18:58 Brigi irqbalance[1273]: Cannot change IRQ 91 affinity: Permission denied
Jul 29 17:18:48 fedora systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
Jul 29 17:18:47 fedora chronyd[1278]: Forward time jump detected!
Jul 29 17:18:40 fedora kernel: ata4: link is slow to respond, please be patient (ready=0)
Jul 29 17:18:40 fedora kernel: ata3: link is slow to respond, please be patient (ready=0)
Jul 29 17:18:39 fedora dbus-broker[1263]: A security policy denied :1.9 to send method call /midi/profile:org.bluez.GattProfile1.Release to :1.73.
Jul 29 17:18:39 fedora rtkit-daemon[1284]: The canary thread is apparently starving. Taking action.
Jul 29 17:18:39 fedora kernel: done.
Jul 29 17:18:39 fedora kernel: usb 1-3.1.1: WARN: invalid context state for evaluate context command.
Jul 29 17:18:39 fedora kernel: usb 1-3.1.2: WARN: invalid context state for evaluate context command.
Jul 29 17:18:39 fedora kernel: usb 1-9: WARN: invalid context state for evaluate context command.
Jul 29 17:18:39 fedora kernel: usb 1-10: WARN: invalid context state for evaluate context command.
Jul 29 17:18:39 fedora kernel: usb 1-5: WARN: invalid context state for evaluate context command.
Jul 29 17:18:39 fedora kernel: usb 1-7: WARN: invalid context state for evaluate context command.
Jul 29 17:18:39 fedora kernel: xhci_hcd 0000:02:00.0: xHC error in resume, USBSTS 0x401, Reinit
Jul 29 17:18:24 fedora systemd-sleep[64091]: Failed to freeze unit 'user.slice': Connection timed out
Jul 29 17:17:21 fedora kdeconnectd[2530]: 2025-07-29T17:17:21 org.kde.pulseaudio: No object for name "auto_null.monitor"
Jul 29 17:17:21 fedora kded6[2244]: org.kde.pulseaudio: No object for name "auto_null.monitor"
Jul 29 17:17:21 fedora plasmashell[2272]: org.kde.pulseaudio: No object for name "auto_null.monitor"
Jul 29 17:17:21 fedora plasmashell[2272]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Jul 29 17:17:21 fedora plasmashell[2272]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Jul 29 17:17:21 fedora kdeconnectd[2530]: 2025-07-29T17:17:21 org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Jul 29 17:17:21 fedora kdeconnectd[2530]: 2025-07-29T17:17:21 org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Jul 29 17:17:21 fedora kded6[2244]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Jul 29 17:17:21 fedora kded6[2244]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Jul 29 17:17:21 fedora plasmashell[2272]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Jul 29 17:17:21 fedora plasmashell[2272]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Jul 29 17:17:21 fedora plasmashell[2272]: org.kde.pulseaudio: No object for name "alsa_input.usb-Samson_Technologies_Samson_GoMic-00.mono-fallback"
Jul 29 17:17:21 fedora plasmashell[2272]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_2d_00.4.analog-stereo"
Jul 29 17:17:21 fedora plasmashell[2272]: org.kde.pulseaudio: No object for name "alsa_input.usb-Samson_Technologies_Samson_GoMic-00.mono-fallback"
Jul 29 17:17:21 fedora plasmashell[2272]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_2d_00.4.analog-stereo"
Jul 29 17:17:21 fedora kdeconnectd[2530]: 2025-07-29T17:17:21 org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Jul 29 17:17:21 fedora kdeconnectd[2530]: 2025-07-29T17:17:21 org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Jul 29 17:17:21 fedora plasmashell[2272]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_2d_00.4.analog-stereo"
Jul 29 17:17:21 fedora kded6[2244]: org.kde.pulseaudio: No object for name "@DEFAULT_SOURCE@"
Jul 29 17:17:21 fedora kded6[2244]: org.kde.pulseaudio: No object for name "@DEFAULT_SINK@"
Jul 29 17:17:21 fedora kded6[2244]: org.kde.pulseaudio: No object for name "alsa_input.usb-Samson_Technologies_Samson_GoMic-00.mono-fallback"
Jul 29 17:17:21 fedora kded6[2244]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_2d_00.4.analog-stereo"
Jul 29 17:17:21 fedora kded6[2244]: org.kde.pulseaudio: No object for name "alsa_input.usb-Samson_Technologies_Samson_GoMic-00.mono-fallback"
Jul 29 17:17:21 fedora kded6[2244]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_2d_00.4.analog-stereo"
Jul 29 17:17:21 fedora kdeconnectd[2530]: 2025-07-29T17:17:21 org.kde.pulseaudio: No object for name "alsa_input.usb-Samson_Technologies_Samson_GoMic-00.mono-fallback"
Jul 29 17:17:21 fedora kdeconnectd[2530]: 2025-07-29T17:17:21 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_2d_00.4.analog-stereo"
Jul 29 17:17:21 fedora kdeconnectd[2530]: 2025-07-29T17:17:21 org.kde.pulseaudio: No object for name "alsa_input.usb-Samson_Technologies_Samson_GoMic-00.mono-fallback"
Jul 29 17:17:21 fedora kdeconnectd[2530]: 2025-07-29T17:17:21 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_2d_00.4.analog-stereo"
Jul 29 17:17:21 fedora kdeconnectd[2530]: 2025-07-29T17:17:21 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_2d_00.4.analog-stereo"
Jul 29 17:17:21 fedora kded6[2244]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_2d_00.4.analog-stereo"
Jul 29 17:17:21 fedora kwin_wayland[2104]: kwin_core: Applying output configuration failed!
Jul 29 17:17:21 fedora kwin_wayland[2104]: kwin_wayland_drm: Atomic modeset test failed! Permission denied
Jul 29 17:17:21 fedora kernel: [drm:nv_drm_atomic_commit [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00002b00] Flip event timeout on head 1
Jul 29 17:17:18 Brigi chronyd[1278]: Can't synchronise: no selectable sources (4 unreachable sources)
Jul 29 17:17:18 Brigi kwin_wayland[2104]: kwin_core: Failed to delay sleep: Sender is not authorized to send message
Jul 29 17:17:18 Brigi dbus-broker[1263]: A security policy denied :1.64 to send method call /org/freedesktop/login1/seat/seat0:org.freedesktop.login1.Seat.Inhibit to org.freedesktop.login1.
Then the new boot cycle. Is this the relevant info? Do you need more details, or the log from the new boot?
I was reading in another thread where someone was theorizing networked drives might cause this problem? And I do have some Samba shares mounted on sleep.
Alright, after doing more testing, I’ve found one thing that always hangs my system and one thing that often hangs my system.
If I’ve got VScodium open and pointed at a folder on a mounted Samba drive and put the system to sleep, it will always hang on wakeup.
If I unplug my phone from the system while the sleep command is being processed (after the screen goes blank), the system has a significant chance to hang on wakeup.
I’ll keep testing and report back. If either of those give folks ideas of what might be going on, please provide me with any info you’ve got!
And @computersavvy , I’m looking at using autofs to help with the unmount issue, but that’s on a timer, so what if the mount was still active during sleep? I don’t want to have to manually unmount all my shares before sleep, is there a utility that can do that for me?
That would be expected. The system sleeping breaks the connection to the remote drive and having an app or a file open in that remote file system would have the link broken at the time it goes to sleep. The system itself does not know the link is broken so it hangs trying to use an already defined link that no longer exists. The remote system sees the break, but the sleeping system is unaware of the break until it attempts to use that link again.
I am unaware of any ready made utility that would manage that for you, but it should be easy to write a script that is called when going to sleep and dismounts the remote devices before sleeping. NOTE however, that any app or open file in the remote file system WILL prevent dismounting the device – such as your indicated VScodium (if the file system is busy it cannot be dismounted.) The user must make certain the file system is not busy before trying to sleep or dismount the device.
Sleep causing a hang just because I’m using a network drive is unacceptable for my usecase, and after some testing I moved from SMB to NFS for my networked drives. The move to NFS fixed the 100% hang on wake if an IDE was open and using my network mounts.
But I still had some intermittent hanging when the system would wake. After lots of digging around the error Failed to freeze unit ‘user.slice’: Connection timed out, it seemed like my issue might be related to a systemD problem. 37590 and 38468
In the week since I started using v257.9 I have had zero hangs when resuming the operating system. I certainly wont claim my issue is fixed at this time, but it currently seems that this update has resolved my issue. So if I make no follow up posts, assume that this issue is resolved.