Date: Sun, 17 Mar 2002 13:31:30 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Kris Kennaway <kris@obsecurity.org> Cc: current@FreeBSD.org, fs@FreeBSD.org Subject: Re: panic: bwrite: buffer is not busy??? Message-ID: <20020317133130.A35137@xor.obsecurity.org> In-Reply-To: <20020317124958.A34008@xor.obsecurity.org>; from kris@obsecurity.org on Sun, Mar 17, 2002 at 12:49:58PM -0800 References: <20020317124958.A34008@xor.obsecurity.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sun, Mar 17, 2002 at 12:49:58PM -0800, Kris Kennaway wrote: > I tried upgrading the bento cluster to 5.x so I can actually get 5.0 > packages built (eaccess problems), and 5 of them blew up in about 10 > minutes with this (I think this is going to be an .. uh .. interesting > test of the stability of 5.0-CURRENT): > > IdlePTD at phsyical address 0x004a6000 > initial pcb at physical address 0x003e9040 > panicstr: bwrite: buffer is not busy??? > panic messages: > --- > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x58 > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc0204b92 > stack pointer = 0x10:0xcf0fac2c > frame pointer = 0x10:0xcf0fac34 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 10095 (umount) > trap number = 12 > panic: page fault As Peter pointed out to me, this is the actual panic; the "bwrite: buffer is not busy???" is spurious and caused by the kernel trying to sync after the first panic. All of the problems I'm currently seeing are in umount. Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8lQsyWry0BWjoQKURAvnZAKDUgxQiB5LyMkf+ceuPAsgMkemhiwCfQY8e lxFGIk6Cnkrh8c+8CzeM5iw= =qDjz -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020317133130.A35137>