You are not logged in.
Pages: 1
After doing a system upgrade about a week ago, I found that when I tried to suspend my computer, it rebooted. I could not debug it,
but after doing another upgrade a few days ago it now tries to suspend three times and then gives up.
The output of `sudo journalctl -b 0` after suspending is available at https://pastebin.com/wWSZagKH.
As you can see it errors with `kernel: PM: Some devices failed to suspend, or early wake event detected` right after stopping the disks,
and then suspend exists with `Failed to suspend system. System resumed again: Device or resource busy`.
I have tried a number of things to debug this:
Unloading xhci_pci and xhci_hcd with modprobe before suspending, no change.
Suspending via `echo -n "mem" | sudo tee /sys/power/state`, which results in a shutdown as it was originally.
Echoing EHC1, EHC2 and XHC to /proc/acpi/wakeup (none of which are listed there when I cat it), no change.
Echoing USB4 to /proc/acpi/wakeup, no change.
However I have run out of ideas and am turning to the community.
Offline
This should give you more ideas https://01.org/node/3721
https://ugjka.net
paru > yay | webcord > discord
pacman -S spotify-launcher
mount /dev/disk/by-...
Offline
I have unfortunately not been able to work it out using that resource.
Here is the log with initcall_debug and no_console_suspend enabled: https://pastebin.com/LARMMMFc
Any other ideas would be greatly appreciated.
Offline
Let's first see what's there:
cat /proc/acpi/wakeup
lsusb
Offline
Sorry for the slow reply, I was at school. Here are those two: https://pastebin.com/JRcjZaNS.
Offline
You saw all the fancy UHC* entries in the wakeup file?
Your USB devices - try to disable them (echoing the ID into the file toggles the state) until things work. My money is on the UPS. My *cyber*money, that is… ;-)
Offline
Unfortunately that did not do it. After leaving everything disabled in /proc/acpi/wakeup I still get the same issue.
Offline
Are there any further steps I could take to debug this?
Offline
Try to eliminate variables as possible.
Eg. seek to S3 from the multi-user.target (ie. no GUI) and w/o network (disconnect and stop the service, eg. NetworkManager)
Unplug everything you can (external readers, mouse, usb keys of all kinds, …)
If you manage to S3, start adding stuff until things fail again.
Offline
I tried from tty2 (no wm), unplugging everything, and disconnecting from the network via
ip link set enp3s0 down
but nothing changed. Could you elaborate on how I would go about seeking to it from multi-user.target?
Offline
Offline
I added the kernel parameter systemd.unit=multi-user.target, but that didn't seem to help unfortunately.
Offline
After running
echo 1 | sudo tee /sys/power/pm_trace
and trying to suspend, I got the following in my log: https://pastebin.com/8kUZMGWw
I don't remember seeing this before, could it simply be caused by the above warning or could it be the root cause?
If so, how would I go about further debugging?
Offline
alarmtimer seems to be the thing to blame, looking in /sys/kernel/debug/suspend_stats I see that it failed with errno -16, even when I disable pm_trace.
I do not know how to proceed from here unfortunately.
Offline
This is the rtc and it's most likely the cause, can you suspend w/ the LTS kernel?
Do you have a parallel windows installation?
Offline
I do have a parallel windows install, although I haven't bothered to set up multiboot with grub, and I haven't booted into it in months.
I am looking into how to switch kernels, I will get back to you with that.
Offline
I just tried the LTS kernel, and I get the same symptom.
Offline
https://wiki.archlinux.org/index.php/Du … t_Start-Up
Ftr, please don't bup but just edit your posts unless somebody has responded.
Offline
I do not (and have not) had fast startup enabled on my windows installation, so that can't be it.
Offline
Sure? It's the default mode, you've to actively disable it and windows will casually re-enable it w/ updates.
Since this is an issue whe interacting w/ the BIOS/CMOS/RTC and a hibernating windows is über-prone to cause this, I strongly recommend to take a look. Notably since the kernel doesn't seem to matter (you could also try downgrading linux and util-linux (and out of tree kernel modules like nvidia)
Offline
I just booted back into windows to check, it is not enabled. I don't actually have the option, but I checked and hibernation is in general disabled.
If it makes any difference the time was wrong in windows, but after setting it correctly there it remains correct under arch so I'm not sure if it changed the RTC.
Suspending still wasn't fixed after booting into windows and shutting down again.
Offline
Pages: 1