From owner-freebsd-x11@FreeBSD.ORG Wed Apr 1 15:42:22 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 347051065676 for ; Wed, 1 Apr 2009 15:42:22 +0000 (UTC) (envelope-from njm@njm.me.uk) Received: from smtp003.apm-internet.net (smtp003.apm-internet.net [85.119.248.52]) by mx1.freebsd.org (Postfix) with SMTP id AA8248FC27 for ; Wed, 1 Apr 2009 15:42:21 +0000 (UTC) (envelope-from njm@njm.me.uk) Received: (qmail 4728 invoked from network); 1 Apr 2009 15:42:19 -0000 Received: from unknown (HELO titania.njm.me.uk) (86.129.210.181) by smtp003.apm-internet.net with SMTP; 1 Apr 2009 15:42:19 -0000 Received: from titania.njm.me.uk (localhost [127.0.0.1]) by titania.njm.me.uk (8.14.3/8.14.3) with ESMTP id n31Fg9Mk002752; Wed, 1 Apr 2009 16:42:11 +0100 (BST) (envelope-from njm@njm.me.uk) Received: (from njm@localhost) by titania.njm.me.uk (8.14.3/8.14.3/Submit) id n31Fg8ZU002751; Wed, 1 Apr 2009 16:42:08 +0100 (BST) (envelope-from njm@njm.me.uk) Date: Wed, 1 Apr 2009 16:42:08 +0100 From: "N.J. Mann" To: Robert Noland Message-ID: <20090401154208.GA873@titania.njm.me.uk> References: <20090330201109.9CE521CC09@ptavv.es.net> <1238445388.8491.358.camel@balrog.2hip.net> <20090331151657.GA898@titania.njm.me.uk> <1238517533.8491.371.camel@balrog.2hip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1238517533.8491.371.camel@balrog.2hip.net> X-Operating-System: FreeBSD 7.2-PRERELEASE User-Agent: mutt-NJM (2009-02-20) Cc: freebsd-x11@FreeBSD.org 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: Wed, 01 Apr 2009 15:42:22 -0000 In message <1238517533.8491.371.camel@balrog.2hip.net>, Robert Noland (rnoland@FreeBSD.org) wrote: > On Tue, 2009-03-31 at 16:16 +0100, N.J. Mann wrote: > > 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? > > Yes, I'm not seeing any change here either. So, I don't think that we > have a locking or ordering issue. Are the effects on shutdown a > problem? Yes, but not excessively so. Once I exit X the only thing I am able to do is reboot by pressing CTRL+ALT+DEL. Nothing else appears to work. However, I tend to stay in X all the time on this machine and only exit if there is a problem. So, diagnosing problems is a real PITA at the moment. :-) > I think it may have more to do with the fact that we have > released memory before we have switched display modes on shutdown. I > can reproduce the strange color effects on this i915, but haven't hit a > case where it created any sort of problem. Is there a way of logging the shutdown sequence of X to a file? So far the only error/diagnostic message I get is: Fatal server error: Caught signal 11. Server aborting I really feel like I am not helping much while using up all your valuable time. Cheers, Nick. --