From owner-freebsd-current@FreeBSD.ORG Tue Aug 24 00:42:31 2004 Return-Path: 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 27BC716A4CE for ; Tue, 24 Aug 2004 00:42:31 +0000 (GMT) Received: from hadar.amcc.com (hadar.amcc.com [192.195.69.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE2E043D4C for ; Tue, 24 Aug 2004 00:42:30 +0000 (GMT) (envelope-from vkashyap@amcc.com) Received: from mailhost02.amcc.com ([192.195.69.49]) by hadar.amcc.com (Netscape Messaging Server 4.15) with SMTP id I2XDYX00.K21; Mon, 23 Aug 2004 17:42:33 -0700 Received: (from vkashyap-pc [10.66.6.61]) by mailhost02.amcc.com (SMSSMTP 4.0.0.59) with SMTP id M2004082317423730199 ; Mon, 23 Aug 2004 17:42:37 -0700 From: "Vinod Kashyap" To: Doug White , current@freebsd.org Date: Mon, 23 Aug 2004 17:42:28 -0700 X-Sent-Folder-Path: Sent Items X-Mailer: Oracle Connector for Outlook 9.0.4 51114 (9.0.6627) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-ID: X-Mailman-Approved-At: Tue, 24 Aug 2004 11:45:50 +0000 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Aug 2004 00:42:31 -0000 > -----Original Message----- > From: owner-freebsd-current@freebsd.org > [mailto:owner-freebsd-current@freebsd.org]On Behalf Of Doug White > Sent: Sunday, August 22, 2004 3:33 PM > To: current@freebsd.org > Subject: Giant deadlock related to twe > = > = > Hey folks, > = > 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: > > twed0: controller error - device failure (flags =3D 0x80) > twed0: controller error - device failure (flags =3D 0x80) > twed0: controller error - device failure (flags =3D 0x80) > twed0: controller error - device failure (flags =3D 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.