[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

Jerome C (me at jeromec.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |me at jeromec.com

--- Comment #4 from Jerome C (me at jeromec.com) ---
I too have a Ryzen 5 3500U and random resumes where the screen updates are very
slow ( 1 frame change every 1-2 minutes ) which looks like it's crashed and in
the kernel logs I see a bunch of "flip_done timed out" and
"amdgpu_dm_atomic_commit_tail" errors

This never happened for me between 5.4.6 - 5.9.14. I noticed this since 5.10.4
and did never suspended on 5.10.0 - 5.10.3, so my guess it's an issue sometime
in 5.10.0 - 5.10.3

Do you have kernel parameter set "init_on_free=1" or in your kernel config
"CONFIG_INIT_ON_FREE_DEFAULT_ON=y", if so try changing/setting the kernel
parameter "init_on_free=0", so far ( for me and still testing ) it's resumed
every time

I think it's an issue with amdgpu and kernel paramater "init_on_free=1" or
kernel config "CONFIG_INIT_ON_FREE_DEFAULT_ON=y" which zero's memory on
free/deallocation.

kernel paramter "init_on_alloc=1" or kernel config
"CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y" works fine for me

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

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