From owner-freebsd-current Sun Mar 16 0:14:38 2003 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 4EE9637B401; Sun, 16 Mar 2003 00:14:36 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BFAA43FA3; Sun, 16 Mar 2003 00:14:35 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h2G8EWO76711; Sun, 16 Mar 2003 03:14:32 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Sun, 16 Mar 2003 03:14:32 -0500 (EST) From: Jeff Roberson To: Morten Rodal Cc: Doug Barton , Attila Nagy , Subject: Re: kern/49079: panic: bwrite: buffer is not busy In-Reply-To: <20030316075920.GA5468@slurp.rodal.no> Message-ID: <20030316031330.O41845-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Based on this output from your gdb session it looks like the code in boot() did run and potentially alter this buffer. panic: bwrite: buffer is not busy??? panic messages: --- panic: bwrite: buffer is not busy??? cpuid = 1; lapic.id = 00000000 Stack backtrace: boot() called on cpu#1 Can you disable sync on panic? The buf must have been modified. That section of code is never entered with b_xflags == 0. The contents of the buf just dont make sense with the panic.. Cheers, Jeff On Sun, 16 Mar 2003, Morten Rodal wrote: > On Sun, Mar 16, 2003 at 02:46:13AM -0500, Jeff Roberson wrote: > > On Sat, 15 Mar 2003, Morten Rodal wrote: > > > > > On Fri, Mar 14, 2003 at 06:47:27PM +0100, Morten Rodal wrote: > > > [snip the parent post] > > > > > > I just got another one of these. This time it didn't double panic > > > while syncing the disks. I've been getting this quite often now, > > > almost daily. If there is anything else I can help you with to get to > > > the bottom of this problem don't hesitate to ask. > > > > > > Attached is a the gdb output and the backtrace from DDB. > > > > Excelent, can you open up the kernel in gdb again. Then do the following: > > > > frame 3 > > print bp > > > > With this information I should be able to find the problem. > > > > -- > Morten Rodal > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message