Hi, I notice a regression report on Bugzilla [1]. Quoting from it:
> The Kernel stalls at boot very long with a drm-amdgpu message, but fails to > restart or shutdown with secure boot enabled or not. Magic key works to exit. > Nothing wrong in the Kernel 6.5 cycle. Later, the reporter (Cc'ed) described the regression: > Let me be clearer, it does not shutdown at all: magic key for shut down has > no effect (o or b). The keyboard is dead. Plus, $ shutdown -r now hangs too. > Restart works when using Alt+PrtSc+b. Same when booting stalls for long. > > We started bisecting with 20230903 daily kernel, the bug was there. 6.6-rc1 > has been removed. Take good note that next boot log after shutdown may or may > not be the same log. Plus, booting requires now and then magic key to > restart, because the Kernel hangs. In this case, we must click enter twice + > Esc to boot in desktop. > > It booted ok after a cold shutdown with enter twice and ESC ounce + > backspace. > ... > In all cases, tpm and secure boot are enabled. If secure boot is disabled, > when we shut down, magic key works to restart. He then pasted journalctl excerpt at the point where the hang occured: > This where it stalls for restart. Shut down hangs at the Lenovo image: > > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: SE 1, SH per SE 1, CU > per SH 8, active_cu_number 8 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv > eng 0 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx_low uses VM > inv eng 1 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring gfx_high uses VM > inv eng 4 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses > VM inv eng 5 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses > VM inv eng 6 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses > VM inv eng 7 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses > VM inv eng 8 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses > VM inv eng 9 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses > VM inv eng 10 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses > VM inv eng 11 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses > VM inv eng 12 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring kiq_0.2.1.0 uses > VM inv eng 13 on hub 0 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM > inv eng 0 on hub 8 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM > inv eng 1 on hub 8 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM > inv eng 4 on hub 8 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM > inv eng 5 on hub 8 > Sep 13 21:43:08 mm kernel: amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM > inv eng 6 on hub 8 > Sep 13 21:43:08 mm kernel: [drm] Initialized amdgpu 3.54.0 20150101 for > 0000:04:00.0 on minor 0 > Sep 13 21:43:08 mm kernel: fbcon: amdgpudrmfb (fb0) is primary device > Sep 13 21:43:08 mm kernel: [drm] DSC precompute is not needed. See Bugzilla for the full thread and links to complete journalctl log. Anyway, I'm adding this regression to regzbot: #regzbot introduced: v6.5..v6.6 https://bugzilla.kernel.org/show_bug.cgi?id=217905 #regzbot title: shutdown/reboot hang on Ryzen 5825U (stuck on amdgpu initialization) Thanks. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217905 -- An old man doll... just what I always wanted! - Clara
