From owner-freebsd-alpha@FreeBSD.ORG  Mon Aug  4 02:01:26 2003
Return-Path: <owner-freebsd-alpha@FreeBSD.ORG>
Delivered-To: freebsd-alpha@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4C89F37B401
	for <freebsd-alpha@freebsd.org>; Mon,  4 Aug 2003 02:01:26 -0700 (PDT)
Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net
	[207.217.120.218])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B9D0D43F75
	for <freebsd-alpha@freebsd.org>;
	Mon,  4 Aug 2003 02:01:23 -0700 (PDT)
	(envelope-from tlambert2@mindspring.com)
Received: from user-2ivfnf5.dialup.mindspring.com ([165.247.221.229]
	helo=mindspring.com)
	by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128)
	(Exim 3.33 #1)	id 19jbDU-0001oa-00; Mon, 04 Aug 2003 02:01:20 -0700
Message-ID: <3F2E20A2.5D45C4F3@mindspring.com>
Date: Mon, 04 Aug 2003 02:00:18 -0700
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Andrew Gallatin <gallatin@cs.duke.edu>
References: <16173.23401.983536.279158@grasshopper.cs.duke.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4bf31a7df29b29cb38130f42d023d51cb350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
cc: freebsd-alpha@freebsd.org
Subject: Re: another vm/pmap alpha panic
X-BeenThere: freebsd-alpha@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Alpha <freebsd-alpha.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-alpha>,
	<mailto:freebsd-alpha-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-alpha>
List-Post: <mailto:freebsd-alpha@freebsd.org>
List-Help: <mailto:freebsd-alpha-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-alpha>,
	<mailto:freebsd-alpha-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Aug 2003 09:01:26 -0000

Andrew Gallatin wrote:
> panic: pmap_remove_all: pv_table for 8306000 is inconsistent
> Stack backtrace:
> db_print_backtrace() at db_print_backtrace+0x18
> backtrace() at backtrace+0x2c
> panic() at panic+0x148
> pmap_remove_all() at pmap_remove_all+0xfc
> vm_object_page_remove() at vm_object_page_remove+0x1b0
> vm_map_delete() at vm_map_delete+0x438
> vm_map_remove() at vm_map_remove+0x64
> exit1() at exit1+0x950
> sys_exit() at sys_exit+0x88
> syscall() at syscall+0x398
> XentSys() at XentSys+0x64
> --- syscall (1) ---
> --- user mode ---
> 
> Of course, the crashdump is not usable.

Despite what Greg says, it's useful to use the gdb "list" command
against the binary addresses to determine the line of code where
your kernel is actually failing.

Specifically,

	gdb -k kernel.debug
	(gdb) list *(vm_object_page_remove+1b0)

(One had to wonder why the "list" command exists, if it's as useless
 as Greg claims).

-- Terry