On 12.11.21 18:24, Mark Boddington wrote: > On 12/11/2021 16:04, Thorsten Leemhuis wrote: > [...] >> On 11.11.21 00:11, Mark Boddington wrote: >>> And also >>> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c?h=linux-5.15.y&id=f02abeb0779700c308e661a412451b38962b8a0b >>> >>> >>> Maybe if the function is called during resume() without being called >>> during init(), bad things happen??? >> Have you tried to revert any of the patches you suspect to cause this >> and see if things improve? And BTW: did 5.15 (aka 5.15.0) work? Or was >> some process to resolve this made already somewhere else and I just >> missed it? >> >> Ciao, Thorsten (with his Linux kernel regression tracker hat on) >> >> #regzbot poke > > I tried reverting both, but they didn't improve the situation. > > I also had the deadlock happen on 5.15 yesterday so the last stabl> kernel I have used is 5.14.15. I can try the latest 5.14.x if that will > help? You can give it a shot, maybe the problem shows up there now. But I doubt it, as in situations like this the change that's causing the problem likely was introduced in mainline (v5.14..v5.15) and not in stable (v5.15..v5.15.1). I'd suggest you do the following: install and run the latest 5.14.y release, just to be sure (and to get something installed running properly). In parallel check if someone reported such a problem already to the developers of the driver in question. This document explains how to find their mailing list or bug tracker archive to check: https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html It also explains many other aspects around searching for existing reports and reporting Linux kernel issues that might be of help. If you don't find any existing reports, report your problem anew with the regression mailing list in CC (no need to CC me or the stable list). Maybe a developer then has a idea what might cause this and point you in some direction to confirm. But in the end in situations like this you'll likely need to bisect the problem using a git bisection (see reporting issues). So consider to do that before reporting, it's not as hard and time-consuming as many people think. Note: As a Linux kernel regression tracker I'm getting a lot of reports on my table and can only look briefly into them. Due to that I sometimes will get things wrong and thus might give bad advice. I hope that's not the case here. But if you think I got something wrong, don't hesitate to tell me about that. That's in both other interest to prevent you from going down the wrong rabbit hole. Ciao, Thorsten (carrying his Linux kernel regression tracker hat) P.S.: Feel free to ignore the following lines, they are for regzbot, my Linux kernel regression tracking bot: #regzbot introduced v5.14..v5.15
