Skip to content

Shutdown hangs on Linux Mint 22.3 with kernel 7.0.0-34; works with 6.8.0-146 #3850

Description

@7capcom-star

Distribution

Mint 22.3

Package version

Cinnamon 6.6.9

Frequency

Always

Bug description

Summary

On this system, Linux Mint 22.3 does not consistently power off completely when running kernel 7.0.0-34-generic. The displays turn off and the shutdown sequence reaches systemd's final poweroff stage, but the computer remains powered on. In one reported occurrence, it was left in this state for 12 minutes without powering off.

After installing and booting kernel 6.8.0-146-generic, shutdown from Cinnamon's normal power menu worked as expected in the user's tests.

This suggests a possible kernel-version regression or interaction with the graphics/power-management path. The cause has not been isolated.

System

OS: Linux Mint 22.3, 64-bit

Desktop: Cinnamon 6.6.9 on X11

CPU: AMD Ryzen Threadripper 1950X

GPU: AMD Radeon RX 580

Motherboard: ASUS PRIME X399-A, Rev 1.xx

BIOS: American Megatrends 1602, dated 2024-01-30

Displays: Three ASUS VA24E monitors, 1920×1080

Current kernel after a subsequent boot: 7.0.0-34-generic

Kernel that worked in the comparison test: 6.8.0-146-generic

ASUS's support page lists BIOS 1602 as the latest BIOS for this board: https://www.asus.com/latin/supportonly/prime%20x399-a/helpdesk_bios/

Steps and results

  • Boot Linux Mint 22.3 with 7.0.0-34-generic.
  • Choose Shut Down from Cinnamon's normal power menu.
  • The monitors turn off and the system begins its shutdown sequence, but the tower stays powered on. One occurrence persisted for 12 minutes.
  • Two desktop launchers were also created and tested:
  • APAGAR PC.desktop: /usr/bin/systemctl poweroff
  • REINICIAR PC.desktop: /usr/bin/systemctl reboot
  • The poweroff launcher produced the same incomplete shutdown while running kernel 7.0. The launchers were later removed because they did not resolve the issue.
  • Install and boot 6.8.0-146-generic. uname -r confirmed that kernel was active. The user reports that shutdown from Cinnamon's normal power menu then worked normally in their tests.
  • After a later power-on, GRUB booted its default kernel, 7.0.0-34-generic. This was a subsequent boot selection; it does not mean the successful 6.8 shutdown test ran on 7.0.

Relevant shutdown log from a 7.0 attempt

The journal showed that VMware stopped and mounted filesystems were unmounted. Systemd then reached:

Reached target shutdown.target - System Shutdown.
Reached target final.target - Late Shutdown Services.
Finished systemd-poweroff.service - System Power Off.
Reached target poweroff.target - System Power Off.
systemd-shutdown[1]: Syncing filesystems and block devices.
systemd-shutdown[1]: Sending SIGTERM to remaining processes...
systemd-journald: Journal stopped

The provided journal excerpt did not show an explicit kernel error after journald stopped, so the exact final-stage failure is not yet identified.

Other observations

Earlier logs included repeated ACPI messages:

[Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)

There was also an asus_wmi LPS0 handler registration message and an AMDGPU DisplayPort infoframe message. Their relationship to this shutdown symptom is unknown.

The journal excerpt from the later transition between kernels showed 7.0.0-34 ending at reboot.target; that was a reboot, not the failed poweroff attempt.

Expected behavior

The system powers off completely after selecting Shut Down.

Actual behavior

With 7.0.0-34-generic, the displays turn off and systemd reaches its final poweroff stage, but the computer can remain powered on indefinitely. With 6.8.0-146-generic, the user reports normal shutdown in their tests.

Steps to reproduce

.

Expected behavior

.

Additional information

.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions