Crashes but can't find reason in journalctl

gibar · 2022-12-06 15:57:50

I have installed arch with kde and sometimes my pc will just shutdown and fully reboot.
This is the output of journalctl at the time of the recent crash:

Dec 06 16:17:14 arch-HP plasmashell[750]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Dec 06 16:17:14 arch-HP plasmashell[750]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Dec 06 16:17:14 arch-HP kded5[717]:
Dec 06 16:17:14 arch-HP systemd[604]: Started alacritty.
Dec 06 16:17:16 arch-HP plasmashell[750]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Dec 06 16:17:16 arch-HP plasmashell[750]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Dec 06 16:17:16 arch-HP plasmashell[750]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Dec 06 16:17:18 arch-HP systemd[1]: Stopping User Manager for UID 973...
Dec 06 16:17:18 arch-HP systemd[528]: Activating special unit Exit the Session...
Dec 06 16:17:18 arch-HP systemd[528]: Stopped target Main User Target.
Dec 06 16:17:18 arch-HP systemd[528]: Stopping D-Bus User Message Bus...
Dec 06 16:17:18 arch-HP systemd[528]: Stopped D-Bus User Message Bus.
Dec 06 16:17:18 arch-HP systemd[528]: Removed slice User Core Session Slice.
Dec 06 16:17:18 arch-HP systemd[528]: Stopped target Basic System.

What is weird to me is that I can't find any errors in jounalctl and that I didn't even start alacritty at that time.
Also i have noticed that Started alacritty was in the logs when I crashed previously.
I have a laptop with ryzen 5 5500u with intergrated graphics.
Crashes like this also happened when i was using kubuntu previously.
Does anyone know what could the problem be?

Last edited by gibar (2022-12-06 17:31:33)

cfr · 2022-12-06 17:10:31

Welcome to the forums.

Please edit your post and use [ code ] [ /code ] tags.

Please post a complete journal which includes the issue. (See link in my signature below for pastebin service strategies.)

Are you saying something else started alacritty, but you don't know what?

gibar · 2022-12-06 17:36:49

Yes i don't know what happens there where it says it started alacritty (because i know i didn't open it before it crashed, i had it open already).
This also happened before with Konsole.
There is no errors i can find in journalctl. Just Stopping User Manager for UID 973...

seth · 2022-12-06 21:35:06

pc will just shutdown and fully reboot

Crashes like this also happened when i was using kubuntu previously.

Parallel (hibernating) windows, underpowered, overheated, broken CPU or RAM or

I have a laptop with ryzen 5 5500u with intergrated graphics.

https://wiki.archlinux.org/title/Ryzen#Random_reboots

Though

What is weird to me is that I can't find any errors in jounalctl and that I didn't even start alacritty at that time.
Also i have noticed that Started alacritty was in the logs when I crashed previously.

it's probably not even a crash.
Check your cronjobs/systemd timers; maybe services and session status

systemctl list-timers --all
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
loginctl session-status

And then there's

Dec 06 16:17:14 arch-HP kded5[717]:

- the KDE daemon system:

kcmshell5 kded

Finally:

There is no errors i can find in journalctl.

That's not what cfr asked for - maybe we can spot something that you missed.
If you're looking for error lines, you'll likely not be lucky - this looks like a misconfigured scheduled thing, not like an actual bug.
(Something will likely run some job in a VTE for no actual reason and that job restarts the system)

gibar · 2022-12-07 16:33:32

I tried to add more voltage to my cpu using amdctl.
I checked all systemd timers and I started the service that they were for and I didn't crash.

I got a new crash.
Here are all the logs: https://pastebin.com/hvvpMcsY

seth · 2022-12-07 16:47:54

...skipping...

Isn't helpful. Don't copy and paste out of the pager.
Also the journal segment starts late.

sudo journactl -b -1 | curl -F 'file=@-' 0x0.st # assuming the last boot saw an undesired reboot

Dec 07 17:20:28 arch-HP systemd[511]: Activating special unit Exit the Session...

is not a crash.

gibar · 2022-12-07 16:53:50

If I didn't crash then why did I just unexpectedly reboot?

http://0x0.st/odTM.txt

V1del · 2022-12-07 16:56:43

Is this actually teh output of -b-1 or the one of b-0 ? The latter would be more interesting in case of a crash

Last edited by V1del (2022-12-07 16:59:40)

gibar · 2022-12-07 17:00:52

this is -b -1
http://0x0.st/odTB.txt

Last edited by gibar (2022-12-07 17:22:33)

seth · 2022-12-07 17:15:37

http://0x0.st/odTM.txt

Dec 07 17:51:00 arch-HP sudo[4896]:      gal : TTY=pts/3 ; PWD=/home/gal ; USER=root ; COMMAND=/usr/bin/journalctl -b -0

http://0x0.st/odTB.txt

Dec 07 17:18:50 arch-HP sudo[1846]:      gal : TTY=pts/1 ; PWD=/home/gal ; USER=root ; COMMAND=/usr/bin/journalctl

Both boots are obviously still running.

seth wrote:

sudo journactl -b -1 | curl -F 'file=@-' 0x0.st # assuming the last boot saw an undesired reboot

It's rebooting because something™ explicitly tells it to.

gibar · 2022-12-07 17:38:27

So you are saying that there might be a service that reboots my system?
How would I find that service?

seth · 2022-12-07 21:35:00

I inferred that from the journal snippets you had provided so far, but http://0x0.st/odTB.txt shows that

Dec 07 17:17:46 arch-HP systemd[1]: Stopping User Manager for UID 973...
Dec 07 17:17:46 arch-HP systemd[512]: Activating special unit Exit the Session...
Dec 07 17:17:46 arch-HP systemd[512]: Stopped target Bluetooth.
Dec 07 17:17:46 arch-HP systemd[512]: Stopped target Main User Target.
Dec 07 17:17:46 arch-HP systemd[512]: Stopping D-Bus User Message Bus...
Dec 07 17:17:46 arch-HP systemd[512]: Stopped D-Bus User Message Bus.
Dec 07 17:17:46 arch-HP systemd[512]: Removed slice User Core Session Slice.
Dec 07 17:17:46 arch-HP systemd[512]: Stopped target Basic System.

this is only the SDDM handover and after

Dec 07 17:17:46 arch-HP systemd[1]: Stopped User Manager for UID 973.

it takes more than a minute until

Dec 07 17:18:50 arch-HP sudo[1846]:      gal : TTY=pts/1 ; PWD=/home/gal ; USER=root ; COMMAND=/usr/bin/journalctl

which is the final command in that journal.

a) are you absolutely sure that http://0x0.st/odTB.txt is the journal for a previous boot (because the very specific tail makes it look like it's the journal for the running boot)
b) if that's trueley, by random chance, the last entry and the system rebooted afterwards, it actually crashes and you're back at https://bbs.archlinux.org/viewtopic.php … 3#p2072253

seth wrote:

Parallel (hibernating) windows, underpowered, overheated, broken CPU or RAM …

1. is there a parallel windows installation?
2. did you look at https://wiki.archlinux.org/title/Ryzen#Random_reboots
3. did you monitor the system temperature ahead of such reboot?
4. did you run memtest86+ (a meaningful test lasts hours - at least over night)

Arch Linux

#1 2022-12-06 15:57:50

Crashes but can't find reason in journalctl

#2 2022-12-06 17:10:31

Re: Crashes but can't find reason in journalctl

#3 2022-12-06 17:36:49

Re: Crashes but can't find reason in journalctl

#4 2022-12-06 21:35:06

Re: Crashes but can't find reason in journalctl

#5 2022-12-07 16:33:32

Re: Crashes but can't find reason in journalctl

#6 2022-12-07 16:47:54

Re: Crashes but can't find reason in journalctl

#7 2022-12-07 16:53:50

Re: Crashes but can't find reason in journalctl

#8 2022-12-07 16:56:43

Re: Crashes but can't find reason in journalctl

#9 2022-12-07 17:00:52

Re: Crashes but can't find reason in journalctl

#10 2022-12-07 17:15:37

Re: Crashes but can't find reason in journalctl

#11 2022-12-07 17:38:27

Re: Crashes but can't find reason in journalctl

#12 2022-12-07 21:35:00

Re: Crashes but can't find reason in journalctl

Board footer