Closed dr3mro closed 2 years ago
I have found a work around which works even if PICOM with GLX backend is running
I have to switch VT to tty2 for example and login then zzz
then it will resume to this tty and then I switch back with ctrl+alt+f9 then no crash
may be it tries to switch to the tty too early before its ready!
drm-fbsd13-kmod (which tracks 5.4) is known to have suspend/resume problems. Try graphics/drm-510-kmod which compiles on 13.1
I can confirm that fixes the issue for me
Describe the bug Whenever I do zzz on my Lenovo Thinkpad x250 using freeBSD 13.1RC2 the Xserver crash then I have to either do zzz again or do kldunload i915kms && kldload i915kms then It will work fine until I do zzz again this issue happens on lid close and was happening on RC1 when using picom GLX backend but now on RC2 it happens even if no applications are running and picom not running at all or running with xrender backend which was working on RC1
FreeBSD version FreeBSD x250 13.1-RC2 FreeBSD 13.1-RC2 releng/13.1-n250104-c2e15a08fd9 GENERIC amd64
PCI Info
DRM KMOD version drm-fbsd13-kmod 5.4.144.g20220223 drm-kmod g20190710_1
To Reproduce on 13.1Rc1 enabling picom or compton with glx backend on 13.1Rc2 independent of picom backend even if uninstalled just enter sleep then wake up then x server crash
xorg.0.log Xorg.0.log