Re: X11 Freeze and Crash on Lenovo Thinkpad T14 AMD GEN1
Dave Voutila writes: > It seems a user with a T14s with similar hardware reported issues with > hibernate. [1] Does your system properly suspend/resume and > hibernate/resume? That was me. :-) I haven't experienced that issue in any case other than trying to resume from hibernation (in any case it wasn't a segmentation fault). I've just updated my machine to the latest snapshot (it's been a few weeks), so will report back if I see it. > I'm sadly no eXpert on X or drm...but if you're getting a segfault, it > might be helpful to get the core dump and see what the stack was via > gdb. > > -Dave > > [1] https://marc.info/?l=openbsd-bugs=161654860102192=2
Re: X11 Freeze and Crash on Lenovo Thinkpad T14 AMD GEN1
> It seems a user with a T14s with similar hardware reported issues with > hibernate. [1] Does your system properly suspend/resume and > hibernate/resume? Yes, without any issue. I was thinking at first it should have been due to suspend/resume, but it's not the case. issue [1] seems not to be the same. > I'm sadly no eXpert on X or drm...but if you're getting a segfault, it > might be helpful to get the core dump and see what the stack was via > gdb. Yes... Totally forgot to do that! Like you, I am not an expert in X and drm. ;)
Re: X11 Freeze and Crash on Lenovo Thinkpad T14 AMD GEN1
Hi, Just got the same issue, this time, my connection was still present. Here the message from dmesg after going into single-user mode by killing init process. [drm] *ERROR* ring sdma0 timeout, signaled seq=30079, emitted seq=30079 [drm] *ERROR* Process information: process pid 0 thread pid 0 Xorg process was a zombie at this time. This behavior seems to be generated when the screen is going blank, in my case, when xautolock is executed or screensaver is set. My first crash was on 2nd April, just after using the last current version at this time.
Re: X11 Freeze and Crash on Lenovo Thinkpad T14 AMD GEN1
niamkik writes: > Hi, > > Just got the same issue, this time, my connection was still present. Here the > message from dmesg after going into single-user mode by killing init process. > > [drm] *ERROR* ring sdma0 timeout, signaled seq=30079, emitted seq=30079 > [drm] *ERROR* Process information: process pid 0 thread pid 0 > > Xorg process was a zombie at this time. This behavior seems to be generated > when the screen is going blank, in my case, when xautolock is executed or > screensaver is set. My first crash was on 2nd April, just after using the > last current version at this time. It seems a user with a T14s with similar hardware reported issues with hibernate. [1] Does your system properly suspend/resume and hibernate/resume? I'm sadly no eXpert on X or drm...but if you're getting a segfault, it might be helpful to get the core dump and see what the stack was via gdb. -Dave [1] https://marc.info/?l=openbsd-bugs=161654860102192=2
