Xorg 7.4 crashes on exit

[Kevin Oberman]

> From: Robert Noland <rnoland at FreeBSD.org>
> Date: Mon, 30 Mar 2009 12:15:34 -0500
> Sender: owner-freebsd-x11 at freebsd.org
> 
> On Mon, 2009-03-30 at 17:19 +0100, N.J. Mann wrote:
> > In message <1238427305.8491.333.camel at balrog.2hip.net>,
> > 	Robert Noland (rnoland at FreeBSD.org) wrote:
> > > On Mon, 2009-03-30 at 16:19 +0100, N.J. Mann wrote:
> > > > In message <1238424768.8491.331.camel at balrog.2hip.net>,
> > > > 	Robert Noland (rnoland at FreeBSD.org) wrote:
> > > > > On Mon, 2009-03-30 at 11:53 +0100, N.J. Mann wrote:
> > [snip]
> > > > > > Okay I tried out your recent changes this morning.
> > > > > > 
> > > > > > First I did a svn update to r190540 to bring my sources up to date and
> > > > > > then I built a new 7-Stable world and kernel and installed them.  Sadly,
> > > > > > I still got the video mode corruption on exiting X or switching from X
> > > > > > to a VT.  I then merged all the changes from head/sys/dev/drm to
> > > > > > stable/7/sys/dev/drm and tried again.  Unfortunately, I got the same
> > > > > > results.  (Xorg.log and dmesg.boot available if required.)  The changes
> > > > > > I merged were: 190020, 190021, 190022, 190023, 190123, 190124, 190125,
> > > > > > 190163, 190164, 190166, 190170, 190282, 190399, 190400, 19401 and
> > > > > > 190433.  Some of these were probably not relevant, but I did everything
> > > > > > to make it easier for me.  (I am very much still testing the water with
> > > > > > svn and this was the first time I tried doing a merge!)
> > > > > > 
> > > > > > Any ideas where to go from here?
> > > > > 
> > > > > Which chip do you have?  I have a patch now that fixes vblank issues, at
> > > > > least I can't break it.  This corruption issue on shutdown still exists,
> > > > > but I've never had a problem vt switching.  I'm told that something is
> > > > > still wrong with interrupts on g45 though.
> > > > 
> > > > Is this the information you require?
> > > > 
> > > > % grep '^\(vga\|agp\|drm\)' r19054M.dmesg.boot
> > > > vgapci0: <VGA-compatible display> port 0xf140-0xf147 mem 0xff900000-0xff97ffff,0xd0000000-0xdfffffff,0xff700000-0xff7fffff irq 16 at device 2.0 on pci0
> > > > agp0: <Intel G33 SVGA controller> on vgapci0
> > > > vgapci0: Reserved 0x10000000 bytes for rid 0x18 type 3 at 0xd0000000
> > > > vgapci0: Reserved 0x80000 bytes for rid 0x10 type 3 at 0xff900000
> > > > vgapci0: Reserved 0x100000 bytes for rid 0x1c type 3 at 0xff700000
> > > > agp0: detected 7164k stolen memory
> > > > agp0: aperture size is 256M
> > > > drm0: <Intel G33> on vgapci0
> > > > vgapci0: Reserved 0x80000 bytes for rid 0x10 type 3 at 0xff900000
> > > > vgapci0: child drm0 requested pci_enable_busmaster
> > > > vga: vga0 already exists; skipping it
> > > > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
> > > > 
> > > > The MB is a Intel DG31GL, which incorporates an Intel GMA 3100 graphics
> > > > adapter.
> > > 
> > > Ok, you can try
> > > http://people.freebsd.org/~rnoland/drm-intel-fix-033009.patch
> > 
> > Okay, I am doing a buildkernel now.  However, I will not be able to test
> > this until later tonight (here) because I now have to go and prepare the
> > evening meal. :-)
> > 
> > Thanks for all your help.
> 
> I think maybe I just found the source of some of the issues... let me do
> a little more testing and I'll get back to you soon.

This may be of no value, but it might be a useful data point.

I have been seeing what sounds like the same thing on my laptop. When I
attempt to exit X, the screen undergoes several changes, ending up with
seemingly randomly colored squares that I'd estimate at 8x8 pixels over
the left third of my screen and vertical stripes which may be duplicates
of one line of my background on the remainder.

The display just sits there and I have no way to see any console
messages, but the console keyboard is alive and well and I can enter
commands (such as 'shutdown -r now') and they work, assuming no typos.

If I attempt to shutdown from Gnome, I get the same result except the
shutdown completes in about the normal time and the system reboots.

One very significant difference from other reports is that I am not
running Intel graphics. I have an ATI(AMD) Radeon X300.

Seems odd (though not unbelievable) that two drivers would exhibit the
same mis-behavior, at least in terms the the symptoms.
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman at es.net			Phone: +1 510 486-8634
Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751