Arch Linux

ConfusedBinaryTree

Member

Registered: 2024-11-09

Posts: 4

System stuck on shutdown but not on reboot

Hello everybody!

My system is not able to shutdown properly, while it can reboot without any issues.

I tried debugging this problem with the help of other posts on the internet but could not get any step further.

- My system is up to date and I am using the vanilla Linux kernel available from the package repository
- I also tried to use the LTS kernel, but it did not help with the issue
- I have logs (with systemd debug and kernel messages) where I just removed my name available here: https://pastebin.com/5yzij4FA
- I obtained the logs with

journalctl -k -b -1

- When I shutdown my system I see at the end something like Shutdown Target Reached. I will make a picture of it and add it

The white area is I assume because my main screen is 4K while the other is 2K.
- The system is at the state shown in the picture not responsive. ALT+CTRL+DEL (many times) does not do anything, switching to another TTY is also not possible (ALT+CTRL+F<number>)
- I have a nvidia GPU (1070) but I am using the nouveau drivers
- I am using LUKS + LVM, On the internet I read that LUKS + LVM might be the issue. I installed it according to the install instructions in the Wiki. The boot process works perfectly fine.
- The filesystem on the volumes are all ext4, as the wiki suggested, I left 256MB free after the last partition
- I am using the new AMD CPU Ryzen 7 9700X

Can you help me fix the problem?
What other information can I provide?

Thank you in advance

Cheers!

EDITED:
- Add command on how I obtained logs
- Add picture showing how the shutdown looks in the end.

Last edited by ConfusedBinaryTree (2024-11-09 16:17:40)

ConfusedBinaryTree

Member

Registered: 2024-11-09

Posts: 4

Re: System stuck on shutdown but not on reboot

Out of curiosity, I tried out the archinstall script. For that I choose btrfs + LUKS. On a freshly installed system I have the same issue as with my main system.

I want to try to get more logs. Potentially from the kernel on this. Since systemd reports, that it shutdown, I assume this is not related to systemd anymore.

cryptearth

Member

Registered: 2024-02-03

Posts: 1,020

Re: System stuck on shutdown but not on reboot

have you checked for bios updates? could be an issue the current installed firmware has issues with this brand new cpu

ConfusedBinaryTree

Member

Registered: 2024-11-09

Posts: 4

Re: System stuck on shutdown but not on reboot

Hey, I did update the BIOS today right after trying out archinstall. Sadly, it did not help with the issue.

ConfusedBinaryTree

Member

Registered: 2024-11-09

Posts: 4

Re: System stuck on shutdown but not on reboot

I continued digging a little further.

I saw this post here https://bbs.archlinux.org/viewtopic.php?pid=2208648 with a link to https://freedesktop.org/wiki/Software/s … eventually which looks very valuable to me.

I debug flags and and now I am able to see more detailed logs in the shutdown log but also in journalctl. I am not getting smarter from that to be honest. In fact, so much log messages that I can't upload them to pastebin in one go.

The last messages in fact are from systemd-shutdown

Nov 20 00:28:26.450964 ConfusedBinaryTreeLinuxDesktop systemd-shutdown[1]: Setting '/proc/sys/kernel/printk' to '5'
Nov 20 00:28:26.451095 ConfusedBinaryTreeLinuxDesktop systemd-shutdown[1]: Successfully forked off '(sd-sync)' as PID 1495.
Nov 20 00:28:26.451128 ConfusedBinaryTreeLinuxDesktop systemd-shutdown[1]: Syncing filesystems and block devices.

After that nothing happens still. Like, not even an hour later.

---

What people in the debian forum recommend is to install the proprietary nvidia drivers: https://forums.debian.net/viewtopic.php?t=158398

I could try that out.

---

I also see that I never mentioned my partitions, maybe somebody sees a mistake right away:

nvme0n1       259:6    0 953.9G  0 disk  
├─nvme0n1p1   259:7    0   512M  0 part  /boot
└─nvme0n1p2   259:8    0 953.4G  0 part  
  └─luks      254:0    0 953.4G  0 crypt 
    ├─vg-root 254:1    0    64G  0 lvm   /
    └─vg-home 254:2    0 889.4G  0 lvm   /home