Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#65648 - [linux] Suspend to RAM (S3)makes system unresponsive for a period of time
Attached to Project:
Arch Linux
Opened by Steve Schaeffer (schasj) - Friday, 28 February 2020, 00:31 GMT
Last edited by freswa (frederik) - Wednesday, 18 March 2020, 20:33 GMT
Opened by Steve Schaeffer (schasj) - Friday, 28 February 2020, 00:31 GMT
Last edited by freswa (frederik) - Wednesday, 18 March 2020, 20:33 GMT
|
DetailsSince kernel 5.5 (possibly a little newer) suspending to RAM suspends my monitor and I can't login via ssh but the disk drives continue to spin for about an hour. During this time I can't wake the system. Once the disks power down I can resume normally.
I have looked at the journal from "Suspend key pressed." through "Enabling non-boot CPUs ..." for each version 5.4.15-5.5.6 and I don't see anything odd. My mobo is an Asus P6T and none of the hardware or firmware has changed in the last year. I don't know what else to provide so I await instructions. |
This task depends upon
Closed by freswa (frederik)
Wednesday, 18 March 2020, 20:33 GMT
Reason for closing: Won't fix
Additional comments about closing: hardware problem
Wednesday, 18 March 2020, 20:33 GMT
Reason for closing: Won't fix
Additional comments about closing: hardware problem
Comment by Steve Schaeffer (schasj) -
Saturday, 29 February 2020, 04:54 GMT
dmesg shows activity during the time that the system was unresponsive. I initiated the suspend at 17:32:07 and dmesg shows activity for about 1.5 hours after that. I'm attaching both dmesg and journal logs for the time period up until I resumed the system.
Comment by Steve Schaeffer (schasj) -
Saturday, 29 February 2020, 04:55 GMT
I guess I can only attach one at a time. Noob here.
Comment by Steve Schaeffer (schasj) -
Wednesday, 18 March 2020, 20:31 GMT
I setup a new system and can't reproduce this issue so I believe this is a problem with my hardware.
journal.log
(21.5 KiB)