Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 20 Feb 2011 10:55:34 -0500
From:      Andrew Boyer <aboyer@averesystems.com>
To:        freebsd-current@freebsd.org, freebsd-stable@freebsd.org
Cc:        Andrey Smagin <samspeed@mail.ru>, Eugene Grosbein <egrosbein@rdtc.ru>, Jeremy Chadwick <freebsd@jdc.parodius.com>, Mike Tancsa <mike@sentex.net>
Subject:   Re: About "panic: bufwrite: buffer is not busy???"
Message-ID:  <B141F65F-FCFB-4DF1-B4B8-1C85B088A47F@averesystems.com>
In-Reply-To: <20110220154651.GA17661@icarus.home.lan>
References:  <4D4A38FD.7000607@rdtc.ru> <4D3011DB.9050900@frasunek.com> <4FD1B1C3-08A7-4F48-A30A-DE5A8F3D3834@averesystems.com> <E1PrAM9-0001fN-00.samspeed-mail-ru@f30.mail.ru> <4D6133AC.6070507@sentex.net> <20110220154651.GA17661@icarus.home.lan>

next in thread | previous in thread | raw e-mail | index | archive | help

On Feb 20, 2011, at 10:46 AM, Jeremy Chadwick wrote:

> On Sun, Feb 20, 2011 at 10:30:52AM -0500, Mike Tancsa wrote:
>> On 2/20/2011 9:33 AM, Andrey Smagin wrote:
>>> On week -current I have same problem, my box paniced every 2-15 min. =
I resolve problem by next steps - unplug network connectors from 2 intel =
em (82574L) cards. I think last time that mpd5 related panic, but mpd5 =
work with another re interface interated on MB. I think it may be em =
related panic, or em+mpd5.
>>=20
>> The latest panic I saw didnt have anything to do with em.  Are you =
sure
>> your crashes are because of the nic drive ?
>=20
> Not to mention, the error string the OP provided (see Subject) is only
> contained in one file: sys/ufs/ffs/ffs_vfsops.c, function
> ffs_bufwrite().  So, that would be some kind of weird =
filesystem-related
> issue, not NIC-specific.  I have no idea how to debug said problem.
>=20

The issue is the file system activity occurring in parallel with the =
coredump, which is strange.  It seems like everything else should be =
halted before the dump begins but I couldn't find a place in the code =
that actually tries to stop the other CPUs.

My question isn't about the initial panic (I was using the sysctl to =
provoke one), but about the secondary panic.

This is on 8-core systems.

-Andrew

--------------------------------------------------
Andrew Boyer	aboyer@averesystems.com







Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B141F65F-FCFB-4DF1-B4B8-1C85B088A47F>