From owner-svn-src-head@FreeBSD.ORG Tue Sep 28 18:34:19 2010 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 336F7106564A; Tue, 28 Sep 2010 18:34:19 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (60.wheelsystems.com [83.12.187.60]) by mx1.freebsd.org (Postfix) with ESMTP id 7876B8FC1F; Tue, 28 Sep 2010 18:34:18 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 9AD7645C99; Tue, 28 Sep 2010 20:34:16 +0200 (CEST) Received: from localhost (chello089077043238.chello.pl [89.77.43.238]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 90A46456B1; Tue, 28 Sep 2010 20:34:10 +0200 (CEST) Date: Tue, 28 Sep 2010 20:33:50 +0200 From: Pawel Jakub Dawidek To: John Baldwin Message-ID: <20100928183350.GB2224@garage.freebsd.pl> References: <20100922222441.00002f27@unknown> <20100923.203143.19192035494300157.imp@bsdimp.com> <1285297884.17619.17.camel@neo.cse.buffalo.edu> <201009240923.04406.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cmJC7u66zC7hs+87" Content-Disposition: inline In-Reply-To: <201009240923.04406.jhb@freebsd.org> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT amd64 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: bruce@cran.org.uk, src-committers@freebsd.org, Ken Smith , svn-src-all@freebsd.org, avg@freebsd.org, gavin@freebsd.org, svn-src-head@freebsd.org, "M. Warner Losh" Subject: Re: svn commit: r212964 - head/sys/kern X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Sep 2010 18:34:19 -0000 --cmJC7u66zC7hs+87 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Sep 24, 2010 at 09:23:04AM -0400, John Baldwin wrote: > > Because disks are big and (again, just trying to explain my > > understanding of what I inherited) we want all the support > > to be in place, just not turned on. There is a difference > > between "You can give us much better information by doing > > > .symbols goo> and then making a one-line change to rc.conf" > > versus "You can give us much better information by making > > a one-line change to rc.conf". >=20 > The biggest argument against this (and the reason I always enable crashdu= mps > on all machines I am involved with) is that many panics are not easily > reproducible, esp. ones that trigger under load. If dumpdev is not on by > default, then the info from a rare or hard-to-trigger bug may simply be l= ost. > Also, "just send-pr or mail the 'foo' file" is even simpler than "enable = this > knob in rc.conf and reproduce your issue, then come back". I am bigger fan of textdumps than minidumps, because in my opinion textdumps provide quite a lot of useful info. I'm working with FreeBSD kernel for years now and almost entirely avoided gdb for kernel debugging. DDB and printf(9) are in 99% enough for me (maybe I'm too traditional, but that's the fact). I'm not saying that textdumps are enough in 99%, though. > Well, if we turn it on we should document it clearly. Folks are already > interested in asking for help once a machine panics, and if the reply to a > query on questions@ can say "please go look for a file named 'foo' and e-= mail > it somewhere or send-pr it", that is far simpler than having to enable du= mps > and reproduce the panic. Another important thing in my opinion is privacy of user's data. Once the data hit the disk it can stay there forever. This is why I use encrypted swap everywhere. I'd never send kernel minidump from my laptop or from any of my servers to anyone, but I'd be happy to send textdump. I find textdumps a great solution that's in the middle between protecting user's privacy and providing a lot of useful info and I'd much prefer to turn on textdumps by default and eventually extend what we dump, than to make minidumps the default. You can always ask user to add this one-line to rc.conf to turn minidump on and provide you the info that was missing in textdump. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --cmJC7u66zC7hs+87 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkyiNQ4ACgkQForvXbEpPzSy8wCaAwcKyVSd72hS+HPLwrj+JM9X h4YAnilkHL9SU+H/tTCwKgEJZETGhab0 =vZn7 -----END PGP SIGNATURE----- --cmJC7u66zC7hs+87--