Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Bullseye suspend issue

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
User avatar
ticojohn
Posts: 1284
Joined: 2009-08-29 18:10
Location: Costa Rica
Has thanked: 21 times
Been thanked: 44 times

Bullseye suspend issue

#1 Post by ticojohn »

System is Bullseye amd64 with XFCE desktop and lightdm.

Yesterday I used the suspend feature and had some strange things happen. The system was suspended for about two hours and when I woke it up I saw that the clock on the top panel off by two hours. It's as if the system clock did not update while asleep. I suppose that makes sense since the system is basically just refreshing ram during the sleep period (I think). However, later that evening I shut the system down and that's when things got strange. On shutdown I got a screen full of messages and instead of powering down the system just hung with the messages displayed on the screen. Unfortunately I was so dumbfounded that I didn't bother to take a picture of the screen. I tried to execute a hard reset (yikes) but nothing happened. Eventually, after about 5 minutes the computer responded to the reset button.

I looked at journalctl for that time period and don't see anything out of the ordinary. Here are the last 40 lines or so from the journal

Code: Select all

Oct 29 20:55:13 debian systemd[1]: Stopped Apply Kernel Variables.
Oct 29 20:55:13 debian systemd[1]: systemd-modules-load.service: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Stopped Load Kernel Modules.
Oct 29 20:55:13 debian systemd[1]: Stopping Network Time Synchronization...
Oct 29 20:55:13 debian systemd[1]: Stopping Update UTMP about System Boot/Shutdown...
Oct 29 20:55:13 debian systemd[1]: systemd-update-utmp.service: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
Oct 29 20:55:13 debian systemd[1]: systemd-timesyncd.service: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Stopped Network Time Synchronization.
Oct 29 20:55:13 debian systemd[1]: systemd-tmpfiles-setup.service: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Stopped Create Volatile Files and Directories.
Oct 29 20:55:13 debian systemd[1]: Stopped target Local File Systems.
Oct 29 20:55:13 debian systemd[1]: Stopped target Local File Systems (Pre).
Oct 29 20:55:13 debian systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Stopped Create Static Device Nodes in /dev.
Oct 29 20:55:13 debian systemd[1]: systemd-sysusers.service: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Stopped Create System Users.
Oct 29 20:55:13 debian systemd[1]: systemd-remount-fs.service: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Stopped Remount Root and Kernel File Systems.
Oct 29 20:55:13 debian systemd[1]: Reached target Shutdown.
Oct 29 20:55:13 debian systemd[1]: dev-disk-by\x2did-ata\x2dSamsung_SSD_850_EVO_250GB_S2R5NB0HA68389Z\x2dpart5.swap: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Deactivated swap /dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S2R5NB0HA68389Z-part5.
Oct 29 20:55:13 debian systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1.0\x2dpart5.swap: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:1f.2-ata-1.0-part5.
Oct 29 20:55:13 debian systemd[1]: dev-disk-by\x2dpartuuid-80f5754e\x2d05.swap: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Deactivated swap /dev/disk/by-partuuid/80f5754e-05.
Oct 29 20:55:13 debian systemd[1]: dev-disk-by\x2did-wwn\x2d0x5002538d4155acf1\x2dpart5.swap: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Deactivated swap /dev/disk/by-id/wwn-0x5002538d4155acf1-part5.
Oct 29 20:55:13 debian systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:00:1f.2\x2data\x2d1\x2dpart5.swap: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Deactivated swap /dev/disk/by-path/pci-0000:00:1f.2-ata-1-part5.
Oct 29 20:55:13 debian systemd[1]: dev-sda5.swap: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Deactivated swap /dev/sda5.
Oct 29 20:55:13 debian systemd[1]: dev-disk-by\x2duuid-ce53fbb9\x2d1c30\x2d4083\x2d8e84\x2df06e5864a0b7.swap: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Deactivated swap /dev/disk/by-uuid/ce53fbb9-1c30-4083-8e84-f06e5864a0b7.
Oct 29 20:55:13 debian systemd[1]: Reached target Unmount All Filesystems.
Oct 29 20:55:13 debian systemd[1]: Reached target Final Step.
Oct 29 20:55:13 debian systemd[1]: systemd-poweroff.service: Succeeded.
Oct 29 20:55:13 debian systemd[1]: Finished Power-Off.
Oct 29 20:55:13 debian systemd[1]: Reached target Power-Off.
Oct 29 20:55:13 debian systemd[1]: Shutting down.
Oct 29 20:55:13 debian systemd-shutdown[1]: Syncing filesystems and block devices.
Oct 29 20:55:13 debian systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Oct 29 20:55:13 debian systemd-journald[244]: Journal stopped
It would appear that a power off signal was sent but the computer did not power down. I have not previously had problems with shutting down the system. Is there perhaps some relationship between suspending the system for an extended period and this strange shutdown failure?
I am not irrational, I'm just quantum probabilistic.

Post Reply