Spontaneous Reboot

Ask Fedora
,
1

Hiya,

I just had a random reboot and was wondering if anyone could help me troubleshoot. I wasn’t doing anything specifically intensive but had a bunch of apps open.

In last reboot I can see the reboot listed at exactly 11:30 when the reboot happened, however when I run journalctl -b -1 the last log in there is from 11:23, way before the reboot. Is there any way I can figure out what caused the shutdown to occur?

I’m on Fedora 43 Workstation with an Nvidia GPU on driver 580.119.02

Any help would be great thanks!

2

The failure to preserve the last part of the journal indicates either a lack of space on the root filesystem or a mass storage hardware problem. The safest approach is to boot a Live USB installer. Then use Gnome Disks or similar tools to check “health” of your storage hardware and the free space. Note that if you are using btrfs, legacy tools often fail to account for metadata, so for btrfs, run btrfs fi us /.

3

Or a bug that crashes the system before it can be written to the journal.

4

Hey so I ran Gnome Disks and the health came back saying undamaged, likewise btrfs didn’t flag anything. I have plenty of space left on my filestem root (over 1TB).

Something I neglected to mention in the post was that I did an update today so it’s likely some process that’s causing it, but again journalctl isn’t being much help.

Is there anything I can do to catch whatever it is in the act?

Cheers

5

How many times has the unexpected shutdown occured?
If it only once it could be a power failure or cosmic ray.

1 Like
6

It’s done it a few times today, at strangely round times e.g. It happened at exactly 11:30am and it’s happened at 6:00pm as well.

I did the update via Gnome Software, in my dnf history I can see 2 Nvidia akmod updates from today, I’ll see if rolling these back helps.

I’m currently away from the machine but will provide detailed journalctl logs when I get back.

Just to rule it out I checked crontab for any jobs on both my local user + root user. I also checked systemctl for any timers. I’ll post all of that as well.

I’m convinced it’s software related but I’m unsure how to rollback from running update via Gnome Software. The update also included a new kernel and I’ve tried selecting the old one in grub as well, that didn’t work.

1 Like
7

To downgrade packages, go to the command line / terminal and type

sudo dnf downgrade packagename

8

Oh interesting, either I misread this earlier or this has updated after the fact, running last reboot now shows that there were indeed crashes at those times when it rebooted:

reboot   system boot  6.18.9-200.fc43* Thu Feb 12 18:11   still running
reboot   system boot  6.18.9-200.fc43* Thu Feb 12 18:03 - 18:07  (00:04)
reboot   system boot  6.18.5-200.fc43* Thu Feb 12 16:00 - crash  (02:02)
reboot   system boot  6.18.9-200.fc43* Thu Feb 12 11:59 - crash  (04:01)
reboot   system boot  6.18.9-200.fc43* Thu Feb 12 11:30 - 11:58  (00:27)
reboot   system boot  6.18.9-200.fc43* Thu Feb 12 10:35 - crash  (00:55)
reboot   system boot  6.18.5-200.fc43* Thu Feb 12 10:32 - 10:34  (00:02)
reboot   system boot  6.18.5-200.fc43* Tue Feb  3 12:07 - 10:31 (8+22:24)

My update finished and rebooted on 10:35, 55 minutes later at 11:30 it crashed. Later on at 16:00 it crashed, and again at apparently 18:02.

11:00 to 11:30 journalctl -b -5:

Feb 12 11:01:00 Apollo.localdomain CROND[40123]: (root) CMD (run-parts /etc/cron.hourly)
Feb 12 11:01:00 Apollo.localdomain run-parts[40126]: (/etc/cron.hourly) starting 0anacron
Feb 12 11:01:00 Apollo.localdomain run-parts[40132]: (/etc/cron.hourly) finished 0anacron
Feb 12 11:01:00 Apollo.localdomain CROND[40122]: (root) CMDEND (run-parts /etc/cron.hourly)
Feb 12 11:02:36 Apollo.localdomain NetworkManager[1568]: <info>  [1770894156.8124] device (wlp7s0): set-hw-addr: set MAC address to 56:9D:62:A4:64:EB (scanning)
Feb 12 11:02:36 Apollo.localdomain NetworkManager[1568]: <info>  [1770894156.8902] device (wlp7s0): supplicant interface state: inactive -> interface_disabled
Feb 12 11:02:36 Apollo.localdomain NetworkManager[1568]: <info>  [1770894156.8902] device (p2p-dev-wlp7s0): supplicant management interface state: inactive -> interface_disabled
Feb 12 11:02:36 Apollo.localdomain NetworkManager[1568]: <info>  [1770894156.8992] device (wlp7s0): supplicant interface state: interface_disabled -> inactive
Feb 12 11:02:36 Apollo.localdomain NetworkManager[1568]: <info>  [1770894156.8992] device (p2p-dev-wlp7s0): supplicant management interface state: interface_disabled -> inactive
Feb 12 11:09:30 Apollo.localdomain NetworkManager[1568]: <info>  [1770894570.8144] device (wlp7s0): set-hw-addr: set MAC address to EE:EF:3E:99:EF:06 (scanning)
Feb 12 11:09:30 Apollo.localdomain NetworkManager[1568]: <info>  [1770894570.8921] device (wlp7s0): supplicant interface state: inactive -> interface_disabled
Feb 12 11:09:30 Apollo.localdomain NetworkManager[1568]: <info>  [1770894570.8922] device (p2p-dev-wlp7s0): supplicant management interface state: inactive -> interface_disabled
Feb 12 11:09:30 Apollo.localdomain NetworkManager[1568]: <info>  [1770894570.9022] device (wlp7s0): supplicant interface state: interface_disabled -> inactive
Feb 12 11:09:30 Apollo.localdomain NetworkManager[1568]: <info>  [1770894570.9022] device (p2p-dev-wlp7s0): supplicant management interface state: interface_disabled -> inactive
Feb 12 11:16:24 Apollo.localdomain NetworkManager[1568]: <info>  [1770894984.8214] device (wlp7s0): set-hw-addr: set MAC address to 36:5A:C8:BE:A4:3C (scanning)
Feb 12 11:16:24 Apollo.localdomain NetworkManager[1568]: <info>  [1770894984.8992] device (wlp7s0): supplicant interface state: inactive -> interface_disabled
Feb 12 11:16:24 Apollo.localdomain NetworkManager[1568]: <info>  [1770894984.8992] device (p2p-dev-wlp7s0): supplicant management interface state: inactive -> interface_disabled
Feb 12 11:16:24 Apollo.localdomain NetworkManager[1568]: <info>  [1770894984.9172] device (wlp7s0): supplicant interface state: interface_disabled -> inactive
Feb 12 11:16:24 Apollo.localdomain NetworkManager[1568]: <info>  [1770894984.9172] device (p2p-dev-wlp7s0): supplicant management interface state: interface_disabled -> inactive
Feb 12 11:20:40 Apollo.localdomain slack[32271]: App Icon is not available when using Portal Notifications
Feb 12 11:21:16 Apollo.localdomain slack[32271]: App Icon is not available when using Portal Notifications
Feb 12 11:21:38 Apollo.localdomain slack[32271]: App Icon is not available when using Portal Notifications
Feb 12 11:23:18 Apollo.localdomain NetworkManager[1568]: <info>  [1770895398.8164] device (wlp7s0): set-hw-addr: set MAC address to 72:EF:67:D4:6A:EF (scanning)
Feb 12 11:23:18 Apollo.localdomain NetworkManager[1568]: <info>  [1770895398.8942] device (wlp7s0): supplicant interface state: inactive -> interface_disabled
Feb 12 11:23:18 Apollo.localdomain NetworkManager[1568]: <info>  [1770895398.8942] device (p2p-dev-wlp7s0): supplicant management interface state: inactive -> interface_disabled
Feb 12 11:23:18 Apollo.localdomain NetworkManager[1568]: <info>  [1770895398.9152] device (wlp7s0): supplicant interface state: interface_disabled -> inactive
Feb 12 11:23:18 Apollo.localdomain NetworkManager[1568]: <info>  [1770895398.9153] device (p2p-dev-wlp7s0): supplicant management interface state: interface_disabled -> inactive
Feb 12 11:23:20 Apollo.localdomain slack[32271]: App Icon is not available when using Portal Notifications
Feb 12 11:23:20 Apollo.localdomain gnome-shell[16155]: Could not find the icon 'status_icon_4-ltr'. The 'hicolor' theme
                                                       was not found either, perhaps you need to install it.
                                                       You can get a copy from:
                                                               http://icon-theme.freedesktop.org/releases
Feb 12 11:23:49 Apollo.localdomain slack[32271]: App Icon is not available when using Portal Notifications

16:00 to 16:30 journalctl -b -3:

Feb 12 15:32:01 Apollo.localdomain gnome-shell[4788]: Received error from D-Bus search provider org.gnome.Boxes.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name “org.gnome.Boxes.SearchProvider” without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Feb 12 15:32:01 Apollo.localdomain systemd[4205]: Started dbus-:1.2-org.gnome.Calculator.SearchProvider@8.service.
Feb 12 15:32:01 Apollo.localdomain systemd[4205]: Started dbus-:1.2-org.gnome.Characters@8.service.
Feb 12 15:32:01 Apollo.localdomain systemd[4205]: Started dbus-:1.2-org.gnome.Nautilus@8.service.
Feb 12 15:32:01 Apollo.localdomain systemd[4205]: Started dbus-:1.2-org.gnome.Settings.SearchProvider@7.service.
Feb 12 15:32:01 Apollo.localdomain systemd[4205]: Started dbus-:1.2-org.gnome.clocks@8.service.
Feb 12 15:32:01 Apollo.localdomain org.gnome.Nautilus[74476]: Connecting to org.freedesktop.Tracker3.Miner.Files
Feb 12 15:32:02 Apollo.localdomain org.gnome.Characters[74475]: JS LOG: Characters Application started
Feb 12 15:32:02 Apollo.localdomain nautilus[74476]: detected unhandled Python exception in 'nautilus'
Feb 12 15:32:02 Apollo.localdomain nautilus[74476]: Traceback (most recent call last):
Feb 12 15:32:02 Apollo.localdomain nautilus[74476]:   File "<string>", line 1, in <module>
Feb 12 15:32:02 Apollo.localdomain nautilus[74476]:   File "/usr/lib64/python3.14/site-packages/gi/__init__.py", line 135, in require_version
Feb 12 15:32:02 Apollo.localdomain nautilus[74476]:     raise ValueError(f"Namespace {namespace} not available for version {version}")
Feb 12 15:32:02 Apollo.localdomain nautilus[74476]: ValueError: Namespace Nautilus not available for version 4.0
Feb 12 15:32:02 Apollo.localdomain nautilus[74476]: <sys>:0: PyGIWarning: Nautilus was imported without specifying a version first. Use gi.require_version('Nautilus', '4.1') before import to ensure that the right version gets loaded.
Feb 12 15:32:02 Apollo.localdomain gnome-shell[4788]: Received error from D-Bus search provider org.gnome.Boxes.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name “org.gnome.Boxes.SearchProvider” without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Feb 12 15:32:02 Apollo.localdomain org.gnome.Nautilus[74476]: Localsearch search engine has no connection
Feb 12 15:32:02 Apollo.localdomain org.gnome.Nautilus[74476]: Localsearch search engine has no connection
Feb 12 15:32:02 Apollo.localdomain systemd[4205]: Started dbus-:1.2-org.gnome.NautilusPreviewer@8.service.
Feb 12 15:32:02 Apollo.localdomain gnome-shell[4788]: Received error from D-Bus search provider org.gnome.Boxes.desktop: Gio.IOErrorEnum: Cannot invoke method; proxy is for the well-known name “org.gnome.Boxes.SearchProvider” without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag
Feb 12 15:32:02 Apollo.localdomain systemd[4205]: Started dbus-:1.2-org.gnome.TextEditor@0.service.
Feb 12 15:32:02 Apollo.localdomain systemd[1]: Starting packagekit.service - PackageKit Daemon...
Feb 12 15:32:02 Apollo.localdomain PackageKit[74836]: daemon start
Feb 12 15:32:02 Apollo.localdomain systemd[1]: Started packagekit.service - PackageKit Daemon.
Feb 12 15:32:02 Apollo.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 12 15:32:03 Apollo.localdomain PackageKit[74836]: resolve transaction /7559_bebbeaed from uid 1000 finished with success after 402ms
Feb 12 15:32:12 Apollo.localdomain org.gnome.Characters[74475]: JS LOG: Characters Application exiting
Feb 12 15:32:14 Apollo.localdomain nautilus[74476]: cannot connect to dbus service: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Feb 12 15:33:00 Apollo.localdomain NetworkManager[1496]: <info>  [1770910380.8265] device (wlp7s0): set-hw-addr: set MAC address to 4A:D3:CF:90:50:0A (scanning)
Feb 12 15:33:00 Apollo.localdomain NetworkManager[1496]: <info>  [1770910380.9043] device (wlp7s0): supplicant interface state: inactive -> interface_disabled
Feb 12 15:33:00 Apollo.localdomain NetworkManager[1496]: <info>  [1770910380.9043] device (p2p-dev-wlp7s0): supplicant management interface state: inactive -> interface_disabled
Feb 12 15:33:00 Apollo.localdomain NetworkManager[1496]: <info>  [1770910380.9194] device (wlp7s0): supplicant interface state: interface_disabled -> inactive
Feb 12 15:33:00 Apollo.localdomain NetworkManager[1496]: <info>  [1770910380.9194] device (p2p-dev-wlp7s0): supplicant management interface state: interface_disabled -> inactive
Feb 12 15:37:07 Apollo.localdomain PackageKit[74836]: daemon quit
Feb 12 15:37:07 Apollo.localdomain systemd[1]: packagekit.service: Deactivated successfully.
Feb 12 15:37:07 Apollo.localdomain audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=packagekit comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 12 15:37:07 Apollo.localdomain systemd[1]: packagekit.service: Consumed 439ms CPU time, 102M memory peak.
Feb 12 15:38:00 Apollo.localdomain gnome-text-editor[74759]: Trying to snapshot GtkGizmo 0x55c9b5314730 without a current allocation
Feb 12 15:39:54 Apollo.localdomain NetworkManager[1496]: <info>  [1770910794.8365] device (wlp7s0): set-hw-addr: set MAC address to BA:90:93:E3:2B:4F (scanning)
Feb 12 15:39:54 Apollo.localdomain NetworkManager[1496]: <info>  [1770910794.9142] device (wlp7s0): supplicant interface state: inactive -> interface_disabled
Feb 12 15:39:54 Apollo.localdomain NetworkManager[1496]: <info>  [1770910794.9143] device (p2p-dev-wlp7s0): supplicant management interface state: inactive -> interface_disabled
Feb 12 15:39:54 Apollo.localdomain NetworkManager[1496]: <info>  [1770910794.9294] device (wlp7s0): supplicant interface state: interface_disabled -> inactive
Feb 12 15:39:54 Apollo.localdomain NetworkManager[1496]: <info>  [1770910794.9294] device (p2p-dev-wlp7s0): supplicant management interface state: interface_disabled -> inactive
Feb 12 15:46:48 Apollo.localdomain NetworkManager[1496]: <info>  [1770911208.8376] device (wlp7s0): set-hw-addr: set MAC address to 8E:62:8C:75:41:83 (scanning)
Feb 12 15:46:48 Apollo.localdomain NetworkManager[1496]: <info>  [1770911208.9153] device (wlp7s0): supplicant interface state: inactive -> interface_disabled
Feb 12 15:46:48 Apollo.localdomain NetworkManager[1496]: <info>  [1770911208.9153] device (p2p-dev-wlp7s0): supplicant management interface state: inactive -> interface_disabled
Feb 12 15:46:48 Apollo.localdomain NetworkManager[1496]: <info>  [1770911208.9304] device (wlp7s0): supplicant interface state: interface_disabled -> inactive
Feb 12 15:46:48 Apollo.localdomain NetworkManager[1496]: <info>  [1770911208.9304] device (p2p-dev-wlp7s0): supplicant management interface state: interface_disabled -> inactive
Feb 12 15:52:43 Apollo.localdomain cupsd[1539]: REQUEST localhost - - "POST / HTTP/1.1" 200 192 Renew-Subscription successful-ok
Feb 12 15:53:42 Apollo.localdomain NetworkManager[1496]: <info>  [1770911622.8255] device (wlp7s0): set-hw-addr: set MAC address to 1A:4A:12:A5:C7:D2 (scanning)
Feb 12 15:53:42 Apollo.localdomain NetworkManager[1496]: <info>  [1770911622.9033] device (wlp7s0): supplicant interface state: inactive -> interface_disabled
Feb 12 15:53:42 Apollo.localdomain NetworkManager[1496]: <info>  [1770911622.9034] device (p2p-dev-wlp7s0): supplicant management interface state: inactive -> interface_disabled
Feb 12 15:53:42 Apollo.localdomain NetworkManager[1496]: <info>  [1770911622.9235] device (wlp7s0): supplicant interface state: interface_disabled -> inactive
Feb 12 15:53:42 Apollo.localdomain NetworkManager[1496]: <info>  [1770911622.9235] device (p2p-dev-wlp7s0): supplicant management interface state: interface_disabled -> inactive

Moments leading up to 18:02 journalctl -b -2 (this one had a lot of OBS logging so decided to omit):

Feb 12 17:59:38 Apollo.localdomain org.gnome.Characters[20352]: JS LOG: Characters Application exiting
Feb 12 17:59:40 Apollo.localdomain nautilus[20353]: cannot connect to dbus service: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Feb 12 17:59:53 Apollo.localdomain systemd[4253]: app-flatpak-io.missioncenter.MissionCenter-3083710389.scope: Consumed 2.342s CPU time, 158.8M memory peak.
Feb 12 18:00:32 Apollo.localdomain org.mozilla.firefox.desktop[11408]: [Parent 1437, Main Thread] WARNING: Failed to enumerate devices of org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
Feb 12 18:00:32 Apollo.localdomain org.mozilla.firefox.desktop[11408]: : 'glib warning', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:201
Feb 12 18:00:32 Apollo.localdomain firefox-bin[11408]: Failed to enumerate devices of org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
Feb 12 18:01:00 Apollo.localdomain CROND[21659]: (root) CMD (run-parts /etc/cron.hourly)
Feb 12 18:01:00 Apollo.localdomain run-parts[21662]: (/etc/cron.hourly) starting 0anacron
Feb 12 18:01:00 Apollo.localdomain run-parts[21668]: (/etc/cron.hourly) finished 0anacron
Feb 12 18:01:00 Apollo.localdomain CROND[21658]: (root) CMDEND (run-parts /etc/cron.hourly)
Feb 12 18:01:44 Apollo.localdomain org.mozilla.firefox.desktop[11408]: [Parent 1437, Main Thread] WARNING: Failed to enumerate devices of org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
Feb 12 18:01:44 Apollo.localdomain org.mozilla.firefox.desktop[11408]: : 'glib warning', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:201
Feb 12 18:01:44 Apollo.localdomain firefox-bin[11408]: Failed to enumerate devices of org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown

There doesn’t seem to be any common thread, nothing loud and shouty anyway.

We did have a power-cut a few weeks ago and maybe I just got really unlucky today with a few surges but I’m still somewhat convinced it’s a software issue because it’s very coincidental after updates.

To downgrade packages, go to the command line / terminal and type

Is there a way to list what packages Gnome Software will have updated? In my dnf history list I only see the Nvidia akmod rpm’s.

9

If your vendor provides diagnostics, run them. You can also run memtest86+, if possible, overnight for several nights.

Older or low quality systems sometimes suffer from power glitches/noise caused by failed capacitors. Positive diagnosis requires test equipment or, for desktops, swapping with a known good power supply. Sometimes visual inspection can find a cracked capacitor on laptops or a bulging top on desktop system boards https://techcircuit.org/electrolytic-capacitor-failures/.

10

Which packages were part of the last upgrade?

sudo dnf history info last
11

If I remember correctly, Gnome is still on DNF 4, while command line defaults to DNF 5 - so run from the command line

dnf4 history list
and
dnf5 history list

1 Like
12

These are almost at regular times, but not exact, so I don’t think its an automated or time based crash.

Run journalctr for the couple if minutes leading up to these times.

If we can’t see anything there, I would not rule out a hardware error. Try teseating RAM and SSD, other plugs too if you are not on a laptop.

1 Like
13

Aha! That was the ticket thanks, over 300 packages in that upgrade:

I’ll undo the transaction and try to upgrade like performing a binary search and see if I can find the issue. May take a few days.

My machine didn’t reboot overnight but it wasn’t being used so that’s another data point, it’s likely an app (or spawned process) I’m using.

I’ve also been tempted to move to SilverBlue, if I keep running into the issue with no luck it might push me toward it, more for peace of mind rollbacks.

14

Yep thanks, I’m not ruling out hardware but it would just be incredibly coincidental that it happened within an hour of performing updates on a system that’s relatively new (built within last 2 years) and has never had a hitch before. I dual boot Windows (though not used for some time) so could try using that for a couple of days and if that also crashes then I know it’s hardware

2 Likes
15

Update on this:
While doing pretty much nothing (because I hadn’t gotten around to it), and using the system in exactly the same way. I haven’t had any crashes or reboots in the 3 days since I last posted. My uptime is over 2½ days now.

The only thing I can think of that I haven’t done, which I usually would have, is to use modprobe to setup v4l2loopback via scrcpy for my android phone because I’ve opted to stream that differently.

I wish I could definitively mark something as a solution but since I can’t reliably make it crash at all it’s hard to test. Thank you everyone for helping out, and sorry this ultimately didn’t have a satisfying resolution but for now I think this is “solved” in some way.

2 Likes
16

Another update:

Ironically it crashed again a few hours after my last reply but at that point I opened scrcpy and OBS studio! So a week on where I haven’t been using these 2 apps and I haven’t had any more crashes so I think I’ve narrowed it down.

OBS also detects that it has shut down uncleanly after it reboots which makes it my top contender, but unfortunately doesn’t write anything useful out to a log. It’s also possibly scrcpy, in my last response I thought it could be due to using v4l2loopback as a sink for it, but I’ve since elected to have it open a window and window capture it inside OBS and I still get a crash.

Basically, if I don’t stream my webcam I don’t get any crashes, the ultimate privacy tool.

Progress is slow but I’ll do some more sleuthing when I can.

1 Like
17

Have you enabled kdump to try to capture these dumps with when they do happen?

See kdumpctl and kdump.conf

Might not help at all, but one never knows.

1 Like
18

Quoting https://obsproject.com/kb/known-conflicts —

Several 3rd party applications can interfere with the correct operation of OBS Studio. These applications usually hook graphics functions that OBS Studio also wants to hook, which can result in crashes or other strange behavior. If you have any of these applications installed, consider disabling or removing them if you’re experiencing issues.

1 Like
19

I’ve not tried this before, I was following the RHEL guide:

Unfortunately, I’m having difficulty setting it up and I think it’s possibly due to secure boot being enabled on this machine. After setting GRUB’s crashkernel option to auto I don’t get any space reserved on boot and kdumpctl fails to start the kdump service. I wonder now if I actually am having a kernel panic after all, and it simply isn’t being caught due to this, is that a possible deduction?

I need secure boot enabled for my Windows partition, I’m not too certain of the repercussions of disabling it temporarily to figure this out. I’m beginning to wonder if I can repro this in a VM instead rather than mess about with my main system now.

20

Thanks, I don’t seem to have any of these installed, other than SELinux which I haven’t tampered with.