From owner-freebsd-current@FreeBSD.ORG  Thu Sep 11 02:08:55 2003
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 880A116A4BF; Thu, 11 Sep 2003 02:08:55 -0700 (PDT)
Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DA17A43FE0; Thu, 11 Sep 2003 02:08:51 -0700 (PDT)
	(envelope-from ache@pobrecita.freebsd.ru)
Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1])
	by nagual.pp.ru (8.12.9/8.12.9) with ESMTP id h8B98o8d001018;
	Thu, 11 Sep 2003 13:08:50 +0400 (MSD)
	(envelope-from ache@pobrecita.freebsd.ru)
Received: (from ache@localhost)
	by pobrecita.freebsd.ru (8.12.9/8.12.9/Submit) id h8B98olo001017;
	Thu, 11 Sep 2003 13:08:50 +0400 (MSD)
	(envelope-from ache)
Date: Thu, 11 Sep 2003 13:08:49 +0400
From: Andrey Chernov <ache@nagual.pp.ru>
To: current@freebsd.org
Message-ID: <20030911090848.GA919@nagual.pp.ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
Subject: Double panics with g_up
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: Thu, 11 Sep 2003 09:08:55 -0000

I saw this already 5 times. It is _always_ double panic. Second panic may 
vary (f.e. clock, etc) but first one _always_ in g_up. Since second panic 
is on the way, there is no usable stack trace remains.

My suggestion: can we add sysctl to NOT sync disk after panic but reboot 
immediately to preserve stack frame (for remote machine)?

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code            = supervisor read, page not present
instruction pointer   = 0x8:0xc017fd3b
stack pointer         = 0x10:0xcd36bb70
frame pointer         = 0x10:0xcd36bb84
code segment          = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags      = interrupt enabled, resume, IOPL = 0
current process               = 3 (g_up)
trap number           = 12
panic: page fault

syncing disks, buffers remaining...

Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x24
fault code            = supervisor read, page not present
instruction pointer   = 0x8:0xc017fd3b
stack pointer         = 0x10:0xcd377c84
frame pointer         = 0x10:0xcd377c98
code segment          = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags      = interrupt enabled, resume, IOPL = 0
current process               = 24 (irq15: ahc0)
trap number           = 12
panic: page fault
Uptime: 2d3h22m53s