System sometimes reboots automatically

Ask Fedora Ask in English
1

I use Fedora as my main workstation, so it runs typically the whole day. Sometimes it happens that it reboots automatically, at least once a day. This happens never when I’m in front of the computer but always when I’m away for some time, so I wonder if this is related to any power saving operation which might fail?

Today the system rebootet at 16:07 (4:07pm) according to “who -b”. If I check journalctl nothing happened directly before the reboot:

Jan 31 15:38:09 fedora rtkit-daemon[977]: Supervising 8 threads of 6 processes of 1 users.
Jan 31 15:38:09 fedora rtkit-daemon[977]: Supervising 8 threads of 6 processes of 1 users.
Jan 31 15:38:12 fedora rtkit-daemon[977]: Supervising 8 threads of 6 processes of 1 users.
Jan 31 15:38:12 fedora rtkit-daemon[977]: Supervising 8 threads of 6 processes of 1 users.
Jan 31 15:41:14 fedora wpa_supplicant[1335]: wlp2s0: WPA: Group rekeying completed with   38:10:d5:2e:07:cd [GTK=CCMP]
Jan 31 15:41:50 fedora gnome-shell[2302]: libinput error: event12 - Logitech USB Keyboard: client bug: event processing lagging behind by 33ms, your system is too slow
Jan 31 15:42:45 fedora cupsd[1188]: REQUEST localhost - - "POST / HTTP/1.1" 200 187 Renew-Subscription successful-ok
Jan 31 15:49:31 fedora firefox.desktop[3486]: ###!!! [Parent][RunMessage] Error: Channel closing: too late to send/recv, messages will be lost
Jan 31 15:51:14 fedora wpa_supplicant[1335]: wlp2s0: WPA: Group rekeying completed with 38:10:d5:2e:07:cd [GTK=CCMP]
Jan 31 16:01:14 fedora wpa_supplicant[1335]: wlp2s0: WPA: Group rekeying completed with 38:10:d5:2e:07:cd [GTK=CCMP]

as you can see, the last log message is 6 minutes before the reboot.

Than at 16:07 i see only messages regarding the system statrt, but nothing regarding the shutdown:

Jan 31 16:07:51 fedora kernel: microcode: microcode updated early to revision 0xea, date = 2021-01-06
Jan 31 16:07:51 fedora kernel: Linux version 5.15.17-200.fc35.x86_64 (mockbuild@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 11.2.1 20211203 (Red Hat 11.2.1-7), GNU ld version 2.37-10.fc35) #1 SMP Thu Jan 27 16:29:05 UTC 2022
Jan 31 16:07:51 fedora kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/boot/vmlinuz-5.15.17-200.fc35.x86_64 root=UUID=5eab2c00-2a3d-483f-9b29-3c07c41140b6 ro resume=UUID=bd082ad8-3c04-4977-97c7-582d671c7319 rhgb quiet
Jan 31 16:07:51 fedora kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jan 31 16:07:51 fedora kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jan 31 16:07:51 fedora kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jan 31 16:07:51 fedora kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Jan 31 16:07:51 fedora kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Jan 31 16:07:51 fedora kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jan 31 16:07:51 fedora kernel: x86/fpu: xstate_offset[3]:  832, xstate_sizes[3]:   64
Jan 31 16:07:51 fedora kernel: x86/fpu: xstate_offset[4]:  896, xstate_sizes[4]:   64
Jan 31 16:07:51 fedora kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Jan 31 16:07:51 fedora kernel: signal: max sigframe size: 2032
Jan 31 16:07:51 fedora kernel: BIOS-provided physical RAM map:
...

Any idea what could be the reasons? Where could I look at beside the journalctl?

Thanks!

2

May be you want to try with previous kernel version (5.15.16) first to see if there any different. If this behavior not present with previous kernel, I suggest make report to bugzilla.

Also maybe you want to read this forum I found from internet search, especially on this comment.

3

Is it in a secure location where no one is tampering with the power?

4

Yes, I can rule out that someone is tempering with the power. I also have the feeling that it happens more often in environments where I often unplug the laptop. So it might be really a power saving issue.

5

Thanks for the link @oprizal this sounds really interesting. It is indeed a Intel laptop. I applied the settings to my grub config and keep an eye on it… Let’s see if this will fix the issue.

6

It seems like this adding "intel_idle.max_cstate=1 i915.enable_dc=0 ahci.mobile_lpm_policy=1 " to my grub config really solved the issue. At least my system runs now two days in a row without any unexpected reboots.

1 Like
7

Awesome!

I change the solution mark to your comment since it more specific solution.