Random system reset / reboot

English Applications
1

I am experiencing random system resets. This has happened in the past, shortly after purchasing this computer. After returning the computer to the shop several times a few years ago, the issue seemed finally resolved. No “smoking gun” was ever found. One difference: I had been using Fedora Linux, and for some unknown reason, the tech had switched me to Garuda Linux (he was a gamer-dude type). After that, I never suffered resets, until now. I recently switched to openSUSE Leap, after update issues with Garuda. Could there be something Fedora-openSUSE related? My CPU is not over-heating; I have recently improved the heat-sink mounting, and the CPU is running cooler than ever. I have tried running journalctl -b -1 -e without finding the culprit. Beyond that, I don’t know where to even begin. Please help.

# inxi -GSat
System:
  Host: localhost.localdomain Kernel: 6.12.0-160000.36-default arch: x86_64
    bits: 64 compiler: gcc v: 13.4.0 clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.0-160000.36-default
    root=UUID=ff113b6e-a2be-43c4-a297-4ed5a127ff67 splash=silent
    mitigations=auto quiet security=selinux selinux=1
  Desktop: KDE Plasma v: 6.4.2 tk: Qt v: N/A info: frameworks v: 6.16.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: openSUSE Leap 16.0
Graphics:
  Device-1: Intel CoffeeLake-S GT2 [UHD Graphics 630] vendor: ASUSTeK
    driver: i915 v: kernel arch: Gen-9.5 process: Intel 14nm built: 2016-20
    ports: active: HDMI-A-3 empty: DP-1, DP-2, DP-3, HDMI-A-1, HDMI-A-2
    bus-ID: 00:02.0 chip-ID: 8086:3e98 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.15 with: Xwayland v: 24.1.6
    compositor: kwin_x11 driver: X: loaded: modesetting unloaded: vesa
    alternate: fbdev,intel dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
    s-diag: 582mm (22.93")
  Monitor-1: HDMI-A-3 mapped: HDMI-3 model: ViewSonic VX3276-FHD
    serial: V9X200262658 built: 2020 res: 1920x1080 hz: 60 dpi: 70 gamma: 1.2
    size: 698x393mm (27.48x15.47") diag: 801mm (31.5") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
    inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.3.3 glx-v: 1.4
    direct-render: yes renderer: Mesa Intel UHD Graphics 630 (CFL GT2)
    device-ID: 8086:3e98 memory: 7.53 GiB unified: yes
  API: Vulkan Message: No Vulkan data available.
Processes:
  CPU top: 5 of 279
  1: cpu: 21.9% command: chrome pid: 2051 mem: 204.4 MiB (1.2%)
  2: cpu: 18.9% command: chrome pid: 2261 mem: 484.7 MiB (3.0%)
  3: cpu: 11.1% command: Xorg.bin pid: 1172 mem: 120.7 MiB (0.7%)
  4: cpu: 9.3% command: plasmashell pid: 1658 mem: 415.1 MiB (2.6%)
  5: cpu: 7.7% command: kwin_x11 pid: 1517 mem: 232.0 MiB (1.4%)
  System RAM: total: 16 GiB available: 15.42 GiB used: 4.83 GiB (31.3%)
  Memory top: 5 of 279
  1: mem: 555.7 MiB (3.5%) command: chrome pid: 1969 cpu: 2.4%
  2: mem: 493.5 MiB (3.1%) command: soffice.bin pid: 9640 cpu: 0.8%
  3: mem: 484.7 MiB (3.0%) command: chrome pid: 2261 cpu: 18.9%
  4: mem: 456.7 MiB (2.8%) command: chrome pid: 2221 cpu: 2.4%
  5: mem: 452.0 MiB (2.8%) command: chrome pid: 2533 cpu: 0.9%
2

Hi, I seem to be experiencing the same problem with my Leap 16. I at first thought this was dirty extraction, cleaned this and replaced paste. then it seemed as thought the Brave browser was at fault, seemed to happen quite quickly when using youtube. however, monitoring the CPU temp shows a max of 65 degrees C and it happened, any ideas?

this is the kernel dump logs I have copied from Cockpit
August 8, 2026
11:23 PM
vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME=“vboxnetctl”.
(udev-worker)
11:23 PM
Device: /dev/sdb [SAT], 16 Currently unreadable (pending) sectors
smartd
11:23 PM
vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME=“vboxdrv”.
(udev-worker)
11:23 PM
vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME=“vboxdrvu”.
(udev-worker)
11:23 PM
spi-nor spi0.1: probe with driver spi-nor failed with error -22
kernel
11:23 PM
spi-nor spi0.0: probe with driver spi-nor failed with error -22
kernel
Reboot
6:21 PM
Device: /dev/sdb [SAT], 16 Currently unreadable (pending) sectors
smartd
6:21 PM
vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME=“vboxnetctl”.
(udev-worker)
6:21 PM
vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME=“vboxdrv”.
(udev-worker)
6:21 PM
vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME=“vboxdrvu”.
(udev-worker)
6:20 PM
spi-nor spi0.1: probe with driver spi-nor failed with error -22
kernel
6:20 PM
spi-nor spi0.0: probe with driver spi-nor failed with error -22
kernel
Reboot
6:19 PM
Device: /dev/sdb [SAT], 16 Currently unreadable (pending) sectors
smartd
6:19 PM
vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME=“vboxnetctl”.
(udev-worker)
6:19 PM
vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME=“vboxdrv”.
(udev-worker)
6:19 PM
vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME=“vboxdrvu”.
(udev-worker)
6:19 PM
spi-nor spi0.1: probe with driver spi-nor failed with error -22
kernel
6:19 PM
spi-nor spi0.0: probe with driver spi-nor failed with error -22
kernel
Reboot
6:09 PM
Device: /dev/sdb [SAT], 16 Currently unreadable (pending) sectors
smartd
6:09 PM
vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME=“vboxnetctl”.
(udev-worker)
6:09 PM
vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME=“vboxdrv”.
(udev-worker)
6:09 PM
vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME=“vboxdrvu”.
(udev-worker)
6:09 PM
spi-nor spi0.1: probe with driver spi-nor failed with error -22
kernel
6:09 PM
spi-nor spi0.0: probe with driver spi-nor failed with error -22
kernel
Reboot
5:51 PM
Device: /dev/sdb [SAT], 16 Currently unreadable (pending) sectors
smartd
5:51 PM
vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME=“vboxnetctl”.
(udev-worker)
5:51 PM
vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME=“vboxdrv”.
(udev-worker)
5:51 PM
vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME=“vboxdrvu”.
(udev-worker)
5:51 PM
spi-nor spi0.1: probe with driver spi-nor failed with error -22
kernel
5:51 PM
spi-nor spi0.0: probe with driver spi-nor failed with error -22
kernel
Reboot
5:09 PM
Device: /dev/sdb [SAT], 16 Currently unreadable (pending) sectors
smartd
2Occurrences
4:55 PM
rtlwifi: AP off, try to reconnect now
kernel
3:09 PM
Device: /dev/sdb [SAT], 16 Currently unreadable (pending) sectors
smartd
4Occurrences
2:38 PM
vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME=“vboxnetctl”.
(udev-worker)
2:38 PM
Device: /dev/sdb [SAT], 16 Currently unreadable (pending) sectors
smartd
2:38 PM
vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME=“vboxdrvu”.
(udev-worker)
2:38 PM
vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME=“vboxdrv”.
(udev-worker)
2:38 PM
spi-nor spi0.1: probe with driver spi-nor failed with error -22
kernel
2:38 PM
spi-nor spi0.0: probe with driver spi-nor failed with error -22
kernel
Reboot
2:32 PM
Device: /dev/sdb [SAT], 16 Currently unreadable (pending) sectors
smartd
2:28 PM
rtlwifi: AP off, try to reconnect now
kernel
2:02 PM
vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME=“vboxnetctl”.
(udev-worker)
2:02 PM
Device: /dev/sdb [SAT], 16 Currently unreadable (pending) sectors
smartd
2:02 PM
vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME=“vboxdrv”.
(udev-worker)
2:02 PM
vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME=“vboxdrvu”.
(udev-worker)
2:02 PM
spi-nor spi0.1: probe with driver spi-nor failed with error -22
kernel
2:02 PM
spi-nor spi0.0: probe with driver spi-nor failed with error -22
kernel

WARNING AND ABOVE

August 8, 2026
6:21 PM
drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.
systemd
6:21 PM
Service file ‘/usr/share//dbus-1/services/org.kde.plasma.Notifications.service’ is not named after the D-Bus name ‘org.freedesktop.Notifications’.
dbus-broker-launch
6:21 PM
Service file ‘/usr/share//dbus-1/services/org.kde.kscreen.service’ is not named after the D-Bus name ‘org.kde.KScreen’.
dbus-broker-launch
6:21 PM
Service file ‘/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service’ is not named after the D-Bus name ‘org.freedesktop.FileManager1’.
dbus-broker-launch
6:21 PM
Service file ‘/usr/share//dbus-1/services/org.jackaudio.service’ is not named after the D-Bus name ‘org.jackaudio.service’.
dbus-broker-launch
6:21 PM
drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.
systemd
6:21 PM
Device: /dev/sdb [SAT], 16 Currently unreadable (pending) sectors
smartd
6:21 PM
vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME=“vboxnetctl”.
(udev-worker)
6:21 PM
VBoxNetAdp: Successfully started.
kernel
6:21 PM
VBoxNetFlt: Successfully started.
kernel
6:21 PM
rtR0InitNative: g_pLnxInitMm=0000000034e98b79
kernel
6:21 PM
vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME=“vboxdrv”.
(udev-worker)
6:21 PM
vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME=“vboxdrvu”.
(udev-worker)
6:21 PM
vboxdrv: loading out-of-tree module taints kernel.
kernel
6:21 PM
src/plugin.c:init_plugin() System does not support asha plugin
bluetoothd
6:21 PM
src/plugin.c:init_plugin() System does not support csip plugin
bluetoothd
6:21 PM
src/plugin.c:init_plugin() System does not support ccp plugin
bluetoothd
6:21 PM
src/plugin.c:init_plugin() System does not support micp plugin
bluetoothd
6:21 PM
profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
bluetoothd
6:21 PM
src/plugin.c:init_plugin() System does not support vcp plugin
bluetoothd
6:21 PM
src/plugin.c:init_plugin() System does not support mcp plugin
bluetoothd
6:21 PM
src/plugin.c:init_plugin() System does not support bass plugin
bluetoothd
6:21 PM
src/plugin.c:init_plugin() System does not support bap plugin
bluetoothd
6:21 PM
src/plugin.c:init_plugin() System does not support admin plugin
bluetoothd
6:21 PM
Failed to initialize thermal events.
irqbalance
6:21 PM
thermal: failed to receive messages.
irqbalance
6:20 PM
bluetooth.service: ConfigurationDirectory ‘bluetooth’ already exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 555)
(uetoothd)
6:20 PM
platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
kernel
6:20 PM
r8169 0000:03:00.1: can’t disable ASPM; OS doesn’t have ASPM control
kernel
6:20 PM
spi-nor spi0.1: probe with driver spi-nor failed with error -22
kernel
6:20 PM
spi-nor spi0.0: probe with driver spi-nor failed with error -22
kernel
6:20 PM
i801_smbus 0000:00:1f.3: Driver SMBus register access inhibited
kernel
6:20 PM
i801_smbus 0000:00:1f.3: BIOS is accessing SMBus registers
kernel
6:20 PM
lpc_ich: Resource conflict(s) found affecting gpio_ich
kernel
6:20 PM
ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20240827/utaddress-204)
kernel
6:20 PM
ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20240827/utaddress-204)
kernel
6:20 PM
ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20240827/utaddress-204)
kernel
6:20 PM
ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20240827/utaddress-204)
kernel
6:20 PM
ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20240827/utaddress-204)
kernel
6:20 PM
ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20240827/utaddress-204)
kernel
6:20 PM
File /var/log/journal/711faa3b26ef4e2799795c73e0ee36a9/system.journal corrupted or uncleanly shut down, renaming and replacing.
systemd-journald
6:20 PM
/usr/lib/systemd/system/systemd-ask-password-plymouth.service:10: ConditionPathExists= path is not absolute, ignoring: ${localstatedir}/run/plymouth/pid
systemd
6:20 PM
/usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd’s process lifecycle management for the service. Please update the service to use a safer KillMode=, such as ‘mixed’ or ‘control-group’. Support for KillMode=none is deprecated and will eventually be removed.
systemd
6:20 PM
ata5.00: supports DRM functions and may not be fully accessible
kernel
2Occurrences
6:20 PM
plymouth-start.service: Referenced but unset environment variable evaluates to an empty string: localstatedir
(lymouthd)
6:20 PM
/usr/lib/systemd/system/systemd-ask-password-plymouth.service:10: ConditionPathExists= path is not absolute, ignoring: ${localstatedir}/run/plymouth/pid
systemd
6:20 PM
/usr/lib/systemd/system/plymouth-start.service:15: Unit uses KillMode=none. This is unsafe, as it disables systemd’s process lifecycle management for the service. Please update the service to use a safer KillMode=, such as ‘mixed’ or ‘control-group’. Support for KillMode=none is deprecated and will eventually be removed.
systemd
6:20 PM
ENERGY_PERF_BIAS: Set to ‘normal’, was ‘performance’
kernel
6:20 PM
VMSCAPE: SMT on, STIBP is required for full protection. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/vmscape.html for more details.
kernel
6:20 PM
MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
kernel

3

Please do such long pastes on paste.opensuse.org and post the URL here, or use command_here | susepaste

1 Like
4

Better is to use susepaste with -e 131040 otherwise the time of live is limited to 30 minutes.
command_here | susepaste -e 131040

-e 131040 means, the paste is deleted after 3 month, the highest time.

1 Like
5

Yes, newbie posting here!
this does look long and a little unreadable. I’ll give susepaste a try.
R

6

https://paste.opensuse.org/pastes/cbb942306fc0

7

Just to make sure: post zypper se -si cockpit | susepaste -e 131040

8

Update: I now suspect the thinkorswim app to be the culprit for these sudden, random system resets. I came to this conclusion after noticing that is seemed to happen with the app running, with no resets when the app was not running. It’s early; the jury is still out, though.

I did discover a “settings” cog on thinkorswim , and after verifying both RAM settings were defaulted to minimums (Startup: 32 MB; Run: 1536 MB), I initiated the Clear cache and restart command. I ran the app all day today, as well as all the other computer activities I do, and: NO RESETS. I plan to monitor this for a few days, and if no more resets, I will consider this issue SOLVED. i plan to reset the thinkorswim cache once a week from now on.

image
image788×700 69.3 KB

9

Posted the solution in a separate post:

Here

10

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.