Date: Sat, 28 Mar 2009 03:55:23 -0500 From: Robert Noland <rnoland@FreeBSD.org> To: David Johnson <david@usermode.org> Cc: freebsd-stable@freebsd.org Subject: Re: X.org hanging under 7.2-PRERELEASE Message-ID: <1238230523.8491.253.camel@balrog.2hip.net> In-Reply-To: <1238222057.8491.224.camel@balrog.2hip.net> References: <200903271944.51781.david@usermode.org> <1238222057.8491.224.camel@balrog.2hip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-r48KmXLROd0dt7W59IMC Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2009-03-28 at 01:34 -0500, Robert Noland wrote: > On Fri, 2009-03-27 at 19:44 -0700, David Johnson wrote: > > I update -STABLE about once a week. On Wednesday I update, and subseque= ntly=20 > > started getting hangs and lockups. This happens only when DRI is enable= d. When=20 > > DRI is disabled there is no problem. The seriousness can vary. Sometime= s I can=20 > > ssh in from another machine to reboot, other times I can't. The last ti= me it=20 > > hung, top showed X.org at 100.0% CPU. The previous time it was stuck wi= th in a=20 > > "drmwtq" state. The hang always occurs within twenty minutes of starti= ng X. >=20 > Actually, the commits that I might have expected to cause this, haven't > been MFC'd yet. You probably did pick up the r6/7xx code in this > update. I also made an error in the GART mapping code, but that should > only effect pci(e) based radeons. >=20 > It could also be related to the 6.12.1 ati driver. AGP mode 4x is > always suspect as well, you might try reducing that to 2 or 1 and see if > the problems go away. >=20 > As for checking out an earlier release, with csup you just have to > specify a date that you want to checkout. See man csup and reference > the section titled CHECKOUT MODE. Actually, hanging in drmwtq is usually an indication of the card going belly up, or of interrupts being trashed. Make sure that you aren't getting an interrupt storm on a shared irq with drm/vgapci. Can you send me a full dmesg after drm is loaded and an xorg.log. Without drm, you really don't use interrupts, so... robert. > robert. >=20 > > Particulars: > > FreeBSD 7.2-PRERELEASE #2: Thu Mar 26 19:21:26 > > xf86-video-ati-6.12.1 (with Radeon X1550) > > kdelibs-4.2.1_1 > >=20 > > Relevant portions of my xorg.conf: > > Section "Module" > > Load "extmod" > > Load "dbe" > > Load "dri" > > Load "glx" > > Load "xtrap" > > Load "freetype" > > EndSection > >=20 > > Section "Device" > > Identifier "Card0" > > Driver "radeon" > > ... > > Option "AGPMode" "4" > > Option "RenderAccel" "on" > > Option "AccelMethod" "EXA" > > EndSection > >=20 > > I have had no prior problems with -STABLE. I have an Intel Q45 chipset,= so I=20 > > need to run -STABLE, and don't have the option of going back to -RELEAS= E. Is=20 > > there any easy way to go back to an earlier -STABLE? --=20 Robert Noland <rnoland@FreeBSD.org> FreeBSD --=-r48KmXLROd0dt7W59IMC 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) iEYEABECAAYFAknN5fsACgkQM4TrQ4qfROO8YQCfYdQNRuRKmkBdI/1e/6Dl0JRl PKAAnitE8P+5X2K1baXU+b+QKR/IFZ6T =UgEB -----END PGP SIGNATURE----- --=-r48KmXLROd0dt7W59IMC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1238230523.8491.253.camel>