OpenSUSE Tumbleweed KDE Plasma. Not sure if it matters but this is a dualboot setup with Windows 11 Pro, a Dell Latitude laptop. OpenSUSE is using LUKS encryption. SecureBoot is enabled.
I am unsure if this has happened before, but nowadays if I leave the OpenSUSE session open (usually with Chromium web browser open on the screen), by morning the system has rebooted and I am greeted with the Windows 11 login screen, which is where the system reboots by default.
Google suggested it could be due to a hardware failure or overheating, but I have run a full diagnostics for the laptop with no problems found, and generally it doesn’t seem to have overheating nor stability problems even in heavy use. If it had HW problems leading to reboots, I’d expect to see them also while using the machine, and overheating while idling at night doesn’t seem probable either.
Also, I don’t recall seeing this if it has been Windows which is left running for the night, but I can’t be fully sure. Maybe I will leave Windows 11 running this night.
A power outage or power supply problems shouldn’t cause this either as it is a a laptop with a healthy battery, and the battery charging level seems the same as previous night so it hasn’t had to run on battery power either.
System Settings => Software Update is set to Manual updates, Notification Frequency = Never. So it shouldn’t be automatic updates rebooting the system either. I update the system manually with “sudo zypper dup” every few weeks.
“sudo journalctl -b -1 -p err” says (these two are from this and yesterday mornings):
Yesterday morning:
Aug 21 02:05:52 localhost kernel: x86/cpu: SGX disabled or unsupported by BIOS.
Aug 21 02:06:12 localhost systemd-cryptsetup[574]: None of the alternative values for PCR 0 encoded in policy match the current TPM state. Either the system has been tempered with or the provided policy is incorrect.
Aug 21 02:06:13 localhost systemd-cryptsetup[574]: No valid TPM2 token data found.
Aug 20 23:06:17 localhost bootctl[1518]: Random seed file '/boot/efi/loader/random-seed' is world accessible, which is a security hole!
Aug 20 23:06:22 localhost.localdomain systemd[1]: Failed to start Update TPM predictions.
This morning:
Aug 22 00:13:17 localhost kernel: x86/cpu: SGX disabled or unsupported by BIOS.
Aug 22 00:13:30 localhost systemd-cryptsetup[572]: None of the alternative values for PCR 0 encoded in poliicy match the current TPM state. Either the system has been tempered with or the provided policy is incorrect.
Aug 22 00:13:31 localhost systemd-cryptsetup[572]: No valid TPM2 token data found.
Aug 21 21:13:35 localhost bootctl[1327]: Random seed file '/boot/efi/loader/random-seed' is world accessible, which is a security hole!
Aug 21 21:13:41 localhost.localdomain systemd[1]: Failed to start Update TPM predictions.
I googled for the meaning of the “None of the alternative values for PCR 0” error which suggested that due to hardware change or BIOS update has changed since e.g. LUKS partition was encrypted. Not sure if that matters, I have always used a LUKS password to boot into OpenSUSE and it still seems to work fine, and no idea if this has anything to do with the nightly reboots.
