From owner-freebsd-current@FreeBSD.ORG Sun Feb 20 15:55:38 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 566A2106564A; Sun, 20 Feb 2011 15:55:38 +0000 (UTC) (envelope-from aboyer@averesystems.com) Received: from zimbra.averesystems.com (75-149-8-245-Pennsylvania.hfc.comcastbusiness.net [75.149.8.245]) by mx1.freebsd.org (Postfix) with ESMTP id 0CD768FC0A; Sun, 20 Feb 2011 15:55:37 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zimbra.averesystems.com (Postfix) with ESMTP id 2232C44A005; Sun, 20 Feb 2011 10:54:44 -0500 (EST) X-Virus-Scanned: amavisd-new at averesystems.com Received: from zimbra.averesystems.com ([127.0.0.1]) by localhost (zimbra.averesystems.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n2TsV5VszDrj; Sun, 20 Feb 2011 10:54:41 -0500 (EST) Received: from [192.168.4.6] (c-24-131-84-46.hsd1.pa.comcast.net [24.131.84.46]) by zimbra.averesystems.com (Postfix) with ESMTPSA id 8CE5844A004; Sun, 20 Feb 2011 10:54:41 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v1082) From: Andrew Boyer In-Reply-To: <20110220154651.GA17661@icarus.home.lan> Date: Sun, 20 Feb 2011 10:55:34 -0500 Message-Id: References: <4D4A38FD.7000607@rdtc.ru> <4D3011DB.9050900@frasunek.com> <4FD1B1C3-08A7-4F48-A30A-DE5A8F3D3834@averesystems.com> <4D6133AC.6070507@sentex.net> <20110220154651.GA17661@icarus.home.lan> To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.1082) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Andrey Smagin , Eugene Grosbein , Jeremy Chadwick , Mike Tancsa 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:55:38 -0000 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