From owner-freebsd-current@FreeBSD.ORG  Tue Mar  8 22:34:39 2005
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 35CF216A4CF; Tue,  8 Mar 2005 22:34:39 +0000 (GMT)
Received: from plounts.uits.indiana.edu (plounts.uits.indiana.edu
	[129.79.1.73])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id C227043D3F; Tue,  8 Mar 2005 22:34:38 +0000 (GMT)
	(envelope-from dmschei@attglobal.net)
Received: from mail-relay.iu.edu (logchain.uits.indiana.edu [129.79.1.77])
	j28MYZ1x024751;	Tue, 8 Mar 2005 17:34:35 -0500 (EST)
Received: from [149.161.16.16] (viper-016-client.iusb.edu [149.161.16.16])
	(authenticated bits=0)j28MYZsY006408;
	Tue, 8 Mar 2005 17:34:35 -0500 (EST)
Message-ID: <422E287A.80805@attglobal.net>
Date: Tue, 08 Mar 2005 17:34:34 -0500
From: David Scheidt <dmschei@attglobal.net>
User-Agent: Mozilla Thunderbird 1.0 (X11/20050102)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Kris Kennaway <kris@FreeBSD.org>
References: <2861.172.16.0.199.1109814152.squirrel@172.16.0.199>
	<20050303015438.GF15329@obiwan.tataz.chchile.org>
	<2910.172.16.0.199.1109816379.squirrel@172.16.0.199>
	<1646.172.16.0.199.1110049506.squirrel@172.16.0.199>
	<4420.172.16.0.199.1110301463.squirrel@172.16.0.199>
	<20050308100730.Q38988@carver.gumbysoft.com>
	<20050308184005.GA30165@hub.freebsd.org>
In-Reply-To: <20050308184005.GA30165@hub.freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: Mike Jakubik <mikej@rogers.com>
cc: freebsd-current@FreeBSD.org
Subject: Re: Reproducible Panic with port iplog
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2005 22:34:39 -0000

Kris Kennaway wrote:
> On Tue, Mar 08, 2005 at 10:09:01AM -0800, Doug White wrote:
> 
>>On Tue, 8 Mar 2005, Mike Jakubik wrote:
>>

>>>It does not seem to be for me. The system just stands there doing nothing
>>>after the panic, when there is no debugger built in the kernel.
>>>
>>>P.S. I have also submitted a PR for this.
>>>http://www.freebsd.org/cgi/query-pr.cgi?pr=78384
>>
>>I don't know if I can get to this before the release, but I've put it on
>>my tracking list.  I need a way to provoke a panic, and the best way seems
>>to be to program the syscons panic key.
> 
> 
> I've seen DDB_UNATTENDED cause a hang-on-panic instead of a dump +
> reboot on HEAD.  I've also seen it not dumping core when it does
> manage to reboot.  I haven't tested this on RELENG_5.
> 
>

Both my ThinkPad and a desktop box I've got running RELENG_5 hang on 
panic.  No reboot, no dump.  Have to pull the battery from the ThinkPad 
to get it to reboot.  dumpdev is set in rc.conf on both machines.