Debian 12 does not properly shutdown nor reboot

[corrierichioggia]

I have installed a few days ago Debian 12 (Bookworm) in a dualboot setup together with Windows 10. However, i have an (inconsistent, usually presents when I use the OS for more than 5/10 minutes) issue: when I shutdown my pc (a Lenovo ThinkBook 15 ACL) I get greeted with the log displayed at the startup (the one with all the starting services etc.) and another line at the end, saying "The system will shutdown now!" (or reboot, depends on what I chose), and a blinking cursor, that does not allow me however to input any keys. The system at that point is pretty much useless, and the only option for me is to force shutdown with the power button. Is there a way to restore full functionality of the shutdown and reboot?

[Aki]

Hello,

Your computer looks like quite new. You may try installing a newer kernel from Debian Backports.

Hope this helps.

--
[1] https://backports.debian.org/

[corrierichioggia]

Thank you for your help. I tried to add the backports sources and installing the linux-image-6.6.13+bpo-amd64 package (kernel 6.6.13), however the problem wasn't fixed.

[manyroads]

You can try to get a better shutdown by logging out your dekstop to the lightdm screen (step 1); from the lightdm screen (step 2) execute shutdown or reboot (your preference).

I have experienced a similar problem to yours on multiple Debian and arch distros. The above procedure has made the process faster and less annoying for me.

[corrierichioggia]

Well, first of all, thanks for the tip. For now, it looks like that by adding the line

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="acpi=force reboot=acpi"

to

Code: Select all

/etc/default/grub

the problem has been fixed, at least temporarily, despite the fact that there were no ACPI errors when executing

Code: Select all

sudo dmesg | grep acpi -i

. I'll post another reply if I see that the problem did not get solved. I'll keep you updated.

[Aki]

Well, first of all, thanks for the tip. For now, it looks like that by adding the line

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="acpi=force reboot=acpi"

to

Code: Select all

/etc/default/grub

the problem has been fixed, at least temporarily, despite the fact that there were no ACPI errors when executing

Code: Select all

sudo dmesg | grep acpi -i

. I'll post another reply if I see that the problem did not get solved. I'll keep you updated.

Which kernel version are you using with the parameters above ?

[corrierichioggia]

I'm using the back ports version (6.6.13)

[Aki]

I'm using the back ports version (6.6.13)

Thanks. Does the same solution work with kernel 6.1.18 (default kernel for Debian Stable 12.5) ?

[corrierichioggia]

Hi. Sorry for being absent those days, I've had no internet access. Every now and then, the issue pops up again. I'll try to manually disconnect and then shutdown every time manually.
No, I haven't tried the stable kernel. I'll try to use it a little bit to evaluate the problem.
Last of all, I have a question: does my installed kernel version get updated "automatically" when I do apt update/upgrade like the stable one does?

[Aki]

Hello,

[..] Every now and then, the issue pops up again. I'll try to manually disconnect and then shutdown every time manually.

I am sorry the solution found is not effective in all cases. However, did the use of the parameters acpi=force reboot=acpi improve the situation ?

does my installed kernel version get updated "automatically" when I do apt update/upgrade like the stable one does?

It will be upgraded when it is updated in the backports repository. Package upgrade for Debian Backports "[..] is done on a best effort basis by the people who track the package, usually the ones who originally did upload the package into backports. When security related bugs are fixed in Debian unstable the backporter is permitted to upload the package from directly there instead of having to wait until the fix hits testing. You can see the open issues for bullseye-backports in the security tracker (though there may be false positives too, the version compare isn't perfect yet)" [1]

--
[1] https://backports.debian.org/FAQ/

[corrierichioggia]

Yes, the situation has improved. I'll have to keep shutting down by disconnecting first, if I want to eliminate the situation.
Do you think the fact that I'm running a dual boot with windows influences something?

[Aki]

Hello,

Yes, the situation has improved. I'll have to keep shutting down by disconnecting first, if I want to eliminate the situation.

If disconnecting from the network (wired ? wireless ?) solves the problem, the problem is with the network interface (probably with its power management).

Do you think the fact that I'm running a dual boot with windows influences something?

It has been reported that devices (i.e. network devices) in Debian GNU/Linux may be in an inconsistent state if Windows is not completely shut down (in dual boot configurations).

Therefore, the "fast boot" feature in Windows must be disabled if you are dual-booting with other operating systems (i.e.: Debian GNU/Linux).

I suppose you already know this, but it might be helpful for others to remember that you don't have to boot Debian GNU/Linux if Windows is suspended or hibernated.

[corrierichioggia]

Sorry, by disconnecting I meant "logging out" (I'm used to saying disconnect because windows says it like that in my language).
The fast-boot is already disabled. If not, the PC wouldn't even prompt the grub screen and directly dump me into windows.

[Aki]

Hello,

by disconnecting I meant "logging out" (I'm used to saying disconnect because windows says it like that in my language).

That's interesting. A problem with the graphics adapter kernel module might cause this.

[corrierichioggia]

Is there a way to check?

[Aki]

Is there a way to check?

You can boot into multi-user.target (instead of graphical.target) passing the following parameter to the kernel using the grub boot loader:

Code: Select all

systemd.unit=multi-user.target

You can then log into the text console and shut down the computer as root with the following command

Code: Select all

shutdown -h now

Then check that the computer shuts down correctly.

[corrierichioggia]

Pardon my ignorance, but could you please explain what the commands you told me do?

[Aki]

See here:

• Linux: Set systemd target (init/runlevel level) at grub command line

[corrierichioggia]

Thank you. I did what suggested and the computer appears to be shutting down correctly. So, does this mean the problem is most likely withing the kernel graphics adapter module? If so, is there a way to fix the problem or at least mitigate it?

[nooblinx]

did you removed splash? https://forums.linuxmint.com/viewtopic.php?t=368407