[Bug 211277] sometimes crash at s2ram-wake (Ryzen 3500U): amdgpu, drm, commit_tail, amdgpu_dm_atomic_commit_tail

[bugzilla-daemon at bugzilla.kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=211277

--- Comment #14 from kolAflash (kolAflash at kolahilft.de) ---
(In reply to Jerome C from comment #13)

I don't get how you got to your results.
There's no straight path from 5.10.4 to 5.11-rc5, as they are on different
branches (5.10.y and master).

Nevertheless, your result may be reasonable from the point of the git history.
I'm not sure about the commit ID a10aad137, but it has an completly identical
twin commit c6d2b0fbb (also removing AMD_PG_SUPPORT_VCN_DPG from that
expression).
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c6d2b0fbb893d5c7dda405aa0e7bcbecf1c75f98
And c6d2b0fbb has been applied between v5.10-rc2 and v5.10-rc3 (a10aad137 is
only in master).

So if c6d2b0fbb (a.k.a a10aad137) is responsible, this explains why I started
recognizing the problem when Debian-Testing went from Linux-5.9 to Linux-5.10.

I'm now running a 5.10.21 kernel where I reverted c6d2b0fbb. And I'll try using
this kernel for at least one week and also run some iterative tests with it. 



Regarding reproduction in general:

I really wonder what triggers this bug. I didn't went so far to test with more
than 50 tests (sleep-wake iterations). Especially I didn't tried more than 50 
because the bug definitely appeared more often if it happened under "natural"
(non-testing) circumstances.

Some test series I did which are hard to make sense of statistically:
I tried 20 tests and nothing happened. A few minutes later I decided to try 50
more tests and it directly failed on the first one. So I had to reboot, tried
again 50 tests and nothing happened. Afterwards I put my notebook into s2ram
and when I woke it the next day it immediately crashed.



By the way the two times it crashed recently (see above) happened with a kernel
I compiled from clean kernel.org sources. Also I never experienced the bug with
a clean 5.8.18 compiled from kernel.org running with the same system for about
a week. So I'm quite convinced it's nothing Debian specific.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.