From owner-freebsd-bugs@FreeBSD.ORG  Tue Mar 20 12:28:21 2007
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
X-Original-To: freebsd-bugs@hub.freebsd.org
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 84B8C16A404;
	Tue, 20 Mar 2007 12:28:21 +0000 (UTC)
	(envelope-from remko@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40])
	by mx1.freebsd.org (Postfix) with ESMTP id 5EA7B13C45A;
	Tue, 20 Mar 2007 12:28:21 +0000 (UTC)
	(envelope-from remko@FreeBSD.org)
Received: from freefall.freebsd.org (remko@localhost [127.0.0.1])
	by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l2KCSLol080173;
	Tue, 20 Mar 2007 12:28:21 GMT
	(envelope-from remko@freefall.freebsd.org)
Received: (from remko@localhost)
	by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l2KCSKqU080169;
	Tue, 20 Mar 2007 12:28:20 GMT (envelope-from remko)
Date: Tue, 20 Mar 2007 12:28:20 GMT
From: Remko Lodder <remko@FreeBSD.org>
Message-Id: <200703201228.l2KCSKqU080169@freefall.freebsd.org>
To: robert@mpe.mpg.de, remko@FreeBSD.org, freebsd-bugs@FreeBSD.org
Cc: 
Subject: Re: kern/61669: [twe] writing to 3ware escalade spends 90% of cpu
	in system.
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2007 12:28:21 -0000

Synopsis: [twe] writing to 3ware escalade spends 90% of cpu in system.

State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Tue Mar 20 12:28:03 UTC 2007
State-Changed-Why: 
Harrison reports that a firmware update resolved this issue.

http://www.freebsd.org/cgi/query-pr.cgi?pr=61669