From owner-freebsd-current@FreeBSD.ORG Wed Aug 20 20:41:00 2003 Return-Path: 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 47E1D16A4BF for ; Wed, 20 Aug 2003 20:41:00 -0700 (PDT) Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au [210.50.30.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9AEC43FDF for ; Wed, 20 Aug 2003 20:40:59 -0700 (PDT) (envelope-from tim@robbins.dropbear.id.au) Received: from mail.robbins.dropbear.id.au (203.134.172.48) by smtp01.syd.iprimus.net.au (7.0.018) id 3F3287DF0030B6FB; Thu, 21 Aug 2003 13:40:58 +1000 Received: by mail.robbins.dropbear.id.au (Postfix, from userid 1000) id A59F0C921; Thu, 21 Aug 2003 13:40:54 +1000 (EST) Date: Thu, 21 Aug 2003 13:40:54 +1000 From: Tim Robbins To: Christian Brueffer Message-ID: <20030821034054.GA54061@dilbert.robbins.dropbear.id.au> References: <20030820222607.GA638@unixpages.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030820222607.GA638@unixpages.org> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: panic: bundirty: buffer 0xc776e118 still on queue 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2003 03:41:00 -0000 On Thu, Aug 21, 2003 at 12:26:07AM +0200, Christian Brueffer wrote: > Hi, > > just got a panic on following 5.1-CURRENT machine: > > FreeBSD gondor.middleearth 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Thu Aug > 7 21:32:39 CEST 2003 chris@haa konia.hitnet.rwth-aachen.de:/usr/obj/usr/src/sys/GONDOR i386 > > A dump is available if anyone needs specific information. [...] > panic: bundirty: buffer 0xc776e118 still on queue 2^M [...] > #2 0xc0254007 in panic (fmt=0xc03cc0ef "bundirty: buffer %p still on queue %d")^M > at /usr/src/sys/kern/kern_shutdown.c:550^M > #3 0xc029b291 in bundirty (bp=0xc776e118) at /usr/src/sys/kern/vfs_bio.c:1121^M > #4 0xc029bde1 in brelse (bp=0xc776e118) at /usr/src/sys/kern/vfs_bio.c:1436^M > #5 0xc02efcb8 in nfs_writebp (bp=0xc776e118, force=1, td=0xc2c17e40)^M > at /usr/src/sys/nfsclient/nfs_vnops.c:2987^M > #6 0xc02e02c3 in nfs_bwrite (bp=0x0) at /usr/src/sys/nfsclient/nfs_bio.c:76^M > #7 0xc029dd41 in getblk (vp=0xc2c77b68, blkno=400, size=15360, slpflag=256, slptimeo=0, flags=0)^M > at /usr/src/sys/kern/vfs_bio.c:2512^M > #8 0xc02e21e5 in nfs_getcacheblk (vp=0xc2c77b68, bn=400, size=15360, td=0xc2c17e40)^M > at /usr/src/sys/nfsclient/nfs_bio.c:1037^M I think I recognise this backtrace. Did you have a read-only NFS mount active at the time of the crash? In any case, a copy of your NFS entries from /etc/fstab (with any private data removed) would be helpful in tracking this problem down. Tim