From owner-freebsd-current@FreeBSD.ORG Tue Nov 5 21:01:51 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id E5DD75CF for ; Tue, 5 Nov 2013 21:01:51 +0000 (UTC) (envelope-from bounces+73574-dfb6-freebsd-current=freebsd.org@sendgrid.me) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) by mx1.freebsd.org (Postfix) with SMTP id 7CC1C2677 for ; Tue, 5 Nov 2013 21:01:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h=from:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=4gVMKdsg3RpsJj/QrPk447Ju66Q=; b=yhLPWKOiXnNLjGTS0N 1OAcI7V73fy0LhTeC9hRJygFFdqiqJlguX0iJR+cN7exTY0dQm9LISbwJYOipa4z rtMX4e50RBjB8lA4pyjgZ31G3XJbM8gEl3tUQg5iaLRH9z+IVri1+NeXMvdBCOjI t7O/L2wFh8HQogCZ3HttryJ9Q= Received: by mf83.sendgrid.net with SMTP id mf83.25880.52795CBE13 Tue, 05 Nov 2013 21:01:50 +0000 (GMT) Received: from mail.tarsnap.com (unknown [10.60.208.13]) by mi34 (SG) with ESMTP id 1422a124948.3eaf.38f537 for ; Tue, 05 Nov 2013 15:01:50 -0600 (CST) Received: (qmail 28414 invoked from network); 5 Nov 2013 21:01:49 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 5 Nov 2013 21:01:49 -0000 Received: (qmail 9076 invoked from network); 5 Nov 2013 21:00:15 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 5 Nov 2013 21:00:15 -0000 Message-ID: <52795C5F.7060008@freebsd.org> Date: Tue, 05 Nov 2013 13:00:15 -0800 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: John Baldwin , freebsd-current@freebsd.org Subject: Re: Automated submission of kernel panic reports: sysutils/panicmail References: <527779ED.9040303@freebsd.org> <527797D8.5040404@freebsd.org> <527811B7.5090102@freebsd.org> <201311051227.14157.jhb@freebsd.org> In-Reply-To: <201311051227.14157.jhb@freebsd.org> X-Enigmail-Version: 1.5.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SG-EID: XhyBwObMhraAR+zdwMupjQ6BIqbhdEfc+6p+uBxS7S88hDVo7wPr0+CK+tH/z+ym609FdjgYpb1IEBu78V5clejnBFYfJO+hs3vHTkKq2DKvpGW7mF4gP1PkvGvTrpZhfaipAhky9po77rtEpg7enF6htHV5MtQR8UOTiviMA/8= Cc: FreeBSD Hackers , Alfred Perlstein , Jordan Hubbard X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 21:01:52 -0000 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