My office workstation, a Dell Precision T1700 running Fedora 34 (mostly KDE when I'm at the machine), has been suspending itself after a power outage. This seems to be connected to a networking problem, but I don't really understand what's going on or where to look. It seems that the system tries to put itself to sleep when it can't connect to the network. I don't understand why this should happen, or what to do about it. On Friday, construction equipment cut the main power feed to our part of campus and there was a roughly half-hour power outage. I was working at home, but reading mail on the office system. The system currently has a small APC UPS and is running apcupsd with pretty much the default configuration. At 14:39:50, there are messages from apcupsd saying the system is running on battery and a mail message to root saying the time left on battery was 64.9 minutes with a 100 percent charge. And at 14:44 the system started to suspend. At about 15:11, it looks like the power returned and the system brought itself back (though with some complaints in the logs, like Failed to StopUnit service: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1). However, there were network problem, both within our department network and at the connection between the department and the campus backbone. These were not resolved until late the next day when the campus IT people finally responded and reset that connection. (Our department IT staff is a lot more responsive and competent than the campus staff...). But my machine was still not reachable. There seem to have also been problems with the switch where my machine connects to the rest of the department network, and it looks like when my machine couldn't connect to the network, it put itself to sleep again: Aug 06 17:47:32 ext.math.umass.edu kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Aug 06 17:47:32 ext.math.umass.edu kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Aug 06 17:47:32 ext.math.umass.edu NetworkManager[2111]: <info> [1628286452.1872] manager: sleep: sleep requested (sleeping: no enabled: yes) Aug 06 17:47:32 ext.math.umass.edu NetworkManager[2111]: <info> [1628286452.1876] manager: NetworkManager state is now ASLEEP Aug 06 17:47:32 ext.math.umass.edu ModemManager[1954]: <info> [sleep-monitor] system is about to suspend Aug 06 17:47:32 ext.math.umass.edu gnome-shell[4292]: Screen lock is locked down, not locking Aug 06 17:47:32 ext.math.umass.edu systemd[1]: Reached target Sleep. Aug 06 17:47:32 ext.math.umass.edu systemd[1]: Starting System Suspend... Aug 06 17:47:32 ext.math.umass.edu systemd-sleep[40504]: Suspending system... Aug 06 17:47:32 ext.math.umass.edu kernel: PM: suspend entry (deep) Aug 07 14:09:22 ext.math.umass.edu kernel: Filesystems sync: 0.379 seconds Aug 07 14:09:22 ext.math.umass.edu kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 07 14:09:22 ext.math.umass.edu kernel: OOM killer disabled. Aug 07 14:09:22 ext.math.umass.edu kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. Aug 07 14:09:22 ext.math.umass.edu kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 07 14:09:22 ext.math.umass.edu kernel: serial 00:06: disabled Aug 07 14:09:22 ext.math.umass.edu kernel: e1000e: EEE TX LPI TIMER: 00000011 Aug 07 14:09:22 ext.math.umass.edu kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 07 14:09:22 ext.math.umass.edu kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache Aug 07 14:09:22 ext.math.umass.edu kernel: sd 1:0:0:0: [sdb] Stopping disk Aug 07 14:09:22 ext.math.umass.edu kernel: sd 0:0:0:0: [sda] Stopping disk Aug 07 14:09:22 ext.math.umass.edu kernel: PM: suspend devices took 1.031 seconds Aug 07 14:09:22 ext.math.umass.edu kernel: ACPI: Preparing to enter system sleep state S3 Aug 07 14:09:22 ext.math.umass.edu kernel: PM: Saving platform NVS memory Aug 07 14:09:22 ext.math.umass.edu kernel: Disabling non-boot CPUs ... lines 835-871 etc. The staff rebooted the machine again, and the same thing happened. Finally this morning, they rebooted both the switch and my machine, and everything seems ok for now, although they are checking the switch and will probably be replacing it. But why should the machine suspend itself when it can't connect to the switch? This is pretty much the only Fedora machine in the department and I mostly administer it (we're currently severely understaffed), so I can't just leave it to the staff to sort things out. I'd very much appreciate any help. George
Attachment:
pgpQGckm1xbma.pgp
Description: OpenPGP digital signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
