Here are some excerpts from the persistent journal, collected from journalctl
:
Jul 31 11:51:57 localhost.localdomain systemd[1]: Received SIGRTMIN+21 from PID 595 (plymouthd).
Jul 31 11:51:57 localhost.localdomain systemd[1]: Started Hold until boot process finishes up.
Jul 31 11:51:57 localhost.localdomain systemd[1]: Reached target Multi-User System.
Jul 31 11:51:57 localhost.localdomain systemd[1]: Reached target Graphical Interface.
Jul 31 11:51:57 localhost.localdomain systemd[1]: Starting Update UTMP about System Runlevel Changes...
Jul 31 11:51:57 localhost.localdomain systemd[1]: systemd-update-utmp-runlevel.service: Succeeded.
Jul 31 11:51:57 localhost.localdomain systemd[1]: Started Update UTMP about System Runlevel Changes.
Jul 31 11:51:57 localhost.localdomain systemd[1]: Startup finished in 11.289s (firmware) + 6.630s (loader) + 1.242s (kernel) + 6.212s (initrd) + 10.985s (userspace) = 36.359s.
Jul 31 11:51:58 localhost.localdomain chronyd[1205]: Selected source 162.221.74.15
Jul 31 11:51:58 localhost.localdomain chronyd[1205]: System clock TAI offset set to 37 seconds
Jul 31 11:52:04 localhost.localdomain systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jul 31 11:52:26 localhost.localdomain systemd[1]: systemd-localed.service: Succeeded.
Jul 31 11:52:27 localhost.localdomain systemd[1]: systemd-hostnamed.service: Succeeded.
Jul 31 11:52:27 localhost.localdomain systemd[1]: fprintd.service: Succeeded.
-- Reboot --
Jul 31 11:53:56 localhost.localdomain kernel: printk: systemd: 16 output lines suppressed due to ratelimiting
Jul 31 11:53:56 localhost.localdomain kernel: audit: type=1404 audit(1627732435.848:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
Jul 31 11:53:56 localhost.localdomain kernel: SELinux: policy capability network_peer_controls=1
Jul 31 11:53:56 localhost.localdomain kernel: SELinux: policy capability open_perms=1
...
Jul 31 11:53:56 localhost.localdomain kernel: input: Dell AIO WMI hotkeys as /devices/virtual/input/input7
Jul 31 11:53:56 localhost.localdomain kernel: usbcore: registered new interface driver btusb
Jul 31 11:53:56 localhost.localdomain kernel: Bluetooth: hci0: Bootloader revision 0.4 build 0 week 30 2018
Jul 31 11:53:56 localhost.localdomain kernel: Bluetooth: hci0: Device revision is 2
Jul 31 11:53:56 localhost.localdomain kernel: Bluetooth: hci0: Secure boot is enabled
Jul 31 11:53:56 localhost.localdomain kernel: Bluetooth: hci0: OTP lock is enabled
-- Reboot --
Jul 31 11:55:44 localhost.localdomain kernel: printk: systemd: 16 output lines suppressed due to ratelimiting
Jul 31 11:55:44 localhost.localdomain kernel: audit: type=1404 audit(1627732543.811:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
Jul 31 11:55:44 localhost.localdomain kernel: SELinux: policy capability network_peer_controls=1
Jul 31 11:55:44 localhost.localdomain kernel: SELinux: policy capability open_perms=1
Jul 31 11:55:44 localhost.localdomain kernel: SELinux: policy capability extended_socket_class=1
Jul 31 11:55:44 localhost.localdomain kernel: SELinux: policy capability always_check_network=0
Jul 31 11:55:44 localhost.localdomain kernel: SELinux: policy capability cgroup_seclabel=1
Jul 31 11:55:44 localhost.localdomain kernel: SELinux: policy capability nnp_nosuid_transition=1
Jul 31 11:55:44 localhost.localdomain kernel: audit: type=1403 audit(1627732543.921:3): auid=4294967295 ses=4294967295 lsm=selinux res=1
That happened while the system was unattended. These are clearly reboots, which are different from logging out a user, and they appear to have occurred at 11:52 and 11:57. In fact, they happen about every 2-5 minutes (based on search of the log):
Line 11920: -- Reboot --
Line 13166: -- Reboot --
Line 14416: -- Reboot --
Line 15664: -- Reboot --
Line 16988: -- Reboot --
Line 21547: -- Reboot --
Line 23678: -- Reboot --
Line 25564: -- Reboot --
Line 26191: -- Reboot --
Line 26826: -- Reboot --
Line 26904: -- Reboot --
I’ve allegedly turned off the screen lock, that shouldn’t be an issue. I’ve already adjusted the settings to make the screen blank, and I’ve already configured the power management to never hibernate and to power down when I press the power button.
I’ve been using CentOS 5 through CentOS 7 for more more than ten years, I’m somewhat familiar with what the system should be doing.
I do see some indications of graphics driver issues in the journal and at the console:
Jul 30 18:22:12 localhost.localdomain gnome-shell[1972]: Error setting property 'Powered' on interface org.bluez.Adapter1: GDBus.Error:org.bluez.Error.Blocked: Blocked through rfkill (g-io-error-quark, 36)
...
In the midst of at least one shutdown I see this:
Jul 30 20:09:29 localhost.localdomain kernel: nouveau 0000:02:00.0: tmr: stalled at ffffffffffffffff
Jul 30 20:09:29 localhost.localdomain kernel: ------------[ cut here ]------------
Jul 30 20:09:29 localhost.localdomain kernel: nouveau 0000:02:00.0: timeout
Jul 30 20:09:29 localhost.localdomain kernel: WARNING: CPU: 0 PID: 1 at drivers/gpu/drm/nouveau/nvkm/subdev/bar/g84.c:38 g84_bar_flush+0xcc/0xe0 [nouveau]
I also see the following:
Jul 30 14:20:25 localhost.localdomain kernel: [Hardware Error]: event severity: fatal
Jul 30 14:20:25 localhost.localdomain kernel: [Hardware Error]: Error 0, type: fatal
Jul 30 14:20:25 localhost.localdomain kernel: [Hardware Error]: section type: unknown, 81212a96-09ed-4996-9471-8d729c8e69ed
Jul 30 14:20:25 localhost.localdomain kernel: [Hardware Error]: section length: 0xc20
Jul 30 14:20:25 localhost.localdomain kernel: [Hardware Error]: 00000000: 00000201 00000000 00000000 01042001 ............. ..
... (~800 lines elided, all similar to these)
Jul 30 14:20:25 localhost.localdomain kernel: [Hardware Error]: 00000c00: ffffffff ffffffff ffffffff ffffffff ................
Jul 30 14:20:25 localhost.localdomain kernel: [Hardware Error]: 00000c10: ffffffff ffffffff ffffffff ffffffff ................