Public bug reported:
On an Asus T300CHI with 16.04 and kernel 4.13.0-25-lowlatency a suspend
operation almost immediately resumed but "systemd-sleep suspend" was
still running and as a result network-manager thought it was in state
"asleep" and would not re-enable networking.
Some system logs looked like they weren't getting the normal flow of
messages and 'systemctl status' for the suspend.target and systemd-
suspend.service showed they thought the system was suspending/suspended.
This was around 07:36. I left the system most of the day until I could
investigate.
I noticed the dmesg showed "Suspended for 23820.656 seconds" when it
resumed/failed to suspend immediately.
After a lot of digging and saving command output of interest at 18:33 I
did:
sudo kill $(pidof systemd-sleep)
the system immediately suspended. After nearly a minute I pressed the
power button and the PC instantly resumed.
dmesg reported "Suspended for 43 seconds" which is correct and network-
manager correctly returned to connected state.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1744370
Title:
'systemd-sleep suspend' hung after an abortive suspend/resume
Status in systemd package in Ubuntu:
New
Bug description:
On an Asus T300CHI with 16.04 and kernel 4.13.0-25-lowlatency a
suspend operation almost immediately resumed but "systemd-sleep
suspend" was still running and as a result network-manager thought it
was in state "asleep" and would not re-enable networking.
Some system logs looked like they weren't getting the normal flow of
messages and 'systemctl status' for the suspend.target and systemd-
suspend.service showed they thought the system was
suspending/suspended.
This was around 07:36. I left the system most of the day until I could
investigate.
I noticed the dmesg showed "Suspended for 23820.656 seconds" when it
resumed/failed to suspend immediately.
After a lot of digging and saving command output of interest at 18:33
I did:
sudo kill $(pidof systemd-sleep)
the system immediately suspended. After nearly a minute I pressed the
power button and the PC instantly resumed.
dmesg reported "Suspended for 43 seconds" which is correct and
network-manager correctly returned to connected state.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1744370/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
