From owner-freebsd-current@FreeBSD.ORG Thu Mar 11 06:45:27 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2353106566C; Thu, 11 Mar 2010 06:45:27 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 682858FC0C; Thu, 11 Mar 2010 06:45:27 +0000 (UTC) Received: by pvg3 with SMTP id 3so2979935pvg.13 for ; Wed, 10 Mar 2010 22:45:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=DKK8WM6roiRfJXKIew9Vdm3UhGxrNZPECAvR1Vs44qc=; b=IRkHHdzSEF2kYGf9mA/eDxQymeWyXnyANfiAU86B6dysFzdDMVqjSF8itU9PYCTbzN hVWU7m8cu/qDBpT5Qdahyux2vbrMSf25r2BAuUMsRBxD/XebVgyyFyyLzYSzbs8Q5WvX OpLTdZw/CE8bmMVz4QFRJpy2fn7ARriBGMWRw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=o4CU1ixFvyaHo2v6lfC1mVLgZnxQQUfU+yMLA4d+tXnAHYnZIBvLFWQ2MwnYCiixTT A4UB6S+K46piALCoQ73jqt2E+YuGX1yWV+f0YySDzOltDXgDVw+xD9VjRmt5Z73kCc8v r/HhliQ/fimA3sxvh9JFUmLgc1ZdEk8onf1ko= MIME-Version: 1.0 Received: by 10.142.152.15 with SMTP id z15mr1157137wfd.341.1268289926889; Wed, 10 Mar 2010 22:45:26 -0800 (PST) In-Reply-To: <4B989064.5030105@freebsd.org> References: <4B989064.5030105@freebsd.org> Date: Wed, 10 Mar 2010 22:45:26 -0800 Message-ID: <7d6fde3d1003102245l41ab8287r81680aa40281d802@mail.gmail.com> From: Garrett Cooper To: Tim Kientzle Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-current@freebsd.org" Subject: Re: X11 crash on exit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Mar 2010 06:45:28 -0000 On Wed, Mar 10, 2010 at 10:40 PM, Tim Kientzle wrote= : > Trying to get X up and running on my Aspire One netbook > and having a couple of problems. =A0Here's the first: > > Whenever I exit, the server gets a Signal 11 and crashes, > corrupting the screen. =A0So 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 =A0i38= 6 > > xorg.conf is pretty vanilla except for the two monitors: =A01600x1200 ext= ernal > on the VGA connector and 1024x600 LVDS display. =A0This was autoprobed by= the > server: > > Section "Device" > =A0 =A0 =A0 =A0Identifier =A0"Card0" > =A0 =A0 =A0 =A0Driver =A0 =A0 =A0"intel" > =A0 =A0 =A0 =A0VendorName =A0"Intel Corporation" > =A0 =A0 =A0 =A0BoardName =A0 "Mobile 945GME Express Integrated Graphics C= ontroller" > =A0 =A0 =A0 =A0BusID =A0 =A0 =A0 "PCI:0:2:0" > =A0 =A0 =A0 =A0Option "monitor-LVDS" "LVDSMonitor" > =A0 =A0 =A0 =A0Option "monitor-VGA" "VGAMonitor" > EndSection > > A backtrace from the server core: > #0 =A00x08092402 in DeliverEventsToWindow () > #1 =A00x0816e37e in ShouldFreeInputMasks () > #2 =A00x081788e9 in SProcXListDeviceProperties () > #3 =A00x0807ecf5 in DisableDevice () > #4 =A00x0807edfa in DisableDevice () > #5 =A00x080cbc5d in xf86PostMotionEvent () > #6 =A00x0807eafb in ActivateDevice () > #7 =A00x0812d168 in LogSetParameter () > #8 =A00x0812d74f in AuditF () > #9 =A00x080bc373 in xf86PrintBacktrace () > #10 > #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