From owner-freebsd-current@FreeBSD.ORG  Thu Sep 11 09:44:26 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 6B68E16A4BF
	for <current@freebsd.org>; Thu, 11 Sep 2003 09:44:26 -0700 (PDT)
Received: from critter.freebsd.dk (p26.n-sfpop02.stsn.com [199.107.153.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8035443FF5
	for <current@freebsd.org>; Thu, 11 Sep 2003 09:44:25 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h8BGiMeG002647;
	Thu, 11 Sep 2003 18:44:25 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: Andrey Chernov <ache@nagual.pp.ru>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 11 Sep 2003 13:08:49 +0400."
             <20030911090848.GA919@nagual.pp.ru> 
Date: Thu, 11 Sep 2003 18:44:22 +0200
Message-ID: <2646.1063298662@critter.freebsd.dk>
cc: current@freebsd.org
Subject: Re: 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 16:44:26 -0000


I have yet to see any information from you I can use to do debugging.

See our handbook if you are in doubt what we need.

Poul-Henning

In message <20030911090848.GA919@nagual.pp.ru>, Andrey Chernov writes:
>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
>

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.