[Bug 231068] x11-servers/xorg-server segmentation fault

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Sep 1 07:11:06 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231068

            Bug ID: 231068
           Summary: x11-servers/xorg-server segmentation fault
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: x11 at FreeBSD.org
          Reporter: mike.d.ft402 at gmail.com
          Assignee: x11 at FreeBSD.org
             Flags: maintainer-feedback?(x11 at FreeBSD.org)

Created attachment 196757
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=196757&action=edit
Backtrace from Xorg.0.log.old

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-intensive
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

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-x11 mailing list