From owner-freebsd-current@FreeBSD.ORG Sun Feb 20 15:47:01 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FCC41065673 for ; Sun, 20 Feb 2011 15:47:01 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 0E35B8FC1C for ; Sun, 20 Feb 2011 15:47:00 +0000 (UTC) Received: from omta18.emeryville.ca.mail.comcast.net ([76.96.30.74]) by qmta06.emeryville.ca.mail.comcast.net with comcast id AFiJ1g0011bwxycA6Fn0fS; Sun, 20 Feb 2011 15:47:00 +0000 Received: from koitsu.dyndns.org ([98.248.33.18]) by omta18.emeryville.ca.mail.comcast.net with comcast id AFmr1g01h0PUQVN8eFmvB1; Sun, 20 Feb 2011 15:46:58 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 3B7109B422; Sun, 20 Feb 2011 07:46:51 -0800 (PST) Date: Sun, 20 Feb 2011 07:46:51 -0800 From: Jeremy Chadwick To: Mike Tancsa Message-ID: <20110220154651.GA17661@icarus.home.lan> References: <4D4A38FD.7000607@rdtc.ru> <4D3011DB.9050900@frasunek.com> <4FD1B1C3-08A7-4F48-A30A-DE5A8F3D3834@averesystems.com> <4D6133AC.6070507@sentex.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4D6133AC.6070507@sentex.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Mailman-Approved-At: Sun, 20 Feb 2011 16:21:13 +0000 Cc: freebsd-stable@freebsd.org, freebsd-current@freebsd.org, Andrey Smagin , Eugene Grosbein , Andrew Boyer Subject: Re: About "panic: bufwrite: buffer is not busy???" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Feb 2011 15:47:01 -0000 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. > > The latest panic I saw didnt have anything to do with em. Are 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(). So, that would be some kind of weird filesystem-related issue, not NIC-specific. I have no idea how to debug said problem. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB |