Shutdown -h now causes reboot

I’ve just finished the mammoth “dnf update” to upgrade Rocky 8.4 to 8.5 on my Lenovo ThinkCentre mini-PC and now when I “shutdown -h now” the machine restarts rather than staying off. Bit weird! Any suggestions?

Seems strange, I just tested on my KVM virtual machine and running the same command shuts down my system without any problems.

[root@rocky ~]# shutdown --help
shutdown [OPTIONS...] [TIME] [WALL...]

Shut down the system.

     --help      Show this help
  -H --halt      Halt the machine
  -P --poweroff  Power-off the machine
  -r --reboot    Reboot the machine
  -h             Equivalent to --poweroff, overridden by --halt
  -k             Don't halt/power-off/reboot, just send warnings
     --no-wall   Don't send wall message before halt/power-off/reboot
  -c             Cancel a pending shutdown

can you try maybe one of the other parameters? Like -H instead of -h, or -P and does that work any better?

I normally just do:

shutdown now

without any additional parameters and that also shuts down properly for me.

how does

# systemctl poweroff

behave?

Same problem - machine shuts down then powers on again. I guess it’s something to do with ACPI, but I haven’t changed the settings since it was working with 8.4.

dmesg say this - relevant?

[ 20.891574] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20210105/utaddress-213)
[ 20.891580] Resource conflict; ACPI support missing from driver?
[ 20.891583] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210105/utaddress-213)
[ 20.891586] Resource conflict; ACPI support missing from driver?
[ 20.891587] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRE) (20210105/utaddress-213)
[ 20.891591] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210105/utaddress-213)
[ 20.891594] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210105/utaddress-213)
[ 20.891597] Resource conflict; ACPI support missing from driver?
[ 20.891598] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRE) (20210105/utaddress-213)
[ 20.891601] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210105/utaddress-213)
[ 20.891604] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210105/utaddress-213)
[ 20.891607] Resource conflict; ACPI support missing from driver?
[ 20.891608] lpc_ich: Resource conflict(s) found affecting gpio_ich

I don’t know, maybe not. See this similar looking bugzilla [1]

Is it rebooting instead of poweroff or is it powering on immediate after powering off?
The latter could mean it is not because of OS, it could also be some firmware thing. Some firmware has related settings like “Power on after Power Loss” or similar. Did firmware settings change recently or was there even a firmware upgrade (maybe automatically per LVFS [2] ?)

[1] 1370254 – ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion
[2] Lenovo ThinkCentre joins the LVFS – Technical Blog of Richard Hughes?