Date: Tue, 8 Mar 2011 11:59:30 -0800 From: Freddie Cash <fjwcash@gmail.com> To: Jeremy Chadwick <freebsd@jdc.parodius.com> Cc: Andrey Smagin <samspeed@mail.ru>, Eugene Grosbein <egrosbein@rdtc.ru>, Andrew Boyer <aboyer@averesystems.com>, Mike Tancsa <mike@sentex.net>, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: About "panic: bufwrite: buffer is not busy???" Message-ID: <AANLkTimT4gQLgc0=kNL1V%2BQZSpP-JN0KE_MtMJV-_e-o@mail.gmail.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
Not sure if the CC: line needs to be trimmed, leaving it as is for now. On Sun, Feb 20, 2011 at 7:46 AM, Jeremy Chadwick <freebsd@jdc.parodius.com> 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 wi= th another re interface interated on MB. I think it may be em related panic= , or em+mpd5. >> >> The latest panic I saw didnt have anything to do with em. =C2=A0Are you = sure >> your crashes are because of the nic drive ? > > 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(). =C2=A0So, that would be some kind of weird filesystem-rel= ated > issue, not NIC-specific. =C2=A0I have no idea how to debug said problem. I can semi-reliably reproduce this panic message on a 9-CURRENT box, with sources from March 7. On this box, it happens every other time I start hastd. hastd creates the 12 GEOM providers used to create a ZFS pool. A simple "service hastd onestart" will generate the panic. Is there any extra info that needed to help track this down? --=20 Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimT4gQLgc0=kNL1V%2BQZSpP-JN0KE_MtMJV-_e-o>