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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
