Re: what to do on magically fixed case? (was Fwd: Kernel 6.6-rc1 fails to reboot or shutdown Ryzen 5825U)

[Thorsten Leemhuis]

On 28.09.23 13:14, Bagas Sanjaya wrote:
> [addressing to Thorsten]
> 
> On Thu, Sep 14, 2023 at 02:03:00PM +0700, Bagas Sanjaya wrote:
>>
>> 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. 
>
> [...]
>
>> 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)
> 
> On Bugzilla, the reporter said that this regression was fixed in linux-next
> tree without specifying the exact commit that do it. He also did not bisect
> as I asked, nor even culprit commit range. Should I mark this regression as 
> fixed?

You ideally might want to ask the report to maybe test -rc4 on Monday,
as the fix by then should have made it to mainline if it was in next a
fwe days ago. If rc4 doesn't fix the problem it might motivate the
reporter to check which patch helps in next, so we could ensure that
it's backported.

But if the reporter isn't motivated there is nothing much we can do
(expect asking the maintainer what commit might need to be mainlined to
fix this; but for a complex subsystem like this I guess that's not worth
the trouble, as I guess the maintainer is unlikely to know).

Hence let's mark this as resolved in regzbot and better spend
everybody's time elsewhere:

#regzbot resolved: fixed in -next according to reporter (and hopefully
in mainline, too)

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.