Perform shutdown on reboot

Support and Help
1

Ubuntu Version:
24.04.02 LTS

Relevant System Information:
9900x, MSI x870 Tomahawk, Kingston Fury DDR5 2x32 (qvl certified, running expo)

Problem Description:
Performing a reboot from Linux (not Ubuntu specifically, and surely hope that it is only Linux related since I didn’t use the system with Windows much) the system gets stuck, with postcode 44 (yes, there isn’t a “postcode 44” in the manuals). The system is responsive to pressing reset, but this state is permanent. Until I don’t press power for 7+ seconds.

When I was testing Fedora, I had the same problem.

And was suggested to use
sudo grubby --update-kernel=ALL --args='reboot=pci'

which did the trick.

So I am looking for how to do it with Ubuntu.

Please note: it is my system for work (+fully encrypted drive), so I cannot simply load from a LiveCD if somethings goes wrong.

2

Let’s first test adding a parameter to GRUB. If it works, we can make it permanent later.

Reboot the laptop and at the GRUB menu press e to edit

Use the arrow keys to find the line that starts with linux:
linux /boot/vmlinuz-...

Usually has quiet splash at the end.

Add reboot=pci after quiet splash so it looks like this quiet splash reboot=pci

Don’t change anything else at this stage.

Now press Ctrl+X or F10 to continue booting.

After login and reaching the desktop open a terminal and run systemctl reboot

If the laptop reboots cleanly, not getting stuck on postcode 44, we can make the change permanent.

2 Likes
3

The tricky part here is that this isn’t 100% reproducible. But for what was tested in Fedora, that fix did work.

This is a noobish question (which I am), but editing in this manner does not write anything (meaning that if I manage to screw up, it will not be persisted)?

4

When accessing and editing Grub immediately after a cold start, any changes made are not persistent.

Persistent Grub changes need admin privileges (sudo) after logging in.

2 Likes
5

Did the temporary workaround help resolve this issue?

If yes, we can make the change persistent as mentioned by @tea-for-one

6

Have been busy to actually try it. Will respond once will get my hands on the question.

1 Like
7

Sorry for the long wait. Still trying to figure with my corp admins the question of editing (for the permanent change) grub configurations on the “corporate”(tuned by the company’s admins) with a fully encrypted drive (what are the chances of things going south?).

8

If the fix works when you try it as suggested above during booting, then making it permanent should not have any adverse affects.

If you make a backup copy of the GRUB config file before applying the persistent change, which we always recommend, then the chances of something going wrong are quite low.

9

As silly as it may sound, I completely forgot about the possibility of making a copy :smiley:

10

You know this strange feeling that the moment you decide to sit and fix the issue… the issue doesn’t reproduce (tried rebooting 3 times, one time specifically by systemctl reboot).

Getting the feeling the Kernel wizards heard my plea (there was an update rolling out last time I rebooted).

Will update how things go (I usually update only when there’s an update asking for it).

1 Like
11

This topic was automatically closed after 30 days. New replies are no longer allowed.