Sorry i was trying to reply to this thread: https://marc.info/?l=openbsd-bugs&m=159383256417523&w=2
On Mon, Dec 07, 2020 at 06:08:02PM +0100, Alex Raschi wrote: > Hi, > > I have a similar problem but with a RX 560, i got some logs for a bug > report then i saw this issue open. The screen becomes unresponsive here > too, with xf86-video-amdgpu the issue appears quickly: sometimes running > 2 games for some seconds is enough. > > But with xf86-video-modesetting the system is stabler, with this driver > usually i am able to use X11 for some hours or days (with suspend). > > I don't know if it is related or not but with xf86-video-amdgpu libGL is > unable to use DRI3 and says: > > libGL: screen 0 does not appear to be DRI3 capable > ... > libGL: Using DRI2 for screen 0 > > With xf86-video-modesetting DRI3 works without issues. > Here are some examples of dmesg errors i get when X11 freezes: > > [drm] *ERROR* Waiting for fences timed out![drm] *ERROR* ring sdma1 timeout, > signaled seq=2236, emitted seq=2236 > [drm] *ERROR* Process information: process pid 0 thread pid 0 > > [drm] *ERROR* Waiting for fences timed out! > > [drm] *ERROR* ring gfx timeout, but soft recovered > [drm] *ERROR* ring sdma0 timeout, signaled seq=22318, emitted seq=22318 > [drm] *ERROR* Process information: process pid 0 thread pid 0 > > [drm] *ERROR* ring sdma1 timeout, signaled seq=12928, emitted seq=12928 > [drm] *ERROR* Process information: process pid 0 thread pid 0 > > [drm] *ERROR* ring sdma1 timeout, signaled seq=38, emitted seq=38 > [drm] *ERROR* Process information: process pid 0 thread pid 0 > > Should i open a new issue and send the complete logs? > > Cheers, Alex
