Date: Fri, 5 Mar 2010 07:57:26 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-hackers@freebsd.org Cc: Dan Naumov <dan.naumov@gmail.com>, freebsd-questions@freebsd.org, sean connolly <connollys1@yahoo.com> Subject: Re: Automated kernel crash reporting system Message-ID: <201003050757.26890.jhb@freebsd.org> In-Reply-To: <775910.52553.qm@web35807.mail.mud.yahoo.com> References: <cf9b1ee01003040409xeba9a74q60d0f3bbc039b147@mail.gmail.com> <alpine.BSF.2.00.1003040802540.46189@pragry.qngnvk.ybpny> <775910.52553.qm@web35807.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <jhell@DataIX.net> > To: Dan Naumov <dan.naumov@gmail.com> > Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>; 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201003050757.26890.jhb>