From owner-freebsd-current@FreeBSD.ORG  Thu Aug 26 18:07:58 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DE99316A4CF
	for <current@freebsd.org>; Thu, 26 Aug 2004 18:07:58 +0000 (GMT)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CC11743D5D
	for <current@freebsd.org>; Thu, 26 Aug 2004 18:07:58 +0000 (GMT)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id BE5B072DD5; Thu, 26 Aug 2004 11:07:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP id BC83A72DD4;
	Thu, 26 Aug 2004 11:07:58 -0700 (PDT)
Date: Thu, 26 Aug 2004 11:07:58 -0700 (PDT)
From: Doug White <dwhite@gumbysoft.com>
To: Vinod Kashyap <vkashyap@amcc.com>
In-Reply-To: <I2XDYX00.K21@hadar.amcc.com>
Message-ID: <20040826110701.L37301@carver.gumbysoft.com>
References: <I2XDYX00.K21@hadar.amcc.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: current@freebsd.org
Subject: RE: Giant deadlock related to twe
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Aug 2004 18:07:59 -0000

On Mon, 23 Aug 2004, Vinod Kashyap wrote:

> > Just got this on my amd64 box. A disk flaked out in my
> > machine, which has
> > a 3ware 8006-2LP with 2 80GB drives in a RAID0.  My X session
> > locked up
> > and was able to break to ddb.  Some ddb twiddling follows.
> > It looks like,
> > at first glance, some sort of deadlock against softupdates.
> >
> > twed0: drive timeouttwed0: drive timeouttwed0: drive
> > timeouttwed0: drive
> > timeout
> > twed0: drive timeouttwed0: drive timeouttwed0: drive timeouttwe0: AEN:
> > <twe0: drive timeout for unknown unit 1>
> > twed0: controller error - device failure (flags = 0x80)
> > twed0: controller error - device failure (flags = 0x80)
> > twed0: controller error - device failure (flags = 0x80)
> > twed0: controller error - device failure (flags = 0x80)
>
> The messages indicate timeouts due to the drive continuously returning
> BUSY to the firmware on the controller.  This could be caused by the
> the drive going bad, or even a one time disturbance like tugging of
> cables, etc.

Right, and a failing drive it was, but it shouldn't lock up the entire
system when it happens.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org