[SOLVED]System hangs on reboot/shutdown

pwish · 2024-06-24 16:39:48

EDIT: IF YOU'RE EXPERIENCING THE SAME PROBLEM THAT I DO, I FIXED IT BY REINSTALLING EVERYTHING USING "pacman -S --asexplicit $(pacman -Qneq)" AND "pacman -S --asdeps $(pacman -Qndq)". THERE MAY BE OTHER PROBLEMS FOR YOU SO IF THAT DOESN'T FIX IT, BE SURE TO CHECK THE THREAD FULLY.

My system sometimes hangs and stays on a black screen and doesn't cut the power on shutdown and also doesn't reboot since the power never cuts.
This is the journalctl output from the last boot after the reboot command:

Jun 24 19:18:47 cherry systemd-logind[829]: The system will reboot now!
Jun 24 19:18:47 cherry systemd-logind[829]: System is rebooting.
Jun 24 19:18:47 cherry sddm-helper[1029]: Signal received: SIGTERM
Jun 24 19:18:47 cherry systemd[1]: Stopping Session 2 of User pwish...
Jun 24 19:18:47 cherry plasmashell[1178]: kf.plasma.quick: Couldn't create KWindowShadow for NotificationPopup_QMLTYPE>
Jun 24 19:18:47 cherry plasmashell[1178]: kf.plasma.quick: Couldn't create KWindowShadow for NotificationPopup_QMLTYPE>
Jun 24 19:18:47 cherry plasmashell[1178]: kf.plasma.quick: Couldn't create KWindowShadow for NotificationPopup_QMLTYPE>
Jun 24 19:18:47 cherry plasmashell[1178]: The X11 connection broke (error 1). Did the X11 server die?
Jun 24 19:18:47 cherry kglobalacceld[1077]: The X11 connection broke (error 1). Did the X11 server die?
Jun 24 19:18:47 cherry kglobalacceld[1077]: The X11 connection broke: I/O error (code 1)

Last edited by pwish (2024-07-01 13:56:06)

pwish · 2024-06-26 20:30:03

The problem still persists and I have waited for some time before cutting the power by force in order to get something useful for the journal. This is the output of journalctl "-b -1 -r --no-pager | curl -F 'file=@-' 0x0.st" :

https://0x0.st/Xmmh.txt

If you need something more feel free to tell me I can provide it.

seth · 2024-06-26 22:39:20

Because it is like top-posting.
Why not?
Please never use "-r" with journalctl.

https://bbs.archlinux.org/viewtopic.php?id=293400
https://aur.archlinux.org/packages/nvidia-535xx-dkms

Edit: though it looks just like Xorg is stuck.

Jun 26 22:56:21 cherry kernel: sysrq: This sysrq operation is disabled.

https://wiki.archlinux.org/title/Keyboa … el_(SysRq) - yo've to explictly enable this, but frenetic usage of ctrl+alt+del ()you've to hit this often and fast) might reboot.

KDE crashes out of the session.
Can you shutdown/reboot when first logging out and then shutting down from SDDM, not directly ot of the session?

Last edited by seth (2024-06-26 22:45:56)

pwish · 2024-06-27 01:44:26

I also thought the issue might be kde related. When I tried using xfce4 the issue seemed to be gone but the problem happens randomly and I only tried 6 reboots back to back so I'm not really sure.

I didn't know I had to enable the shortcut I'll do it next time I boot.

I will try shutting down from sddm after closing the current session and I'll notify the result. I always use terminal to shutdown/reboot using "shutdown now" and "reboot" but KDE's own button doesn't make a difference it's still sometimes triggered.

I didn't understand if I should try changing the nvidia drivers like the thread you suggested or you've changed your mind after your edit so clarification could be great.

Thanks for giving the time to help and I'm sorry for using "-r" I'll be more carefull next time. Like I said I'll notify after I can access my pc again.

pwish · 2024-06-27 05:00:05

When I tried logging out of my session I got the black screen again.

The output of journalctl -b -1 --no-pager | curl -F 'file=@-' 0x0.st : "http://0x0.st/XmSK.txt"

I will try to get into sddm and try shutting down from there again and I will edit after I try.

edit: okay so I was able to log out 2 times and each time I was able to shutdown succesfully. But after that I wasn't able to log out ever again. It just gave me the black screen but this time I had my cursor on the screen and occasionally some apps working so I swapped to tty3 and managed to get the journal after the black screen. Here is the output of "journalctl -b --no-pager | curl -F 'file=@-' 0x0.st" after I was able to acces tty3: "http://0x0.st/XmSQ.txt"

edit2: I was able to log out and get back to sddm a couple more times and every time I did I was able to reboot/shutdown. But then I tried to shutdown before logging in and it gave me the black screen again. Here is the input of "journalctl -b -1 --no-pager | curl -F 'file=@-' 0x0.st" after it gave me the black screen before logging in: "http://0x0.st/XmSg.txt"

Last edited by pwish (2024-06-27 06:12:40)

seth · 2024-06-27 05:53:21

The nvida module showed up and the symptoms superficially matched - but it's only printing because the Xorg process locks up and the backtrace doesn't match on the details.

If the context doesn't matter (ie. shutting down from SDDM doesn't reliably work) see https://wiki.archlinux.org/title/Ryzen# … k_freezing

pwish · 2024-06-27 06:35:06

I think shutting down from SDDM now works after adding "echo rcu_nocbs=0-$(($(nproc)-1))" as a kernel parameter but it's still inconsistent like doing it in terminal. It can still sometimes give black screen.

Last edited by pwish (2024-06-27 06:35:49)

seth · 2024-06-27 13:06:49

Try things independently (ie. how does rebooting from SDDM behave without any kernel parameters, how does rebooting from KDE behave with mitigating kernel parameters) and certainly try to restrict the cstates.

pwish · 2024-06-27 15:16:15

I have added the kernel parameter but I'm not sure if it restricted it successfully or should i use disable-c6-systemd as wiki suggested so I'll look into it if there is a command for it that shows. I'll edit the results after.

seth · 2024-06-27 17:14:41

The wiki wrote:

Adding the kernel parameter processor.max_cstate=5 helped in some cases but other users reported that the option is not applied and the c6 state is still entered.

The only way this makes sense if some userspace tool changes the limit at runtime (TLP or so might plausibly do that)

pwish · 2024-06-27 18:47:46

I tried all of them both seperately and together but "idle=nomwait" since I own a desktop but it felt like the first two didn't made any difference to the boot and "pci=nomsi" made me unable to boot so I prepared a usb and got rid of it. It looks like none of it made a real difference... Do you think since it looks like Plasma causes it, getting rid of configs and reinstalling could fix the crashes?

Last edited by pwish (2024-06-27 18:52:32)

seth · 2024-06-27 20:28:42

You could test the behavior w/ a fresh user, but plasma/sddm has a record itr.
However, https://wiki.archlinux.org/title/Ryzen# … nd_suspend
Tried "processor.max_cstate=1"?

pwish · 2024-06-27 20:55:26

I tried "processor.max_cstate=5" i'll give processor.max_cstate=1 a try and notify. Fresh user idea seems solid I'll edit the results.

edit: processor.max_cstate=1 didn't work and reboot/shutdown is still inconsistent. will try with a new user.

edit2: new user didn't fix anything.

Last edited by pwish (2024-06-27 21:23:32)

pwish · 2024-06-29 16:03:45

Nothing I did made any difference whatsoever. If there is someone else who could help I'd really appreciate it. Thanks.

seth · 2024-06-29 16:13:38

I think shutting down from SDDM now works

Is this still the case?

pwish · 2024-06-29 17:59:03

Not really like I said in the first sentence, the inconsistency is still an issue. It's not that shutdown/reboot hangs every time and it's frustrating. Both using terminal and sddm could cause this issue. It's just that using sddm was usually way more broken. It's fixed in a sense that it's now as broken as using the terminal. It's still not 100% fixed though. But I remembered something, in the past steam used to give me problems when I tried playing unity games. I fixed it by reinstalling. Even though it's usually configs that's causing majority of the problems, I figured maybe some packages updated weirdly and that may cause the problem. So i reinstalled everything using "pacman -S --asexplicit $(pacman -Qneq)" and "pacman -S --asdeps $(pacman -Qndq)". I will notify the results. If you end up finding something in the logs that I couldn't. I'd be more than happy to listen and figure this out.

pwish · 2024-07-01 13:48:26

So far it looks like my issue is fixed after reinstalling everything. Maybe it really was a faulty update or something. I have no idea what was causing this issue but I think it's safe to say my issue is fixed now. It's probably better to open a new thread if the issue continues. Thanks seth for your help! The only issue I currently have is that I can't log out but that probably has something to do with drkonqi instead looking at this thread. Thanks again! I'll mark the thread as [SOLVED] now.

Last edited by pwish (2024-07-01 13:52:03)

Arch Linux

#1 2024-06-24 16:39:48

[SOLVED]System hangs on reboot/shutdown

#2 2024-06-26 20:30:03

Re: [SOLVED]System hangs on reboot/shutdown

#3 2024-06-26 22:39:20

Re: [SOLVED]System hangs on reboot/shutdown

#4 2024-06-27 01:44:26

Re: [SOLVED]System hangs on reboot/shutdown

#5 2024-06-27 05:00:05

Re: [SOLVED]System hangs on reboot/shutdown

#6 2024-06-27 05:53:21

Re: [SOLVED]System hangs on reboot/shutdown

#7 2024-06-27 06:35:06

Re: [SOLVED]System hangs on reboot/shutdown

#8 2024-06-27 13:06:49

Re: [SOLVED]System hangs on reboot/shutdown

#9 2024-06-27 15:16:15

Re: [SOLVED]System hangs on reboot/shutdown

#10 2024-06-27 17:14:41

Re: [SOLVED]System hangs on reboot/shutdown

#11 2024-06-27 18:47:46

Re: [SOLVED]System hangs on reboot/shutdown

#12 2024-06-27 20:28:42

Re: [SOLVED]System hangs on reboot/shutdown

#13 2024-06-27 20:55:26

Re: [SOLVED]System hangs on reboot/shutdown

#14 2024-06-29 16:03:45

Re: [SOLVED]System hangs on reboot/shutdown

#15 2024-06-29 16:13:38

Re: [SOLVED]System hangs on reboot/shutdown

#16 2024-06-29 17:59:03

Re: [SOLVED]System hangs on reboot/shutdown

#17 2024-07-01 13:48:26

Re: [SOLVED]System hangs on reboot/shutdown

Board footer