PC crashing/rebooting for no reason

Hello everyone,

I’ve had some sudden crashed/reboots for some months now on Tumbleweed.
I’m using the latest snapshot, latest BIOS and no overclocking.

I’m using Wayland.

I’m at a loss having tried everything I know, re installed CPU on socket, tried with only 1 stick of RAM, swapped RAM slot locations. Checked temps and they are withing reasonable levels, maybe 60-70C for the CPU and 80C at max for the GPU.

AMD R5 5600
AMD 5600XT GPU

I did manage to get the logs from journalctl -b -1 -p 3: just after the latest reboot happened today:

May 28 14:04:44 localhost.localdomain systemd-coredump[24983]: [🡕] Process 1478 (kwin_wayland) of user 1000 dumped core.
                                                               
                                                               Stack trace of thread 1478:
                                                               #0  0x00007fa9d346896d n/a (libpipewire-module-client-node.so + 0x1296d)
                                                               #1  0x00007fa9f57683fc n/a (/usr/lib64/libpipewire-0.3.so.0.370.0 (deleted) + 0x463fc)
                                                               ELF object binary architecture: AMD x86-64
May 28 14:04:44 localhost.localdomain akonadiserver[2066]: org.kde.pim.akonadiserver: Control process died, exiting!
May 28 14:04:45 localhost.localdomain bluetoothd[943]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
May 28 14:04:58 localhost.localdomain konsole[25912]: kf.xmlgui: Shortcut for action  "" "Mostrar las órdenes rápidas" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
May 28 14:04:58 localhost.localdomain konsole[25912]: kf.xmlgui: Shortcut for action  "" "Mostrar el gestor de SSH" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.

Sounds like a bug - you might try switching to using X11 and see if it stabilizes - but you should open a bug in bugzilla.

Run hardware diagnostics, and provide full logs:

sudo journalctl -b -1 -o short-delta

where -1 is the boot that crashed.

Hi, I’m getting a huge text from this command so I pasted it here:

Thanks you!!!

I get Server Nor Found.

FYI we prefer paste.opensuse.org

sudo journalctl -b -1 -o short-delta | susepaste

Hi,

Hope it works now:

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

These are not full logs. It looks like instead the command I suggested, you run the journalctl command, skipped to the end and copied the terminal output. We can see the last 40s though, and it appears that network services are spamming the logs. Nothing else that can justify a crash.

I tried using the full: sudo journalctl -b -1 -o short-delta | susepaste

But I’m getting: Paste failed :frowning:

Run the command FIRST, then add to suSe Paste

No issues here uploading 250KB. You might have hit an upload limit.

Try instead

sudo journalctl -b -1 -o short-delta | xclip -selection clipboard

This will copy to clipboard, then navigate to paste.opensuse.org and create a manual paste.

Back to the topic, you’ll need to troubleshoot more. I suggested running hardware diagnostics to rule out hardware issues. Also try describing what you are doing when it reboots. The immediate cause won’t be in the logs, but could be something started minutes before the reboot. It could be a sudden rise in CPU temperatures, you’ll never be able to notice this.

I believe the log is simply too large, I did:

sudo journalctl -b -1 -o short-delta > log.txt

And the file ended up being 3.9 MiB, cant upload it to Susepaste

Hi,

I’ve done some testing for example:

Letting memtest run for a full 24 hours with no errors at the end of it.
Also on Windows I did a CPU+GPU stress test for more than 1 hour and no problems there.
Swapped RAM sticks between slots.
Swapped CPU’s between 2400g and r5 5600.
PSU is from a reputable brand, Seasonic 80+ Bronze, 620W.

Hi!

Is there any way of sharing this log which is too long for either pastebin or susepaste?

sudo journalctl -b -1 -o short-delta

I think the trailing lines might be enough (for starters):

sudo journalctl -b -1 -o short-delta | tail -n 5000 | susepaste -e 10080

Hi!

That is awesome thank you!

ttps://paste.opensuse.org/42f499b344c7

Things to fix:

  1. Deal with the spamming in the logs
[ 8565.718742 <    2.992301 >] localhost.localdomain NetworkManager[29464]: <info>  [1685301159.4457] policy: set-hostname: set hostname to 'localhost.localdomain' (no hostname found)
[ 8565.719121 <    0.000379 >] localhost.localdomain nscd[969]: 969 monitoring file `/etc/nsswitch.conf` (7)
[ 8565.719286 <    0.000165 >] localhost.localdomain nscd[969]: 969 monitoring directory `/etc` (2)
[ 8565.719327 <    0.000041 >] localhost.localdomain nscd[969]: 969 monitoring file `/etc/resolv.conf` (5)
[ 8565.719345 <    0.000018 >] localhost.localdomain nscd[969]: 969 monitoring directory `/etc` (2)
[ 8565.726880 <    0.007535 >] localhost.localdomain dns-dnsmasq.sh[16324]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit

I don’t use any of these services here, but my guess is that setting a hostname for this machine on /etc/hostname might stop this spamming.

This is possibly unrelated to your issue, just basic hygiene for your system.

  1. There’s snapper running sometime before the end of these logs. It took a minute to run, 12 minutes before the end of logs. I’d temporarily disable at least timeline snapshots and maybe other snapper systemd services.

If you want to do that, match these settings:

$ grep -E 'QGROUP|TIMELINE' /etc/snapper/configs/root
QGROUP=""
TIMELINE_CREATE="no"
TIMELINE_CLEANUP="no"

I understand btrfs could cause the system to stall. Reboot? Hmm, I’m not sure.

  1. Use Xorg as recommended by @hendersj. I’d also try icewm as desktop environment.

Mostly to rule out possible causes.

Hi!

I’ve tried the solutions you posted with no success.
Even changing to Xorg from Wayland didn’t help
This is my last crash log: which seems to contain some extra bit of information:

pc0:/home/gabrielbyrnei # journalctl -b -1 -p 3
May 31 18:23:08 pc0 (udev-worker)[663]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
May 31 18:23:08 pc0 (udev-worker)[656]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
May 31 18:23:09 pc0 (udev-worker)[663]: vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
May 31 18:33:32 pc0 kernel: Freezing remaining freezable tasks failed after 20.011 seconds (0 tasks refusing to freeze, wq_busy=1):
May 31 18:33:52 pc0 kernel: Freezing remaining freezable tasks failed after 20.008 seconds (0 tasks refusing to freeze, wq_busy=1):
May 31 18:33:52 pc0 systemd-sleep[3234]: Failed to put system to sleep. System resumed again: Device or resource busy
May 31 18:33:52 pc0 systemd[1]: Failed to start System Suspend.
Jun 01 08:50:41 pc0 konsole[6424]: kf.xmlgui: Shortcut for action  "" "Mostrar las órdenes rápidas" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s)>
Jun 01 08:50:41 pc0 konsole[6424]: kf.xmlgui: Shortcut for action  "" "Mostrar el gestor de SSH" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) in>
Jun 01 09:20:25 pc0 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=278042, emitted seq=278044
Jun 01 09:20:25 pc0 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gpu-driver pid 10360 thread spring:cs0 pid 10363
Jun 01 09:20:35 pc0 kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:77:crtc-0] hw_done or flip_done timed out

Also this after running same journalctl command after rebooting. Crash happened at 09:24:42:

pc0:/home/gabrielbyrnei # journalctl -b -1 -p 3
Jun 01 09:22:26 pc0 (udev-worker)[644]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
Jun 01 09:22:26 pc0 (udev-worker)[678]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
Jun 01 09:22:26 pc0 (udev-worker)[644]: vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
Jun 01 09:22:48 pc0 akonadiserver[1956]: org.kde.pim.akonadiserver: Control process died, exiting!
Jun 01 09:24:15 pc0 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=24324, emitted seq=24326
Jun 01 09:24:15 pc0 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gpu-driver pid 4689 thread spring:cs0 pid 4692
Jun 01 09:24:18 pc0 kernel: [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
Jun 01 09:24:42 pc0 systemd-coredump[4792]: [🡕] Process 4689 (spring-main) of user 1000 dumped core.
                                            
                                            Stack trace of thread 144:
                                            #0  0x00007ffbb0291184 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x91184)
                                            #1  0x00007ffbb023f00e n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x3f00e)
                                            #2  0x00007ffbb02287fc n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x287fc)
                                            #3  0x0000559bc5775aa0 n/a (/home/gabrielbyrnei/.var/app/info.beyondallreason.bar/data/engine/105.1.1-1767-gaaf2cc3 bar/spring + 0x31>
                                            #4  0x00007ffbb0241a4e n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x41a4e)
                                            #5  0x00007ffbacf50675 n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/dri/libgallium_dri.so + 0x950675)
                                            #6  0x00007ffbac6bf41d n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/dri/libgallium_dri.so + 0xbf41d)
                                            #7  0x00007ffbac710c2c n/a (/usr/lib/x86_64-linux-gnu/GL/default/lib/dri/libgallium_dri.so + 0x110c2c)
                                            #8  0x00007ffbb028f1da n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8f1da)
                                            #9  0x00007ffbb0317f44 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x117f44)
                                            ELF object binary architecture: AMD x86-64
Jun 01 09:24:42 pc0 akonadiserver[3646]: org.kde.pim.akonadiserver: Control process died, exiting!
Jun 01 09:24:59 pc0 konsole[6090]: kf.xmlgui: Shortcut for action  "" "Mostrar las órdenes rápidas" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s)>
Jun 01 09:24:59 pc0 konsole[6090]: kf.xmlgui: Shortcut for action  "" "Mostrar el gestor de SSH" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) in>
Jun 01 10:02:17 pc0 konsole[13693]: kf.xmlgui: Shortcut for action  "" "Mostrar las órdenes rápidas" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s>
Jun 01 10:02:17 pc0 konsole[13693]: kf.xmlgui: Shortcut for action  "" "Mostrar el gestor de SSH" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) i>
Jun 01 10:08:55 pc0 konsole[14495]: kf.xmlgui: Shortcut for action  "" "Mostrar las órdenes rápidas" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s>
Jun 01 10:08:55 pc0 konsole[14495]: kf.xmlgui: Shortcut for action  "" "Mostrar el gestor de SSH" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) i>

Hi!

Unfortunately crashes/freezes keep happening, but now the system goes into a black screen for some seconds (mouse and keyboard unresponsive) and then after some seconds reboots itselfs.
On the boot up I can see for a brief moment maybe 6 lines of some kinds of errors.

This is from the last time the system crashed/froze:

pc0:/home/gabrielbyrnei # journalctl -b -1 -p 3
Jun 03 22:29:09 pc0 bluetoothd[949]: src/plugin.c:plugin_init() Failed to init vcp plugin
Jun 03 22:29:09 pc0 bluetoothd[949]: src/plugin.c:plugin_init() Failed to init mcp plugin
Jun 03 22:29:09 pc0 bluetoothd[949]: src/plugin.c:plugin_init() Failed to init bap plugin
Jun 03 22:29:09 pc0 (udev-worker)[677]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
Jun 03 22:29:09 pc0 (udev-worker)[673]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
Jun 03 22:29:09 pc0 (udev-worker)[677]: vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
Jun 03 22:29:21 pc0 bluetoothd[949]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Jun 03 22:39:34 pc0 kernel: Freezing remaining freezable tasks failed after 20.007 seconds (0 tasks refusing to freeze, wq_busy=1):
Jun 03 22:39:54 pc0 kernel: Freezing remaining freezable tasks failed after 20.004 seconds (0 tasks refusing to freeze, wq_busy=1):
Jun 03 22:39:54 pc0 systemd-sleep[3217]: Failed to put system to sleep. System resumed again: Device or resource busy
Jun 03 22:39:54 pc0 systemd[1]: Failed to start System Suspend.
Jun 04 12:13:43 pc0 konsole[8068]: kf.xmlgui: Shortcut for action  "" "Mostrar las órdenes rápidas" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Jun 04 12:13:43 pc0 konsole[8068]: kf.xmlgui: Shortcut for action  "" "Mostrar el gestor de SSH" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead.
Jun 04 16:24:33 pc0 bluetoothd[949]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Jun 05 09:07:52 pc0 bluetoothd[949]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down

To see if it is hardware or software - boot off a USB drive with a known good Tumbleweed.

I use the Geeko Linux (it is OpenSUSE with some of their options) the Rolling is Tumbleweed, the Stable is Leap 15.4.

Get it from here https://geckolinux.github.io/

If it still crashes - you have a hardware problem. If it works - you can install it from the USB drive, reboot, and then do a zypper dup to get all the patches since it was created.

It is the simple way to see if the hardware or software is to blame for the reboots.