Shut down not possible (restarts instead)

Community Support
,
1

I’m using Fedora on my relatively new Framework 13 with AMD Ryzen AI 370HX

I think it was yesterday that I first noticed an issue that the laptop would not shut down properly, the screen had gone black already but the power button white LED was still on. I thought of a temporary glitch, and after a while (I think 30 seconds or so) I long-pressed (10sec) the power button, and it turned off.

Today, I started up Linux, then did the upgrade from F42 to F43. After the upgrade, I noticed that bluetooth wasn’t working, to which I found this forum thread. However, when I tried to apply the solution proposed there (i.e., shut down), I noticed, that now the laptop would still not shut down properly - I have now tried several times, every time I select shut down and let it proceed, it turns off the screen, but the power button stays glowing, and after like 20 seconds or so, it does a reboot…

in journalctl, I cannot see anything out of the ordinary.

Nov 23 00:24:20 fedora systemd\[1\]: Reached target poweroff.target - System Power Off. 
Nov 23 00:24:20 fedora systemd\[1\]: **Shutting down.** 
Nov 23 00:24:20 fedora kernel: **audit: type=1131 audit(1763853860.604:228): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'** 
Nov 23 00:24:20 fedora audit: BPF prog-id=60 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=59 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=73 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=72 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=55 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=54 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=45 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=47 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=46 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=67 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=66 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=52 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=51 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=48 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=50 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=49 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=69 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=68 op=UNLOAD 
Nov 23 00:24:20 fedora audit: BPF prog-id=41 op=UNLOAD 
Nov 23 00:24:20 fedora systemd-shutdown\[1\]: Syncing filesystems and block devices. 
Nov 23 00:24:20 fedora systemd-shutdown\[1\]: Sending SIGTERM to remaining processes... 
Nov 23 00:24:20 fedora systemd-journald\[772\]: Received SIGTERM from PID 1 (systemd-shutdow). 
Nov 23 00:24:20 fedora systemd-journald\[772\]: Journal stopped 
**-- Boot 221516c911754cafa5f7f9af8f5d877f --** 
Nov 23 00:25:09 fedora kernel: **Linux version 6.17.8-300.fc43.x86_64 (mockbuild@ab7cf9a033ee48b98a175e8677ed2d80) (gcc (GCC) 15.2.1 20251022 (Red Hat 15.2.1-3), GNU ld version 2.45-1.fc43) #1 SMP PREEMPT_DYNAMIC Fri Nov 14 01:47:12 UTC 2025** 
Nov 23 00:25:09 fedora kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.17.8-300.fc43.x86_64 root=UUID=b19f1ca4-153c-4166-94f1-5cc582483255 ro rootflags=subvol=root rhgb quiet 
Nov 23 00:25:09 fedora kernel: x86/split lock detection: #DB: warning on user-space bus_locks

Anyone has encountered this, or tipps what I can try next?

2

Ok after two more tries, one of which had the laptop stuck again (for > 10 minutes), where I terminated again by long-pressing shutdown button, it seems to have somehow resolved itself.
Now, bluetooth works again, and on shut down (one attempt so far), it actually did shut down…

3

Seems the behavior is linked to connecting the laptop to my screen (an LG 32UL950-W) via this USB-C 3.2 20GBit/s cable (right back port, but is the same at the left back one).
The shut down seems to get stuck only when its connected to that screen.

Apart from that, the connection works fine (there is an image on the screen, and USB devices connected to the screen are available on the PC.

4

I have currently a similar issue with my Framework Desktop.
I run Omarchy 3.2.3 and it’s not shutting down anymore, and restarting again.

Thanks to your suggestion I tried unplugging my monitor (thunderbolt/usb-c) and it solves the issue. Thank you!

I reported my issue in the omarchy bugtracker Shutdown does not shutdown, system restarts after a while · Issue #3918 · basecamp/omarchy · GitHub

5

Since it happens on both an Arch-based distribution and on Fedora, it looks like this is not distribution specific thing

6

I suspect it might be an AMD issue, as I have the same problem here on a fw desktop/nixos if a wd19tb dock is plugged in, and if i unplug it shuts down properly.