From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 4 13:43:28 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF36B1065672; Thu, 4 Mar 2010 13:43:28 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout3.freenet.de (mout3.freenet.de [IPv6:2001:748:100:40::2:5]) by mx1.freebsd.org (Postfix) with ESMTP id 755918FC1C; Thu, 4 Mar 2010 13:43:28 +0000 (UTC) Received: from [195.4.92.20] (helo=10.mx.freenet.de) by mout3.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.72 #1) id 1NnBKl-0006rl-Vf; Thu, 04 Mar 2010 14:43:23 +0100 Received: from p57ae1de2.dip0.t-ipconnect.de ([87.174.29.226]:61705 helo=ernst.jennejohn.org) by 10.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.72 #2) id 1NnBKl-0003of-P4; Thu, 04 Mar 2010 14:43:23 +0100 Date: Thu, 4 Mar 2010 14:43:21 +0100 From: Gary Jennejohn To: jhell Message-ID: <20100304144321.39ad948d@ernst.jennejohn.org> In-Reply-To: References: X-Mailer: Claws Mail 3.7.4 (GTK+ 2.16.2; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Hackers , Dan Naumov , freebsd-questions@freebsd.org Subject: Re: Automated kernel crash reporting system X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Mar 2010 13:43:29 -0000 On Thu, 4 Mar 2010 08:06:50 -0500 jhell wrote: > > 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 ? > This feature is mentioned as a mechanism which could be used as part of the automatic reporting functionality. So it's not quite the same thing. --- Gary Jennejohn