Date: Fri, 10 Apr 2009 13:31:33 -0500 From: Robert Noland <rnoland@FreeBSD.org> To: xorquewasp@googlemail.com Cc: freebsd-hackers@freebsd.org Subject: Re: diagnosing freezes (DRI?) Message-ID: <1239388293.1922.80.camel@balrog.2hip.net> In-Reply-To: <20090410175922.GA50520@logik.internal.network> References: <20090410132354.GA20721@logik.internal.network> <20090410154251.GA49384@logik.internal.network> <1239385368.1922.74.camel@balrog.2hip.net> <20090410175922.GA50520@logik.internal.network>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-ABgEv5/yoxMYHp9F+ppQ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2009-04-10 at 18:59 +0100, xorquewasp@googlemail.com wrote: > Hello. >=20 > On 2009-04-10 12:42:48, Robert Noland wrote: > >=20 > > Are you running powerd by chance? I was seeing an issue that seemed to > > be related to powerd. Since I've disabled it on that box, it hasn't > > hung up any more. >=20 > I'm not running powerd, no. >=20 > >=20 > > As far as drm is concerned, I've been running on an x1650 for probably = a > > week now while working mostly on port stuff and I haven't seen any > > issues. This is with full 3d and compiz running, etc... So, if it is > > drm related... we are going to have to dig up some debugging info > > somehow... > >=20 > > robert. > >=20 >=20 > The system doesn't seem to have frozen since DRI/DRM was disabled. >=20 > I did have one crash/reboot whilst building a large number of packages > with tinderbox. I've currently got both tinderbox and a make -j 16 > buildworld going on a loop in the hope that I can trigger it again. >=20 > Being the idiot I am, I had encrypted swap enabled and so savecore > didn't save anything. Won't make that mistake twice. >=20 > I'm currently using a world compiled WITH_DEBUG but is there anything > else I can do? If it is locking the whole system, then a core is really our best shot. If you can extract anything useful from xorg.log or setting hw.dri.0.debug that also might be of use. I'm running on 2 cores, but it is possible that some locking issue exists. All of the driver specific ioctls are run under a lock though. robert. > thanks, > xw > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " --=20 Robert Noland <rnoland@FreeBSD.org> FreeBSD --=-ABgEv5/yoxMYHp9F+ppQ 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) iEYEABECAAYFAknfkIUACgkQM4TrQ4qfROM1BgCdGTQClBQdo+yaZbueBjQmh+aD ykEAn11Fy70MGp04+K5UyMUnJEYUTsju =hK7c -----END PGP SIGNATURE----- --=-ABgEv5/yoxMYHp9F+ppQ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1239388293.1922.80.camel>