Date: Tue, 05 Nov 2013 13:00:15 -0800 From: Colin Percival <cperciva@freebsd.org> To: John Baldwin <jhb@freebsd.org>, freebsd-current@freebsd.org Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org>, Alfred Perlstein <alfred@freebsd.org>, Jordan Hubbard <jkh@ixsystems.com> Subject: Re: Automated submission of kernel panic reports: sysutils/panicmail Message-ID: <52795C5F.7060008@freebsd.org> In-Reply-To: <201311051227.14157.jhb@freebsd.org> References: <527779ED.9040303@freebsd.org> <527797D8.5040404@freebsd.org> <527811B7.5090102@freebsd.org> <201311051227.14157.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/05/13 09:27, John Baldwin wrote: > One of my previous employers maintained a database of panics and I added ways > to recognize "known panics" and tag them. I ended up relying a lot on stack > trace details from specific OS versions to mark a panic as an instance of a > specific bug. Also, you may have very different stack traces even on the same > build version for a single bug. In the case of my employer we had a > constrained set of kernel configs and specific build versions to work with. > It might be harder to correctly match panics in the wild what with patched > trees and random kernel configs. Right, I'm sure there will be panics I can't match up against anything else -- but this is fine. If I get enough panic reports, I can still get useful data out even if some of them aren't immediately usable. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52795C5F.7060008>