From owner-freebsd-questions@FreeBSD.ORG Fri Mar 5 13:43:44 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6222A1065678; Fri, 5 Mar 2010 13:43:44 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 307EB8FC24; Fri, 5 Mar 2010 13:43:44 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id CDE8D46B45; Fri, 5 Mar 2010 08:43:43 -0500 (EST) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 4A0C48A021; Fri, 5 Mar 2010 08:43:31 -0500 (EST) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Fri, 5 Mar 2010 07:57:26 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <775910.52553.qm@web35807.mail.mud.yahoo.com> In-Reply-To: <775910.52553.qm@web35807.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201003050757.26890.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Fri, 05 Mar 2010 08:43:31 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.5 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Dan Naumov , freebsd-questions@freebsd.org, sean connolly Subject: Re: Automated kernel crash reporting system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2010 13:43:44 -0000 On Thursday 04 March 2010 8:50:56 am sean connolly wrote: > Hi Dan, > > Automatic reporting would end up being a mess given that panics can be caused by hardware problems. Having an autoreport check if memtest was run before it reports, or having it only run with -CURRENTmight be useful. That's not quite true. Many hardware failure-type panics look the same (a machine check exception panic, an NMI due to a hardware error (this has a unique panic message), or panics in pmap_remove*() on x86 cover the vast majority of them). My previous employer actually did track panics using a script like crashinfo, and I was able to categorize known panics by looking for signatures in stack backtraces or other panic messages. > ________________________________ > From: jhell > To: Dan Naumov > Cc: FreeBSD Hackers ; freebsd- questions@freebsd.org > Sent: Thu, March 4, 2010 8:06:50 AM > Subject: Re: Automated kernel crash reporting system > > > On Thu, 4 Mar 2010 07:09, dan.naumov@ wrote: > > Hello > > > > I noticed the following on the FreeBSD website: > > http://www.freebsd.org/projects/ideas/ideas.html#p-autoreport Has > > there been any progress/work done on the automated kernel crash > > reporting system? The current ways of enabling and gathering the > > information required by developers for investigating panics and > > similar issues are unintuitive and user-hostile to say the least and > > anything to automate the process would be a very welcome addition. > > > > > > - Sincerely, > > Dan Naumov > > > > Hi Dan, > > I am assuming that the output of crashinfo_enable="YES" is not what you > are talking about is it ? are you aware of it ? > > The info contained in the crashinfo.txt.N is pretty informative for > developers, maybe your talking about another way of submitting it ? > > Regards, > > -- > > jhell > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > > > > _______________________________________________ > 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" > -- John Baldwin