Date: Sat, 19 Jun 2010 19:33:16 +0300 From: Andriy Gapon <avg@freebsd.org> To: Andriy Gapon <avg@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: KDB_TRACE in GENERIC Message-ID: <4C1CF14C.8080108@freebsd.org> In-Reply-To: <20100619143920.GM3632@acme.spoerlein.net> References: <4C1C7686.3050206@freebsd.org> <20100619143920.GM3632@acme.spoerlein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
on 19/06/2010 17:39 Ulrich Spörlein said the following: > On Sat, 19.06.2010 at 10:49:26 +0300, Andriy Gapon wrote: >> I propose to add the following options into GENERIC (perhaps only i386 and amd64): >> >> options KDB >> options KDB_TRACE >> options KDB_UNATTENDED >> options SC_DISABLE_KDBKEY # <- not sure about his one >> >> This would increase kernel size only by a fraction, would not result in any POLA >> violations (KDB_UNATTENDED, SC_DISABLE_KDBKEY) and would provide a useful service. >> >> Currently we get many panic reports that are almost impossible to analyze >> because there is no stack trace. Especially this is true for panics at >> installation time, when people use GENERIC from release media and do not have >> ability to try a custom kernel. >> >> What do you think? > > I'd rather propose we turn on textdumps, as many people will be in X11 > when disaster strikes and there's no easy way to get the crashdump then. Would you really "rather" propose it? Or propose it in addition to what I proposed? Or as a next step even? :-) BTW, as I said, I am very much concerned about panics that people get when running (trying to run) FreeBSD installation image, X is not a factor at that stage. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C1CF14C.8080108>