Can't shutdown or turn sleep PC

sometimes after pressing Power Off button Fedora is shutting down, monitor screen is turning off but power led is on and fan is still spinning. So I have to long press power button to completely turn off PC. Same behavior when Fedora turns to sleep. However, sometimes power off/sleep is working correct. And that is not matter what I did before turning off PC. It is possible that machine will not power off even if I turn it on and right away turn off.

OS: Fedora 38 x64
Kernel version: 6.3.12-200.fc38.x86_64 (same behavior with 6.2.19)
Device: LENOVO IdeaCentre AIO 3 24IMB05
BIOS version: O4RKT30A

Last lines of journalctl --system are:

Jul 13 13:24:16 fedora systemd[1]: Shutting down.
Jul 13 13:24:16 fedora audit: BPF prog-id=70 op=UNLOAD
...
Jul 13 13:24:16 fedora audit: BPF prog-id=47 op=UNLOAD
Jul 13 13:24:16 fedora systemd-shutdown[1]: Syncing filesystems and block devices.
Jul 13 13:24:16 fedora systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Jul 13 13:24:16 fedora systemd-journald[597]: Received SIGTERM from PID 1 (systemd-shutdow).
Jul 13 13:24:16 fedora systemd-journald[597]: Journal stopped

Shutdown logs are mostly seems fine except lines:

Jul 13 13:24:14 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\DPPP], AE_NOT_FOUND (20221020/psargs-330)
Jul 13 13:24:14 fedora kernel: ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20221020/psparse-529)
Jul 13 13:24:14 fedora kernel: ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20221020/psparse-529)

Any ideas how to solve this problem?

This is a very common problem, but also very vendor/model dependent so your best resource is vendor-specific forums.

Since you didn’t specify, I’ll assume Fedora Workstation and Gnome Session.

You seem to have a recent BIOS update, so you may need to adjust BIOS settings for the actions of the power button (short press and long press).

What do you get for acpi -V -i? Can you shutdown properly using the command line: sudo shudown now --halt. If that doesn’t work in a Gnome session, try logging out and then using the text console (<ctrl-alt F3>). This could help narrow down the problem.

There are command-line kernel options to workaround ACPI/BIOS problems, but I haven’t needed them for years, so not sure what is currently available.

acpi -V -i output:

No support for device type: power_supply
No support for device type: power_supply
Thermal 0: ok, 27.8 degrees C
Thermal 0: trip point 0 switches to mode active at temperature 71.0 degrees C
Thermal 0: trip point 1 switches to mode active at temperature 55.0 degrees C
Thermal 0: trip point 2 switches to mode active at temperature 50.0 degrees C
Thermal 0: trip point 3 switches to mode active at temperature 45.0 degrees C
Thermal 0: trip point 4 switches to mode active at temperature 40.0 degrees C
Cooling 0: Fan 0 of 1
Cooling 1: SEN4 no state information available
Cooling 2: Processor 0 of 3
Cooling 3: Processor 0 of 3
Cooling 4: x86_pkg_temp no state information available
Cooling 5: intel_powerclamp 0 of 100
Cooling 6: Processor 0 of 3
Cooling 7: Processor 0 of 3
Cooling 8: Processor 0 of 3
Cooling 9: Fan 0 of 1
Cooling 10: SEN2 no state information available
Cooling 11: Processor 0 of 3
Cooling 12: Fan 0 of 1
Cooling 13: INT3400 Thermal no state information available
Cooling 14: Processor 0 of 3
Cooling 15: Fan 0 of 1
Cooling 16: B0D4 no state information available
Cooling 17: Processor 0 of 3
Cooling 18: Processor 0 of 3
Cooling 19: TCC Offset 5 of 63
Cooling 20: Processor 0 of 3
Cooling 21: Processor 0 of 3
Cooling 22: Fan 0 of 1
Cooling 23: SEN3 no state information available
Cooling 24: Processor 0 of 3

If I use sudo shutdown now --halt the problem is 100% reproducible. PC doesn’t power down. And no matter if I run this command under Gnome session or text console. Behavior is the same (problematic).

I’ll assume Fedora Workstation and Gnome Session

yep

Here is possible power options in BIOS. Nothing usable…

The CLI command is systemctl power-off or gnome-session-quit --power-off if your in a gnome terminal.

2 Likes

sudo shutdown now --halt is supposed to shutdown the OS but leave the machine powered on. To also cut the power, you need to specify --poweroff instead of --halt.

Why --halt would be useful, I wouldn’t know.

1 Like

Using the command-line sometimes produces error messages that are otherwise hard to find. Halt has to wait for processes to shutdown cleanly, so something like “out of space saving cached data” might be in play.

Halt should be last step before poweroff, so now we can focus on “poweroff”, which gets into vendor dependent BIOS details.

I fixed the problem by downgrading kernel to 5.15

Using 5.15 kernel about two weeks without any problems.
So looks like v6 has new bugs ¯\_(ツ)_/¯. If anyone here want (and able) try to fix it please contact me and I will provide any necessary debug information.

It seems that it may be useful for one to file a bug report against the kernel if there is hardware that absolutely will not boot with a 6.X.X kernel. That is done at bugzilla.redhat.com.

1 Like