Debian 12 does not properly shutdown nor reboot

[corrierichioggia]

Yes, already did. Also removed quiet. The only things in the linux_cmdline option are acpi=force and reboot=acpi. (how do I display more than 20 messages in this forum at once?)

[nooblinx]

Yes, already did. Also removed quiet. The only things in the linux_cmdline option are acpi=force and reboot=acpi. (how do I display more than 20 messages in this forum at once?)

so that maybe fixed it

[Aki]

Thank you. I did what suggested and the computer appears to be shutting down correctly. So, does this mean the problem is most likely withing the kernel graphics adapter module? If so, is there a way to fix the problem or at least mitigate it?

You may identify the kernel module driving the graphic adapter and then you may search for its parameters or similar issues on the internet.

[corrierichioggia]

Well, unfortunately, I haven't found anything reporting shutdown issues that have similar "symptoms" to mine.
I've tried to do sudo dmesg | grep "amdgpu" and here is the output, even though I don't see anything wrong.

Code: Select all

[    3.953406] [drm] amdgpu kernel modesetting enabled.
[    3.968172] amdgpu: Virtual CRAT table created for CPU
[    3.968693] amdgpu: Topology: Add CPU node
[    3.969337] amdgpu 0000:05:00.0: enabling device (0006 -> 0007)
[    4.091741] amdgpu 0000:05:00.0: amdgpu: Fetched VBIOS from VFCT
[    4.092244] amdgpu: ATOM BIOS: 113-LUCIENNE-016
[    4.092848] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/renoir_asd.bin
[    4.093945] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/renoir_ta.bin
[    4.094620] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/renoir_dmcub.bin
[    4.095531] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/renoir_pfp.bin
[    4.096109] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/renoir_me.bin
[    4.096705] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/renoir_ce.bin
[    4.097234] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/renoir_rlc.bin
[    4.097898] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/renoir_mec.bin
[    4.099229] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/renoir_sdma.bin
[    4.100764] amdgpu 0000:05:00.0: firmware: direct-loading firmware amdgpu/renoir_vcn.bin
[    4.103134] amdgpu 0000:05:00.0: vgaarb: deactivate vga console
[    4.103139] amdgpu 0000:05:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
[    4.103146] amdgpu 0000:05:00.0: amdgpu: MODE2 reset
[    4.103743] amdgpu 0000:05:00.0: amdgpu: VRAM: 2048M 0x000000F400000000 - 0x000000F47FFFFFFF (2048M used)
[    4.103750] amdgpu 0000:05:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
[    4.103756] amdgpu 0000:05:00.0: amdgpu: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
[    4.103970] [drm] amdgpu: 2048M of VRAM memory ready
[    4.103977] [drm] amdgpu: 6902M of GTT memory ready.
[    4.104979] amdgpu 0000:05:00.0: amdgpu: Will use PSP to load VCN firmware
[    4.893504] amdgpu 0000:05:00.0: amdgpu: RAS: optional ras ta ucode is not available
[    4.902397] amdgpu 0000:05:00.0: amdgpu: RAP: optional rap ta ucode is not available
[    4.907219] amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
[    4.907233] amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
[    4.908133] amdgpu 0000:05:00.0: amdgpu: SMU is initialized successfully!
[    5.133938] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[    5.133958] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[    5.134098] amdgpu: Virtual CRAT table created for GPU
[    5.134395] amdgpu: Topology: Add dGPU node [0x164c:0x1002]
[    5.134400] kfd kfd: amdgpu: added device 1002:164c
[    5.134453] amdgpu 0000:05:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 8, active_cu_number 8
[    5.134603] amdgpu 0000:05:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[    5.134609] amdgpu 0000:05:00.0: amdgpu: ring gfx_low uses VM inv eng 1 on hub 0
[    5.134614] amdgpu 0000:05:00.0: amdgpu: ring gfx_high uses VM inv eng 4 on hub 0
[    5.134620] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 5 on hub 0
[    5.134625] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 6 on hub 0
[    5.134630] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 7 on hub 0
[    5.134636] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 8 on hub 0
[    5.134641] amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 9 on hub 0
[    5.134646] amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 10 on hub 0
[    5.134652] amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 11 on hub 0
[    5.134657] amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 12 on hub 0
[    5.134663] amdgpu 0000:05:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 13 on hub 0
[    5.134668] amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
[    5.134674] amdgpu 0000:05:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
[    5.134679] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
[    5.134684] amdgpu 0000:05:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
[    5.134689] amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
[    5.136749] [drm] Initialized amdgpu 3.54.0 20150101 for 0000:05:00.0 on minor 0
[    5.142471] fbcon: amdgpudrmfb (fb0) is primary device
[    5.184211] amdgpu 0000:05:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[    6.363310] snd_hda_intel 0000:05:00.1: bound 0000:05:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])

Journalctl does not contain anything containing the word "amdgpu" since the last boot.

[corrierichioggia]

Well, after a bit of tinkering, I decided to switch back to X11, at least temporarily. Apparently, Wayland isn't ready yet, despite being adopted by the majority of distros. In those days, I noticed that screen sharing does not work on Wayland (even though I installed Pipewire and configured it) and the shutdown problems are (at least for now) fixed with X11. It may be insecure and heavy, but it does the job well.
Thank you all for the help.

[Aki]

Hello,

[.] the shutdown problems are (at least for now) fixed with X11. [..]

Thanks for the update. That is an interesting clue.

Searching for similar problems with Wayland, I came across this bug report:

• https://bugs.kde.org/show_bug.cgi?id=445449

  SUMMARY
  When issuing a shutdown or restart from within a Plasma Wayland session, there is a 1 min. 30 sec. delay while waiting for systemd to stop Simple Desktop Display Manager. This times out and forces a SIGKILL to sddm and associated processes. If I log out of my session and shutdown/reboot directly from sddm, this issue does not occur. Shutdown is instantaneous. I cannot reproduce in the X11 session. It only occurs in Wayland. It also did not occur prior to 5.23.3. A relevant portion of my shutdown log is attached. Not much to see, unfortunately.

This bug report lead to this other bug report:

• Slow shutdown problems in kde plasma with sddm #1476

The latter report, leads to this Debian Bug Tracking System report:

• Debian Bug report logs - #1042851 sddm: Fails to terminate during shutdown/reboot (timeout)

According to it:

Message #10 received at 1042851@bugs.debian.org (full text, mbox, reply):
From: Pierre <pierre@alterna.tv>
To: 1042851@bugs.debian.org
Subject: Still present in 12.4
Date: Mon, 29 Jan 2024 20:47:14 -0500

Hi,

According to sddm development https://github.com/sddm/sddm/issues/1476 issue comment-1152889613, this should be fixed with version 0.20.

Various mitigation operations like switching VT are presented in that thread.

--
Pierre Métras

Are you using sddm as your login manager? If so, you might consider rebuilding and testing sddm version 0.20 (from Debian testing) for Debian Bookwork:

Code: Select all

$ rmadison sddm
sddm       | 0.18.0-1+deb10u1 | oldoldstable       | source, amd64, arm64, armhf, i386
sddm       | 0.18.0-1+deb10u1 | oldoldstable-debug | source
sddm       | 0.19.0-3         | oldstable          | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
sddm       | 0.19.0-5         | stable             | source, amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x
sddm       | 0.20.0-2         | testing            | source, amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x
sddm       | 0.20.0-2         | unstable           | source
sddm       | 0.20.0-2         | unstable-debug     | source
sddm       | 0.20.0-2+b1      | unstable           | amd64, arm64, armel, armhf, i386, mips64el, ppc64el, s390x
sddm       | 0.20.0-2+b2      | unstable           | riscv64

You can do it with the following commands:

Code: Select all

su -l -c "apt install devscripts"
dget -x http://deb.debian.org/debian/pool/main/s/sddm/sddm_0.20.0-2.dsc
cd sddm-0.20.0/
su -l -c "cd $PWD; mk-build-deps -i"
dpkg-buildpackage -b
cd ..

The following packages should be built:

Code: Select all

$ ls sddm*.deb 
sddm-dbgsym_0.20.0-2_amd64.deb             sddm-theme-maldives_0.20.0-2_all.deb
sddm-theme-debian-elarun_0.20.0-2_all.deb  sddm-theme-maui_0.20.0-2_all.deb
sddm-theme-debian-maui_0.20.0-2_all.deb    sddm-theme-maya_0.20.0-2_all.deb
sddm-theme-elarun_0.20.0-2_all.deb         sddm_0.20.0-2_amd64.deb

Then, you can install them (the Debian Stable installed sddm version will be replaced); i.e.:

Code: Select all

su -l -c "cd $PWD; dpkg -i sddm_0.20.0-2_amd64.deb"

Hope this helps.

[corrierichioggia]

Thanks! The issue seems to be gone right now. I'll keep you updated.
Screensharing still does not work. I'll open another issue for that.
Thank you all for your help and time.

[Aki]

Hello,

Thanks! The issue seems to be gone right now. I'll keep you updated.

May you please confirm that you have sorted it?

Thanks :)

[corrierichioggia]

Absolutely. My computer now shuts down as expected.

[Aki]

I'm glad you sorted it out. :) :)

Please, mark the discussion as "solved" manually adding the text tag "[Solved]" at the beginning of the subject of the first message.

Happy Debian !