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

    • ⲇⲅⲇ@lemmy.ml
      3·
      2 days ago

      seems its a nvidia issue, i also have that issue, the gpu locks and i need to reboot while the VM with the nvidia passthrough freezes. i need a full reboot from baremetal machine to stop gpu using all his power stuck, don’t let it be for hours being on or you will kill your hardware

      • potentiallynotfelix@lemmy.fishOP
        1·
        1 day ago

        sudo dmsetup info returns:

        Name:              raven--vg-root
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        1
Event number:      0
Major, minor:      254, 0
Number of targets: 1
UUID: LVM-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Name:              raven--vg-swap_1
State:             ACTIVE
Read Ahead:        256
Tables present:    LIVE
Open count:        2
Event number:      0
Major, minor:      254, 1
Number of targets: 1
UUID: LVM-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
        • ReversalHatchery@beehaw.org
          1·
          13 hours ago

          did you make these yourself? if not, could you cdo an ls -l /dev/mapper? it shows which name corresponds to which dm device

        • truthfultemporarily@feddit.org
          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
            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
              2·
              1 day 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
                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.deEnglish
            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.

    • BCsven@lemmy.ca
      1·
      2 days ago

      Says reboot, are you issuing a reboot or a shutdown poweroff? Entering sleep state 5 shout be power off right?

      • potentiallynotfelix@lemmy.fishOP
        1·
        2 days ago

        I click the reboot button on cockpit, which issues a shutdown --reboot command as root. I agree that sleep state S5 is powered off. From the acpi docs:

        A computer state where the computer consumes a minimal amount of power. No user mode or system mode code is run. This state requires a large latency in order to return to the Working state. The system’s context will not be preserved by the hardware. The system must be restarted to return to the Working state. It is not safe to disassemble the machine in this state.

        This likely means my system is failing to reach that s5/g2 state.

        • BCsven@lemmy.ca
          3·
          2 days ago

          If you ssh login directly and issue same command, not In cockpit interface, does it react the same?