Date: Sat, 11 Apr 2009 23:26:43 +0200 From: "Paul B. Mahol" <onemda@gmail.com> To: xorquewasp@googlemail.com Cc: freebsd-hackers@freebsd.org Subject: Re: diagnosing freezes (DRI?) Message-ID: <3a142e750904111426u43c11a38wc6b385d3ff215673@mail.gmail.com> In-Reply-To: <20090411101559.GC83697@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> <3a142e750904101730k53b7fbabn6e801ac36f1182e0@mail.gmail.com> <20090411101559.GC83697@logik.internal.network>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/11/09, xorquewasp@googlemail.com <xorquewasp@googlemail.com> wrote: > On 2009-04-11 02:30:40, Paul B. Mahol wrote: >> >> 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. > > I don't seem to have that sysctl. > > You sure that's the correct name? Well if you dont have it, capturing cores should generaly still work. But in this case some kind of serial console is only remaining option. -- Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750904111426u43c11a38wc6b385d3ff215673>