Thank you!

Flashing an older bios seemed to succeed! I gave it 14 hours or so before attempting a reboot, and if seemed to reboot without stalling. I’ll give it a few more days now and try another, but that seemed to have fixed it.

halt -p did nothing different. still hung on shutdown.

Only happened to me once

sudo systemctl reboot did the same. I’m starting to think this is bios related.

sudo dmsetup info returns:

Name:              raven--vg-root
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        1
Event number:      0
Major, minor:      254, 0
Number of targets: 1
UUID: LVM-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Name:              raven--vg-swap_1
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        2
Event number:      0
Major, minor:      254, 1
Number of targets: 1
UUID: LVM-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Yes, I’ve always made sure to use update-grub and checked cmdline to make sure it has the correct parameters. Regardless of acpi=force or acpi=off, it would still hang.

I click the reboot button on cockpit, which issues a shutdown --reboot command as root. I agree that sleep state S5 is powered off. From the acpi docs:

A computer state where the computer consumes a minimal amount of power. No user mode or system mode code is run. This state requires a large latency in order to return to the Working state. The system’s context will not be preserved by the hardware. The system must be restarted to return to the Working state. It is not safe to disassemble the machine in this state.

This likely means my system is failing to reach that s5/g2 state.

thanks for the suggestion, could you elaborate on what this would do differently from the regular shutdown command that systemctl uses? thanks again

Ok. Cockpit uses the shutdown command to shut down[src], but systemctl poweroff might work. I will also attempt to revert bioses if msi supports it. thank you very much!

yeah journalctl logs show nothing relevant. I have disabled acpi and forced it(acpi=force), but that didn’t fix this. There are a lot of different combinations of acpi settings I could try:

acpi=force noapic
nolapic
noapic
acpi_osi=“Linux”
acpi_osi=“Windows 2006”
acpi=ht
pci=noacpi
acpi=noirq
pnpacpi=off

But I found these from a guy which they didn’t work on so I’m reluctant to try them.

The xserver-xorg-video-nouveau package was not installed, how else would I remove nouveau?

I’ve run arch linux for a year or so before converting it, and no issues with shutdown. what makes you think that’s the cause?

Monitor output after shutting down:

I’ve given it 6 hours or so to shut down, so it’s almost 100% a hang not a slow shutdown