[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 #34 from Jerome C (me at jeromec.com) ---
Using 5.13.0 now and the issue is still here

(In reply to kolAflash from comment #32)
> Created attachment 296901 [details]
> dmesg via SSH, running amd-drm-next-5.14-2021-05-12 without
> ip_block_mask=0x0ff and with Xorg
> 
> (In reply to Jerome C from comment #31)
> > [...]
> > hiya, you may not know this but use in "amdgpu.ip_block_mask=0x0ff" and not
> > "ip_block_mask=0x0ff"
> > [...]
> > I can see in your kernel logs that VCN is still enabled
> 
> Ooops you're right.
> I know someone wrote that before. But it seems I somehow missed it while
> editing my Grub parameters.
> 
> I'll give it another try!
> 
> 
> ----
> 
> 
> In the meanwhile I performed test number 2.
> 
> > 2. amd-drm-next-5.14-2021-05-12* without ip_block_mask=0x0ff, with Xorg
> [...]
> 
> This time the crash was very different!
> 
> After some minutes (about 3) the graphical screen actually turned back on.
> I'm pretty sure that didn't happen with the other kernels I tested.
> (never tested amd-drm-next-5.14-2021-05-12 before)
> 
> Nevertheless everything graphical is lagging extremely. If I move the mouse
> or do anything else it takes more than 10 seconds until something happens on
> the screen.
> 
> On the other hand SSH access is smoothly possible. And I was able to save
> the dmesg output. (see attachment)
> Unlocking the screen via SSH (loginctl) or starting graphical programs
> (DISPLAY=:0 xterm) works, but is extremely slow too. (> 10 seconds waiting)

You have any updates since you corrected the kernel parameter?

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

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