From owner-freebsd-x11@FreeBSD.ORG Tue Mar 31 16:36:10 2009 Return-Path: Delivered-To: freebsd-x11@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 089D41065714; Tue, 31 Mar 2009 16:36:08 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail4.es.net [IPv6:2001:400:6000:6::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6F3CB8FC1B; Tue, 31 Mar 2009 16:36:08 +0000 (UTC) (envelope-from oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id n2VGa66l021537 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 31 Mar 2009 09:36:07 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 855B01CC29; Tue, 31 Mar 2009 09:36:06 -0700 (PDT) To: "N.J. Mann" In-reply-to: Your message of "Tue, 31 Mar 2009 16:16:57 BST." <20090331151657.GA898@titania.njm.me.uk> Date: Tue, 31 Mar 2009 09:36:06 -0700 From: "Kevin Oberman" Message-Id: <20090331163606.855B01CC29@ptavv.es.net> Cc: freebsd-x11@FreeBSD.org, Robert Noland Subject: Re: Xorg 7.4 crashes on exit X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2009 16:36:11 -0000 > Date: Tue, 31 Mar 2009 16:16:57 +0100 > From: "N.J. Mann" > > Hi Robert, > > > In message <1238445388.8491.358.camel@balrog.2hip.net>, > Robert Noland (rnoland@FreeBSD.org) wrote: > > On Mon, 2009-03-30 at 13:11 -0700, Kevin Oberman wrote: > > > > From: Robert Noland > > > > Date: Mon, 30 Mar 2009 14:54:45 -0500 > [snip] > > > > > > > > Is this on CURRENT or STABLE and do you know at least approximately when > > > > you started seeing the issue? > > > > > > > > > > It is on stable and I THINK it started when I updated my system to > > > 7.2-PRERELEASE last week. My previous Stable was on February 7 and it > > > pre-dated the Xorg-1.5.3 server update on the system. > > > > > > I normally update ports daily, but I did delay the Xorg update for a > > > week or two to let dust settle. > > > > There are a lot of changed in that window... I really hope that this > > doesn't fix it, but could you try reverting: > > > > balrog% svn diff -c r189669 > > Index: drm_drv.c > > =================================================================== > > --- drm_drv.c (revision 189668) > > +++ drm_drv.c (revision 189669) > > @@ -131,7 +131,7 @@ > > .d_poll = drm_poll, > > .d_mmap = drm_mmap, > > .d_name = "drm", > > - .d_flags = D_TRACKCLOSE | D_NEEDGIANT > > + .d_flags = D_TRACKCLOSE > > }; > > > > static struct drm_msi_blacklist_entry drm_msi_blacklist[] = { > > I was not sure whether you wanted Kevin, me or both of us to try the > above, so I tried it anyway. :-) It has no visible affect here at all. > I double checked I had patched the right file and even re-compiled > (after doing a rm -rf /usr/obj and a make clean) and re-installed the > resulting kernel. No change. > > Are there any debug messages I can enable to help you out here? For me and my Radeon, the change seems to have "fixed" the problem. I have rebooted several times, including after loading the system with a variety of graphics oriented tasks (Flash, MPEGs, WMV, ...), I have been unable to trigger the problem with the NEEDGIANT. I don't have witness in my kernel and really would have problems with having it there on this system this week as I am on-call. Yuck! -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751