Control: tag -1 moreinfo On Fri, 13 Oct 2023 00:47:57 -0400 Simon Heath <ice...@dreamquest.io> wrote: > Package: libdrm-amdgpu1 > Version: 2.4.115-1 > > When GDM3 starts, or when I turn it off and log into the console by hand > and then start sway or another WM, often the graphics mode switch will > hang for a few seconds on an unresponsive black screen, then go back to > a text console for an instant and try again. This seems to repeat 0-3 > times until eventually it works successfully. Sometimes it works on the > first try, often on the second try, etc. > > Once Sway or GDM3 and Xorg have actually started, it *seems* perfectly > stable, as far as I've seen so far. > > I also see the following errors in dmesg associated with the > apparent-crash-and-restart: > > [ 26.625039] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, > signaled seq=23, emitted seq=25 > [ 26.625482] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process > information: process pid 0 thread pid 0 > [ 26.625820] amdgpu 0000:c1:00.0: amdgpu: GPU reset begin! > [ 26.810595] [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 > [amdgpu]] *ERROR* MES failed to response msg=3 > [ 26.810761] [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to > unmap legacy queue > ... > Kernel: Linux 6.5.0-1-amd64 (SMP w/12 CPU threads; PREEMPT)
Those messages are actually from the kernel driver. Can you test whether the issue is still present with kernel 6.5.8-1 (Testing) and if so, also try it with 6.5.10-1 from Unstable?
signature.asc
Description: This is a digitally signed message part.
