I’ve had two server oses here: alma linux and debian(currently). On both of them, they will hang when I shut them down from cockpit, and they hang at the end of the shutdown.

Also, it takes an hour to a day to have this issue start. if it’s restarted two times in a row quickly, it works perfectly fine for some reason.

What I’ve tried:

  • setting “acpi=off” and “acpi=force” kernel parameters in grub
  • removing my nvidia gpu(i was using nouveau drivers)
  • changing distros

nothing worked. here are some things that both distros had in common with eachother:

  • systemd
  • cockpit
  • libvirt & qemu
  • docker

does anyone have advice? nothing i’ve seen online has worked. thank you for suggestions

      • truthfultemporarily@feddit.org
        link
        fedilink
        arrow-up
        2
        ·
        2 days ago

        Because you tried two different OSes and the point where it hangs is the point where the OS sends an APM/ACPI command to reboot / power off. This is the last thing the OS does. So if that’s not happening something is wrong with the hardware, BIOS, or BIOS settings.

        You could try the syslog (journalctl), but logging is probably already off at that point.

        • potentiallynotfelix@lemmy.fishOP
          link
          fedilink
          arrow-up
          2
          ·
          2 days ago

          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.

          • ReversalHatchery@beehaw.org
            cake
            link
            fedilink
            arrow-up
            2
            ·
            2 days ago

            did you check it /proc/cmdline if the params were taken into account? perhaps you edited the config but didn’t update the initramfs

            • potentiallynotfelix@lemmy.fishOP
              link
              fedilink
              arrow-up
              2
              ·
              1 day ago

              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.

        • hendrik@palaver.p3x.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 days ago

          And I guess if you’re in front of the computer, you could just press the reset button or unplug it at that point (after it sucessfully synchronized the disks). no need to let it sit, there is no harm or data to be lost at that point.