Date: Sat, 13 Jul 2002 04:34:20 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: current@freebsd.org Subject: Re: bdwrite: buffer is not busy Message-ID: <20020713003419.GA3548@nagual.pp.ru> In-Reply-To: <200207122218.aa20866@salmon.maths.tcd.ie> References: <20020712182534.GA336@nagual.pp.ru> <200207122218.aa20866@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 12, 2002 at 22:18:35 +0100, Ian Dowse wrote: > In message <20020712182534.GA336@nagual.pp.ru>, "Andrey A. Chernov" writes: > >I see this panic constantly during last month or two, UP machine, no > >softupdates. Anybody else saw it too? Any ideas? > > The "buffer is not busy" panic is usually a secondary panic that > occurs while trying to sync the disks after a different panic. If > possible, try to get the first panic message, or ideally a stack > trace. This is remote machine, all I can see is savecore info in /var/crash. BTW, can we "fix" it in simple way, i.e. always disallow second panic dump just checking panic flag? -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020713003419.GA3548>