From owner-svn-src-head@freebsd.org Wed Apr 25 18:44:58 2018 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9793BFAC882; Wed, 25 Apr 2018 18:44:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B647693C0; Wed, 25 Apr 2018 18:44:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 3972B10AFD3; Wed, 25 Apr 2018 14:44:57 -0400 (EDT) From: John Baldwin To: Conrad Meyer Cc: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r332959 - head/sys/kern Date: Wed, 25 Apr 2018 09:54:55 -0700 Message-ID: <5237617.Ai8m1U92WL@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <201804241854.w3OIsKuQ083232@repo.freebsd.org> References: <201804241854.w3OIsKuQ083232@repo.freebsd.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Wed, 25 Apr 2018 14:44:57 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.25 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: Wed, 25 Apr 2018 18:44:58 -0000 On Tuesday, April 24, 2018 06:54:20 PM Conrad Meyer wrote: > Author: cem > Date: Tue Apr 24 18:54:20 2018 > New Revision: 332959 > URL: https://svnweb.freebsd.org/changeset/base/332959 > > Log: > panic: Optionally, trace secondary panics > > To diagnose and fix secondary panics, it is useful to have a stack trace. > When panic tracing is enabled, optionally trace secondary panics as well. > > The option is configured with the tunable/sysctl debug.trace_all_panics. > > (The original concern that inspired only tracing the primary panic was > likely that the secondary trace may scroll the original panic message or trace > off the screen. This is less of a concern for serial consoles with logging. > Not everything has a serial console, though, so the behavior is optional.) Note that KDB_TRACE is enabled by default, so you would need it to always default to false to preserve existing behavior by default. -- John Baldwin