Date: Sat, 01 Sep 2018 07:11:03 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: maintainer-feedback requested: [Bug 231068] x11-servers/xorg-server segmentation fault Message-ID: <bug-231068-7141-vVhrKAo3KU@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-231068-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-231068-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Bugzilla Automation <bugzilla@FreeBSD.org> has asked freebsd-x11 mailing li= st <x11@FreeBSD.org> for maintainer-feedback: Bug 231068: x11-servers/xorg-server segmentation fault https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231068 --- Description --- X11 crashes every 10 hours of use or so, it is very hard to pinpoint what triggers it, but I think I get the crash when closing some graphics-intensi= ve program like FlightGear, Blender or Qutebrowser. During the runtime of Xorg= the system has been suspended several times, maybe that affects it somehow... The stack trace is always the same, except for the "3: ? (?+0xe12) [0x7fffffffffa5]" being a bit different for different versions of drm-next-= kmod -- see attachment. The only major changes to my setup before I started getting this were: -switching to drm-next-kmod, because I'd been getting regular "GPU hung" messages with the default module; -removing x11-drivers/xf86-video-intel, because modeset driver is now usable unlike the last time I had tried. My current setup: FreeBSD 11.2-RELEASE-p2, generic kernel with drm-next-kmod-4.11.g20180822 xorg-server-1.18.4_9,1 using modeset driver Lenovo B570e Intel(R) Core(TM) i7-2820QM CPU @ 2.30GHz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-231068-7141-vVhrKAo3KU>