Date: Mon, 30 Mar 2009 11:18:22 -0500 From: Robert Noland <rnoland@FreeBSD.org> To: "N.J. Mann" <njm@njm.me.uk> Cc: freebsd-x11@FreeBSD.org Subject: Re: Xorg 7.4 crashes on exit Message-ID: <1238429902.8491.336.camel@balrog.2hip.net> In-Reply-To: <20090330151923.GB920@titania.njm.me.uk> References: <200903250150.n2P1ou4g062376@svn.freebsd.org> <20090325092904.GA2801@titania.njm.me.uk> <1237999344.1828.6.camel@balrog.2hip.net> <20090227141146.GA88783@titania.njm.me.uk> <20090330105326.GA920@titania.njm.me.uk> <1238424768.8491.331.camel@balrog.2hip.net> <20090330151923.GB920@titania.njm.me.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-mvzJF4N2KP9fqLIcKlo5 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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: > > > Hi Robert, > > >=20 > > >=20 > > > [Moved from svn-src-all@ to x11@ to merge threads.] > > >=20 > > > In message <1237999344.1828.6.camel@balrog.2hip.net>, > > > Robert Noland (rnoland@FreeBSD.org) wrote: > > > > On Wed, 2009-03-25 at 09:29 +0000, N.J. Mann wrote: > > > > > In message <200903250150.n2P1ou4g062376@svn.freebsd.org>, > > > > > Robert Noland (rnoland@FreeBSD.org) wrote: > > > > > > Author: rnoland > > > > > > Date: Wed Mar 25 01:50:56 2009 > > > > > > New Revision: 190401 > > > > > > URL: http://svn.freebsd.org/changeset/base/190401 > > > > > >=20 > > > > > > Log: > > > > > > Rework the management of vblank interrupts a bit. > > > > > > =20 > > > > > > When a vt switch occurs the irq handler is uninstalled. Inte= rrupts > > > > > > and the state tracking of what was enabled/disabled wasn't wo= rking > > > > > > properly. This should resolve the reports of "slow windows" = after a > > > > > > vt switch, among other things. The radeon 2d driver seems to= work a > > > > > > bit more correctly than the Intel driver. With the Intel dri= ver, > > > > > > vblank interrupts will be enabled at system startup and will = only > > > > > > be disabled after an additional modeset (vt switch, dpms, ran= dr event). > > > > > > =20 > > > > > > With this patch, I am able to run glxgears synced to vblank a= nd > > > > > > vt switch while it is running without ill effects. > > > > > > =20 > > > > > > MFC after: 3 days > > > > > >=20 > > > > > > Modified: > > > > > > head/sys/dev/drm/drm_irq.c > > > > >=20 > > > > > Is this a possible cure for the problem I reported here: > > > > > http://lists.freebsd.org/pipermail/freebsd-x11/2009-February/0076= 70.html > > > >=20 > > > > It could be... interrupts were not working correcty, especially on > > > > Intel. There is likely still an issue with restarting X that I nee= d to > > > > look into, but I've not seen a problem vt switching or shutting dow= n. > > >=20 > > > Okay I tried out your recent changes this morning. > > >=20 > > > First I did a svn update to r190540 to bring my sources up to date an= d > > > then I built a new 7-Stable world and kernel and installed them. Sad= ly, > > > 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 chang= es > > > 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 everythi= ng > > > to make it easier for me. (I am very much still testing the water wi= th > > > 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 vblank issues, a= t > > 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. >=20 > Is this the information you require? >=20 > % grep '^\(vga\|agp\|drm\)' r19054M.dmesg.boot > vgapci0: <VGA-compatible display> port 0xf140-0xf147 mem 0xff900000-0xff9= 7ffff,0xd0000000-0xdfffffff,0xff700000-0xff7fffff irq 16 at device 2.0 on p= ci0 > 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 >=20 > The MB is a Intel DG31GL, which incorporates an Intel GMA 3100 graphics > adapter. >=20 >=20 > Cheers, > Nick. Ok, Are you seeing the corruption with an unpatched 7-STABLE? Just looking at what I need to merge and none of the latest Intel stuff is in STABLE that I can see. robert. > --=20 > "Nothing stands for content-free corporate bullshit quite like PowerPoint= ." >=20 --=20 Robert Noland <rnoland@FreeBSD.org> FreeBSD --=-mvzJF4N2KP9fqLIcKlo5 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) iEYEABECAAYFAknQ8M4ACgkQM4TrQ4qfRONjTQCfWIwLcU/DeeASJcuQ5z4RyxgQ CpwAnApCMPPrZ7zJiIGX0djM4gQ+gs5u =IlGV -----END PGP SIGNATURE----- --=-mvzJF4N2KP9fqLIcKlo5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1238429902.8491.336.camel>