X11 crash on exit

Garrett Cooper yanefbsd at gmail.com
Thu Mar 11 06:45:28 UTC 2010


On Wed, Mar 10, 2010 at 10:40 PM, Tim Kientzle <kientzle at freebsd.org> wrote:
> Trying to get X up and running on my Aspire One netbook
> and having a couple of problems.  Here's the first:
>
> Whenever I exit, the server gets a Signal 11 and crashes,
> corrupting the screen.  So far, I've been able to just
> tap the power button to get a clean reboot (in particular,
> it's just X crashing, not the whole system).
>
> FreeBSD 9.0-CURRENT r201154M: Tue Dec 29 09:27:29 PST 2009 GENERIC  i386
>
> xorg.conf is pretty vanilla except for the two monitors:  1600x1200 external
> on the VGA connector and 1024x600 LVDS display.  This was autoprobed by the
> server:
>
> Section "Device"
>        Identifier  "Card0"
>        Driver      "intel"
>        VendorName  "Intel Corporation"
>        BoardName   "Mobile 945GME Express Integrated Graphics Controller"
>        BusID       "PCI:0:2:0"
>        Option "monitor-LVDS" "LVDSMonitor"
>        Option "monitor-VGA" "VGAMonitor"
> EndSection
>
> A backtrace from the server core:
> #0  0x08092402 in DeliverEventsToWindow ()
> #1  0x0816e37e in ShouldFreeInputMasks ()
> #2  0x081788e9 in SProcXListDeviceProperties ()
> #3  0x0807ecf5 in DisableDevice ()
> #4  0x0807edfa in DisableDevice ()
> #5  0x080cbc5d in xf86PostMotionEvent ()
> #6  0x0807eafb in ActivateDevice ()
> #7  0x0812d168 in LogSetParameter ()
> #8  0x0812d74f in AuditF ()
> #9  0x080bc373 in xf86PrintBacktrace ()
> #10 <signal handler called>
> #11 0x081534d6 in ProcRRDeleteOutputProperty ()
> #12 0x00000030 in ?? ()
> #13 0x081534bb in ProcRRDeleteOutputProperty ()
> #14 0x5a5a5a5a in ?? ()
> #15 0x287367c0 in ?? ()
> #16 0xbfbfecb8 in ?? ()
> #17 0x0806ed9e in ProcSetSelectionOwner ()

Hi Tim!
    X11 appears to crash a lot with SIGSEGV when something library or
application along the way breaks; I've run into this issue multiple
times lately trying to setup my PoC thin client from scratch over the
past couple of days.
    Is this recently happening after an application upgrade, or is
this a new [pristine?] machine?
Thanks!
-Garrett


More information about the freebsd-current mailing list