From owner-freebsd-stable@FreeBSD.ORG Thu Sep 28 20:07:00 2006 Return-Path: X-Original-To: freebsd-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 1C7E516A416 for ; Thu, 28 Sep 2006 20:07:00 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99B2D43DED for ; Thu, 28 Sep 2006 20:06:27 +0000 (GMT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate1.punkt.de with ESMTP id k8SK6QF0009686 for ; Thu, 28 Sep 2006 22:06:26 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id k8SK6Pa9035301; Thu, 28 Sep 2006 22:06:25 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id k8SK6PfG035300; Thu, 28 Sep 2006 22:06:25 +0200 (CEST) (envelope-from ry93) Date: Thu, 28 Sep 2006 22:06:25 +0200 From: "Patrick M. Hausen" To: Alan Amesbury Message-ID: <20060928200625.GB34886@hugo10.ka.punkt.de> References: <20060927215554.C059316A601@hub.freebsd.org> <451C26BD.2090807@umn.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <451C26BD.2090807@umn.edu> User-Agent: Mutt/1.5.10i Cc: freebsd-stable@freebsd.org Subject: Re: 6.2 SHOWSTOPPER - em completely unusable on 6.2 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: Thu, 28 Sep 2006 20:07:00 -0000 Hi! On Thu, Sep 28, 2006 at 02:47:09PM -0500, Alan Amesbury wrote: > Additional data point: On 6.1-RELEASE I've observed the same sort of > behavior, but without any noticeable consistency. It affects bge(4) and > em(4) systems. In the case of the bge(4)-equipped system, there's a > very weak correlation between heavy disk activity and watchdog timeouts. > However, on that system, it doesn't look like the network card shares > its PCI bus and interrupt with any other devices: Same here, just to make sure to get that point through: em doesn't share an interrupt with anything else -> hang will occur sooner or later if the system is busy (sometimes later, but reproducably) force system to share interrupt of, say, ata0 and em0 -> immediate *kaboom* whenever both are busy HTH, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de