I guess your random reboots are not related to that ACPI bug.

When restarting from a unexpected random reboot, check last lines of syslog for some kind of crash or fatal error.

OK, thanks! I've dumped the log from approximately one minute and thirty seconds before, and one minute and thirty seconds after the incident. If you can spot anything related to the crash, I'd be really grateful 🙏🏻. If not, I'll have to wait for the next occurrence.

https://cd.wedos.com/s/K2tf8zW25FKNfEa

Hello welblaud,

Have you checked if RAM is functioning properly?

Follow this tutorial: https://slimbook.com/en/blog/guides-2/post/rule-out-ram-failure-error-with-memtest86-356

Best regards.

Thanks, @Vaja Benidze. I ran it, and it passed without any errors (I have 2×32GB). This leads me to two observations or ideas:

1. The issue does not occur often, but when it does, it seems to be somehow associated with watching videos on YouTube OR watching videos on YouTube while something is running in the background (I use Toolbox and Podman heavily).
2. The strange thing is that it leads to a total failure, which resembles something like a kernel error.

For now, I consider the situation stable. If it occurs again, I'll try to gather more information and post an update.

Hello again,

I’ve continued investigating the issue, and I believe I’ve found the key log entry that might be crucial:

x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks

I’m happy to report this issue myself if you can guide me to the right place, or I’d appreciate it if you could forward this information to the relevant team.

The crash occurred during normal browsing of a static webpage with minimal JavaScript. No heavy multimedia content was involved this time, but the behavior remains consistent with a complete system restart (not just GNOME or Firefox crashing). It might also be worth mentioning that I am using a 'Slimbook Small Dock' with my setup. While I’m not sure if it’s related, it could potentially play a role in this issue.

Here’s the full log context for reference:

led 22 20:34:34 slimbook rpm-ostree[93771]: In idle state; will auto-exit in 61 seconds
led 22 20:34:44 slimbook rpm-ostree[93771]: Allowing active client :1.6364 (uid 1000)
led 22 20:34:44 slimbook rpm-ostree[93771]: client(id:cli dbus:1.6364 unit:[email protected] uid:1000) added; new total=1
led 22 20:34:44 slimbook rpm-ostree[93771]: client(id:cli dbus:1.6364 unit:[email protected] uid:1000) vanished; remaining=0
led 22 20:34:44 slimbook rpm-ostree[93771]: In idle state; will auto-exit in 63 seconds
led 22 20:34:52 slimbook org.mozilla.firefox.desktop[386522]: [Parent 2, Main Thread] WARNING: Failed to enumerate devices of org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
led 22 20:34:52 slimbook org.mozilla.firefox.desktop[386522]: : 'glib warning', file /builds/worker/checkouts/gecko/toolkit/xre/nsSigHandlers.cpp:201
led 22 20:34:52 slimbook firefox-bin[386522]: Failed to enumerate devices of org.freedesktop.UPower: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown
led 22 20:34:54 slimbook rpm-ostree[93771]: Allowing active client :1.6367 (uid 1000)
led 22 20:34:54 slimbook rpm-ostree[93771]: client(id:cli dbus:1.6367 unit:[email protected] uid:1000) added; new total=1
led 22 20:34:54 slimbook rpm-ostree[93771]: client(id:cli dbus:1.6367 unit:[email protected] uid:1000) vanished; remaining=0
led 22 20:34:54 slimbook rpm-ostree[93771]: In idle state; will auto-exit in 62 seconds
-- Boot e2a114c16caf4ba2b99dfb5a6921726e --
led 22 20:35:25 fedora kernel: Linux version 6.12.9-200.fc41.x86_64 (mockbuild@ff27ee54c23b4f1ab915082a1b1c8b7e) (gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3), GNU ld version 2.43.1-5.fc41) #1 SMP PREEMPT_DYNAMIC Thu Jan  9 16:05:40 UTC 2025
led 22 20:35:25 fedora kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/ostree/fedora-1b575fded85a5a6842bc4a4305a82a031aa0380f231af2d5233e6480c88cea1b/vmlinuz-6.12.9-200.fc41.x86_64 rhgb quiet root=UUID=90c8853c-1590-48f6-bfa6-3bfed9f70c23 rootflags=subvol=root rw ostree=/ostree/boot.0/fedora/1b575fded85a5a6842bc4a4305a82a031aa0380f231af2d5233e6480c88cea1b/0
led 22 20:35:25 fedora kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
led 22 20:35:25 fedora kernel: BIOS-provided physical RAM map:
led 22 20:35:25 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009dfff] usable

Just another one log. It resembles the previous. It is interesting the split_locks happens after the boot, hence it probably is not the cause. For now, the Shell@wayland lines are a bit more suspicious. Again, I was just reading something in Firefox.

led 23 18:53:17 slimbook NetworkManager[1331]: <info>  [1737654797.7638] device (wg0): state change: config -> ip-config (reason 'none', managed-type: 'full')
led 23 18:53:17 slimbook systemd-resolved[1152]: enp0s13f0u1u2c2: Bus client set default route setting: no
led 23 18:53:17 slimbook systemd-resolved[1152]: enp0s13f0u1u2c2: Bus client reset DNS server list.
led 23 18:53:17 slimbook systemd-resolved[1152]: wg0: Bus client set default route setting: yes
led 23 18:53:17 slimbook systemd-resolved[1152]: wg0: Bus client set DNS server list to: 100.64.0.7
led 23 18:53:17 slimbook NetworkManager[1331]: <info>  [1737654797.7804] device (wg0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')
led 23 18:53:17 slimbook NetworkManager[1331]: <info>  [1737654797.7823] device (wg0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')
led 23 18:53:17 slimbook NetworkManager[1331]: <info>  [1737654797.7825] device (wg0): state change: secondaries -> activated (reason 'none', managed-type: 'full')
led 23 18:53:17 slimbook NetworkManager[1331]: <info>  [1737654797.7829] manager: NetworkManager state is now CONNECTED_SITE
led 23 18:53:17 slimbook NetworkManager[1331]: <info>  [1737654797.7832] device (wg0): Activation: successful, device activated.
led 23 18:53:17 slimbook geoclue[1891]: Failed to query location: Query location SOUP error: Not Found
led 23 18:53:18 slimbook NetworkManager[1331]: <info>  [1737654798.0484] manager: NetworkManager state is now CONNECTED_GLOBAL
led 23 18:53:20 slimbook rpm-ostree[96321]: Allowing active client :1.6011 (uid 1000)
led 23 18:53:20 slimbook rpm-ostree[96321]: client(id:cli dbus:1.6011 unit:[email protected] uid:1000) added; new total=1
led 23 18:53:20 slimbook rpm-ostree[96321]: client(id:cli dbus:1.6011 unit:[email protected] uid:1000) vanished; remaining=0
led 23 18:53:20 slimbook rpm-ostree[96321]: In idle state; will auto-exit in 63 seconds
led 23 18:53:28 slimbook systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
led 23 18:53:28 slimbook audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" host>
led 23 18:53:30 slimbook rpm-ostree[96321]: Allowing active client :1.6014 (uid 1000)
led 23 18:53:30 slimbook rpm-ostree[96321]: client(id:cli dbus:1.6014 unit:[email protected] uid:1000) added; new total=1
led 23 18:53:30 slimbook rpm-ostree[96321]: client(id:cli dbus:1.6014 unit:[email protected] uid:1000) vanished; remaining=0
led 23 18:53:30 slimbook rpm-ostree[96321]: In idle state; will auto-exit in 64 seconds
-- Boot 41ec9bc11cc14ec5b93b84c99c49b801 --
led 23 18:53:59 fedora kernel: Linux version 6.12.9-200.fc41.x86_64 (mockbuild@ff27ee54c23b4f1ab915082a1b1c8b7e) (gcc (GCC) 14.2.1 20240912 (Red Hat 14.2.1-3), GNU ld version 2.43.1-5.fc41) #1 SMP PREEMPT_DYNAM>
led 23 18:53:59 fedora kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/ostree/fedora-1b575fded85a5a6842bc4a4305a82a031aa0380f231af2d5233e6480c88cea1b/vmlinuz-6.12.9-200.fc41.x86_64 rhgb quiet root=UUID=90c8853c-159>
led 23 18:53:59 fedora kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
led 23 18:53:59 fedora kernel: BIOS-provided physical RAM map:

Hello welblaud,

I’m going to make some suggestions to try to isolate the issues:

1. Does this also happen while running on battery mode, or only when connected to the power supply? I assume you are using the original charger.

2. Update the BIOS and EC by following this tutorial: https://slimbook.com/en/blog/guides-2/post/how-to-update-bios-and-ec-on-your-slimbook-377
   

3. Verify that "Secure Boot" is disabled in the BIOS settings.

4. Reinstall Fedora.

If you continue to experience issues, we recommend contacting technical support through this link: https://slimbook.com/en/support

Best regards.

For now, it seems the issue was caused by the graphics card driver or the kernel. It typically occurred a few minutes after watching videos. Initially, I tried disabling hardware acceleration in browsers, which seemed to help. A few days later, Fedora released a major update for Mesa and Vulkan drivers. With that update, I decided to re-enable hardware acceleration—and since then, the issue appears to have stopped happening 🎉 I hope it's fully resolved!