Date: Mon, 24 Jan 2011 11:51:12 +0100 From: Gary Jennejohn <gljennjohn@googlemail.com> To: Doug Barton <dougb@FreeBSD.org> Cc: David Demelier <demelier.david@gmail.com>, freebsd-current@freebsd.org, Garrett Cooper <gcooper@FreeBSD.org> Subject: Re: why panic(9) ? Message-ID: <20110124115112.624daee1@ernst.jennejohn.org> In-Reply-To: <4D3CF1DE.8010403@FreeBSD.org> References: <AANLkTi=OQbS-0jJx0YwZhM7xDWPLOkaYYZAYfESUEvvM@mail.gmail.com> <AANLkTi=6ODRNH5Z_oRVzqWStAuv%2B4-aBDoUSY5baYkvQ@mail.gmail.com> <4D3CB2FE.2080603@gmail.com> <4D3CF1DE.8010403@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 23 Jan 2011 19:28:30 -0800 Doug Barton <dougb@FreeBSD.org> wrote: > On 01/23/2011 15:00, David Demelier wrote: > > In any case, when panic occurs, switching display to the tty can be > > great. Why not a sysctl like kern.tty_on_panic? Because when you're > > running X and a panic occurs not everybody understand what happens. > > Putting the following in /etc/sysctl.conf can help: > > debug.debugger_on_panic=0 > > The reason being that sometimes when you panic in X the system is > attempting to drop to the debugger, but can't, which is why it hangs. > For what it's worth this appears to be the default on -current. -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110124115112.624daee1>