From owner-freebsd-current@FreeBSD.ORG  Sun Nov 30 16:10:16 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 4672C16A4CF
	for <current@FreeBSD.org>; Sun, 30 Nov 2003 16:10:16 -0800 (PST)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 59A7A43FCB
	for <current@FreeBSD.org>; Sun, 30 Nov 2003 16:10:15 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id hB10A7eF025004;
	Sun, 30 Nov 2003 16:10:11 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200312010010.hB10A7eF025004@gw.catspoiler.org>
Date: Sun, 30 Nov 2003 16:10:07 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: shoesoft@gmx.net
In-Reply-To: <1070193640.2995.8.camel@shoeserv.freebsd>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: current@FreeBSD.org
Subject: Re: 5.2-BETA panic: page fault
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: Mon, 01 Dec 2003 00:10:16 -0000

Can you reproduce this problem without bktr?

> #6  0xc06743d8 in calltrap () at {standard input}:94
> #7  0xc0505b53 in _mtx_lock_flags (m=0x0, opts=0, 
>     file=0xc06bfc1d "/usr/src/sys/kern/kern_lock.c", line=228)
>     at /usr/src/sys/kern/kern_mutex.c:214
> #8  0xc0502b54 in lockmgr (lkp=0xc3b2e028, flags=0, interlkp=0xe4, 
>     td=0xc06bfc1d) at /usr/src/sys/kern/kern_lock.c:228
> #9  0xc0566d87 in vfs_busy (mp=0x0, flags=16, interlkp=0xc075d0e0,
> td=0x0)
>     at /usr/src/sys/kern/vfs_subr.c:527
> #10 0xc056cfff in sync (td=0xc0730dc0, uap=0x0)

> #16 0xc06743d8 in calltrap () at {standard input}:94
> #17 0xc0505b53 in _mtx_lock_flags (m=0x0, opts=0, 
>     file=0xc06bfc1d "/usr/src/sys/kern/kern_lock.c", line=228)
>     at /usr/src/sys/kern/kern_mutex.c:214
> #18 0xc0502b54 in lockmgr (lkp=0xc3b2e028, flags=0, interlkp=0xe4, 
>     td=0xc06bfc1d) at /usr/src/sys/kern/kern_lock.c:228
> #19 0xc0566d87 in vfs_busy (mp=0x0, flags=0, interlkp=0x0, td=0x0)
>     at /usr/src/sys/kern/vfs_subr.c:527
> #20 0xc056374c in lookup (ndp=0xd7f2ec00) at
> /usr/src/sys/kern/vfs_lookup.c:559

You are getting a double panic, with the second happening during the
file system sync.  The code seems to be be tripping over the same mount
list entry each time.  Maybe the mount list is getting corrupted.  Are
you using amd?  Print *lkp in the lockmgr() stack frame.


You might want to add
	KASSERT(mp->mnt_lock.lk_interlock !=NULL, "vfs_busy: NULL mount
        pointer interlock");
at the top of vfs_busy() and right before the lockmgr() call.