On Tue, 2023-11-14 at 10:36 -0600, Roger Heflin wrote: > That is not a reboot. That is a crash/power off or something else. > > You might move your wake up the machine to say 7:40 and see if the > machine still does it at 8am or then does it at 7:50 (10 min after > reboot). > > If it does it 10 minutes after reboot that is often the default for > the watchdog reset timer that will force power the machine (in bios) > if the OS does not touch the watchdog every so often. > > If the machine has the watchdog enabled, there is a decent chance it > is not getting correctly restarted after hibernation. Tried that, but the machine still boots at 08:00. I logged the watchdog status in the hibernate resume script: Wed 15 Nov 07:40:46 GMT 2023 Device: /dev/watchdog0 Identity: iTCO_wdt [version 2] Timeout: 30 seconds Timeleft: 2 seconds Pre-timeout: 0 seconds FLAG DESCRIPTION STATUS BOOT-STATUS KEEPALIVEPING Keep alive ping reply 1 0 MAGICCLOSE Supports magic close char 0 0 SETTIMEOUT Set timeout (in seconds) 0 0 Interestingly, the running watchdog status (after the forced boot) has a different identity field: $ wdctl Device: /dev/watchdog0 Identity: iamt_wdt [version 1] Timeout: 120 seconds FLAG DESCRIPTION STATUS BOOT-STATUS KEEPALIVEPING Keep alive ping reply 1 0 SETTIMEOUT Set timeout (in seconds) 0 0 ALARMONLY Not trigger reboot 0 0 but I'm not sure that's relevant. Either way, the forced boot still happens at 08:00 and not after a 10-minute timeout, so the mystery continues. poc _______________________________________________ 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, report it: https://pagure.io/fedora-infrastructure/new_issue
