Date: Sat, 11 Apr 2009 02:30:40 +0200 From: "Paul B. Mahol" <onemda@gmail.com> To: xorquewasp@googlemail.com Cc: freebsd-hackers@freebsd.org, Robert Noland <rnoland@freebsd.org> Subject: Re: diagnosing freezes (DRI?) Message-ID: <3a142e750904101730k53b7fbabn6e801ac36f1182e0@mail.gmail.com> In-Reply-To: <20090410211307.GA83697@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> <1239388293.1922.80.camel@balrog.2hip.net> <20090410211307.GA83697@logik.internal.network>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/10/09, xorquewasp@googlemail.com <xorquewasp@googlemail.com> wrote: > On 2009-04-10 13:31:33, Robert Noland wrote: >> >> 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. > > Ok. I've re-enabled drm.ko and radeon.ko and am running X. I'll leave > the system under load and let you know when it inevitably locks up... > > cheers, If it locks under X11 then use debug.debugger_on_panic=0 sysctl. Not doing this will increase drasticaly chances of locking whole system and not providing any debug data. -- Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750904101730k53b7fbabn6e801ac36f1182e0>