Xorg 7.4 crashes on exit

[N.J. Mann]

In message <1238517533.8491.371.camel at balrog.2hip.net>,
	Robert Noland (rnoland at FreeBSD.org) wrote:
> On Tue, 2009-03-31 at 16:16 +0100, N.J. Mann wrote:
> > In message <1238445388.8491.358.camel at balrog.2hip.net>,
> > 	Robert Noland (rnoland at FreeBSD.org) wrote:
> > > On Mon, 2009-03-30 at 13:11 -0700, Kevin Oberman wrote:
> > > > > From: Robert Noland <rnoland at FreeBSD.org>
> > > > > 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.
--