Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Mar 2009 15:36:28 -0500
From:      Robert Noland <rnoland@FreeBSD.org>
To:        Kevin Oberman <oberman@es.net>
Cc:        freebsd-x11@FreeBSD.org
Subject:   Re: Xorg 7.4 crashes on exit
Message-ID:  <1238445388.8491.358.camel@balrog.2hip.net>
In-Reply-To: <20090330201109.9CE521CC09@ptavv.es.net>
References:  <20090330201109.9CE521CC09@ptavv.es.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--=-jSf3i60RvaGh8LIp2x5z
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mon, 2009-03-30 at 13:11 -0700, Kevin Oberman wrote:
> > From: Robert Noland <rnoland@FreeBSD.org>
> > Date: Mon, 30 Mar 2009 14:54:45 -0500
> >=20
> > On Mon, 2009-03-30 at 12:38 -0700, Kevin Oberman wrote:
> > > > From: Robert Noland <rnoland@FreeBSD.org>
> > > > Date: Mon, 30 Mar 2009 12:15:34 -0500
> > > > Sender: owner-freebsd-x11@freebsd.org
> > > >=20
> > > > On Mon, 2009-03-30 at 17:19 +0100, N.J. Mann wrote:
> > > > > In message <1238427305.8491.333.camel@balrog.2hip.net>,
> > > > > 	Robert Noland (rnoland@FreeBSD.org) wrote:
> > > > > > On Mon, 2009-03-30 at 16:19 +0100, N.J. Mann wrote:
> > > > > > > In message <1238424768.8491.331.camel@balrog.2hip.net>,
> > > > > > > 	Robert Noland (rnoland@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.
> > > > > > > > >=20
> > > > > > > > > First I did a svn update to r190540 to bring my sources u=
p to date and
> > > > > > > > > then I built a new 7-Stable world and kernel and installe=
d them.  Sadly,
> > > > > > > > > I still got the video mode corruption on exiting X or swi=
tching 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 g=
ot the same
> > > > > > > > > results.  (Xorg.log and dmesg.boot available if required.=
)  The changes
> > > > > > > > > I merged were: 190020, 190021, 190022, 190023, 190123, 19=
0124, 190125,
> > > > > > > > > 190163, 190164, 190166, 190170, 190282, 190399, 190400, 1=
9401 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!)
> > > > > > > > >=20
> > > > > > > > > Any ideas where to go from here?
> > > > > > > >=20
> > > > > > > > Which chip do you have?  I have a patch now that fixes vbla=
nk 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 s=
omething is
> > > > > > > > still wrong with interrupts on g45 though.
> > > > > > >=20
> > > > > > > Is this the information you require?
> > > > > > >=20
> > > > > > > % grep '^\(vga\|agp\|drm\)' r19054M.dmesg.boot
> > > > > > > vgapci0: <VGA-compatible display> port 0xf140-0xf147 mem 0xff=
900000-0xff97ffff,0xd0000000-0xdfffffff,0xff700000-0xff7fffff irq 16 at dev=
ice 2.0 on pci0
> > > > > > > agp0: <Intel G33 SVGA controller> on vgapci0
> > > > > > > vgapci0: Reserved 0x10000000 bytes for rid 0x18 type 3 at 0xd=
0000000
> > > > > > > vgapci0: Reserved 0x80000 bytes for rid 0x10 type 3 at 0xff90=
0000
> > > > > > > vgapci0: Reserved 0x100000 bytes for rid 0x1c type 3 at 0xff7=
00000
> > > > > > > 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 0xff90=
0000
> > > > > > > vgapci0: child drm0 requested pci_enable_busmaster
> > > > > > > vga: vga0 already exists; skipping it
> > > > > > > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xb=
ffff on isa0
> > > > > > >=20
> > > > > > > The MB is a Intel DG31GL, which incorporates an Intel GMA 310=
0 graphics
> > > > > > > adapter.
> > > > > >=20
> > > > > > Ok, you can try
> > > > > > http://people.freebsd.org/~rnoland/drm-intel-fix-033009.patch
> > > > >=20
> > > > > 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 prep=
are the
> > > > > evening meal. :-)
> > > > >=20
> > > > > Thanks for all your help.
> > > >=20
> > > > 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.
> > >=20
> > > This may be of no value, but it might be a useful data point.
> > >=20
> > > 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 wi=
th
> > > seemingly randomly colored squares that I'd estimate at 8x8 pixels ov=
er
> > > the left third of my screen and vertical stripes which may be duplica=
tes
> > > of one line of my background on the remainder.
> > >=20
> > > 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=
.
> > >=20
> > > 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.
> > >=20
> > > One very significant difference from other reports is that I am not
> > > running Intel graphics. I have an ATI(AMD) Radeon X300.
> > >=20
> > > Seems odd (though not unbelievable) that two drivers would exhibit th=
e
> > > same mis-behavior, at least in terms the the symptoms.
> >=20
> > Is this on CURRENT or STABLE and do you know at least approximately whe=
n
> > you started seeing the issue?
> >=20
> > robert.
> >=20
> > --=20
> > Robert Noland <rnoland@FreeBSD.org>
> > FreeBSD
>=20
> 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.
>=20
> 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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- drm_drv.c   (revision 189668)
+++ drm_drv.c   (revision 189669)
@@ -131,7 +131,7 @@
        .d_poll =3D       drm_poll,
        .d_mmap =3D       drm_mmap,
        .d_name =3D       "drm",
-       .d_flags =3D      D_TRACKCLOSE | D_NEEDGIANT
+       .d_flags =3D      D_TRACKCLOSE
 };
=20
 static struct drm_msi_blacklist_entry drm_msi_blacklist[] =3D {

robert.

--=20
Robert Noland <rnoland@FreeBSD.org>
FreeBSD

--=-jSf3i60RvaGh8LIp2x5z
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (FreeBSD)

iEYEABECAAYFAknRLUwACgkQM4TrQ4qfROMXKwCcDpDiKAUoYeU4Ns1iUZGpNOgQ
0JgAn0BPQmkr25k7ahRfLbe0t3PEgA+x
=bLd0
-----END PGP SIGNATURE-----

--=-jSf3i60RvaGh8LIp2x5z--




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1238445388.8491.358.camel>