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 <jh...@dataix.net> > To: Dan Naumov <dan.nau...@gmail.com> > Cc: FreeBSD Hackers <freebsd-hack...@freebsd.org>; freebsd- questi...@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-unsubscr...@freebsd.org" > > > > > _______________________________________________ > freebsd-hack...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > -- John Baldwin _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"