From owner-freebsd-stable@FreeBSD.ORG Mon Nov 13 22:16:48 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5333A16A525 for ; Mon, 13 Nov 2006 22:16:48 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2B4843DE3 for ; Mon, 13 Nov 2006 22:15:32 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Mon, 13 Nov 2006 17:15:31 -0500 id 00056414.4558EE83.0000143D Received: from Internal Mail-Server by mx01 (envelope-from wmoran@collaborativefusion.com) with AES256-SHA encrypted SMTP; 13 Nov 2006 17:15:29 -0500 Date: Mon, 13 Nov 2006 17:15:29 -0500 From: Bill Moran To: stable@freebsd.org Message-Id: <20061113171529.a75fe20a.wmoran@collaborativefusion.com> Organization: Collaborative Fusion X-Mailer: Sylpheed version 2.2.9 (GTK+ 2.10.6; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: em interrupt storm X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Nov 2006 22:16:48 -0000 Just experienced an "interrupt storm" on an em device that disabled a server until I could reboot it. My initial research turned up this thread: http://lists.freebsd.org/pipermail/freebsd-current/2005-November/058336.html Which seems related, even if it is a little old. I'm aware that there have been problems with recent versions of the em driver but I haven't been following them closely enough, and there's a LOT of mail traffic on this topic. Note that this is a FreeBSD 5.3-RELEASE-p37 system. An upgrade is possible, but this is a production system and the problem occurs infrequently, so I'm reluctant to schedule downtime unless I have good reason to believe that it will fix the problem. Anyone remember if the above problem was fixed in more recent versions, or knows enough about the issue to comment on whether I'm barking up the correct tree or not? I'm pretty early in the diagnosis on this, but I'm looking for pointers to keep me from doing random upgrades or other time-wasting activities. -- Bill Moran Collaborative Fusion Inc. wmoran@collaborativefusion.com Phone: 412-422-3463x4023 **************************************************************** IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. **************************************************************** IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.