From owner-freebsd-current@FreeBSD.ORG  Sun Nov 30 16:35:59 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 F22DC16A4CE
	for <current@FreeBSD.org>; Sun, 30 Nov 2003 16:35:58 -0800 (PST)
Received: from email06.aon.at (WARSL402PIP3.highway.telekom.at [195.3.96.75])
	by mx1.FreeBSD.org (Postfix) with SMTP id 73A8843FAF
	for <current@FreeBSD.org>; Sun, 30 Nov 2003 16:35:56 -0800 (PST)
	(envelope-from shoesoft@gmx.net)
Received: (qmail 238588 invoked from network); 1 Dec 2003 00:35:54 -0000
Received: from m102p005.dipool.highway.telekom.at (HELO ?62.46.2.165?)
	([62.46.2.165]) (envelope-sender <shoesoft@gmx.net>)
	by qmail6rs.highway.telekom.at (qmail-ldap-1.03) with SMTP
	for <truckman@FreeBSD.org>; 1 Dec 2003 00:35:54 -0000
From: Stefan Ehmann <shoesoft@gmx.net>
To: Don Lewis <truckman@FreeBSD.org>
In-Reply-To: <200312010010.hB10A7eF025004@gw.catspoiler.org>
References: <200312010010.hB10A7eF025004@gw.catspoiler.org>
Content-Type: text/plain
Message-Id: <1070238961.5827.17.camel@shoeserv.freebsd>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Mon, 01 Dec 2003 01:36:02 +0100
Content-Transfer-Encoding: 7bit
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:35:59 -0000

On Mon, 2003-12-01 at 01:10, Don Lewis wrote:
> Can you reproduce this problem without bktr?
> 
<snip>
> 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.

No, I'm not using amd.

(kgdb) print *lkp
$1 = {lk_interlock = 0x0, lk_flags = 0, lk_sharecount = 0, lk_waitcount
= 0, 
  lk_exclusivecount = 0, lk_prio = 0, lk_wmesg = 0x0, lk_timo = 0, 
  lk_lockholder = 0x0, lk_newlock = 0x0}

This is indeed just NULLs.

I haven't tried without bktr yet but I hope I'll have time for that (and
the KASSERT) tomorrow.

The panic only seems to happen when accessing my read-only mounted ext2
partition. Today I tried not to access any data there and uptime is
14h30min now. The panic always happened after a few hours. So this is
probably the core of the problem.