Date: Mon, 23 Aug 2004 17:42:28 -0700 From: "Vinod Kashyap" <vkashyap@amcc.com> To: Doug White <dwhite@gumbysoft.com>, current@freebsd.org Subject: RE: Giant deadlock related to twe Message-ID: <I2XDYX00.K21@hadar.amcc.com>
next in thread | raw e-mail | index | archive | help
> -----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: > <twe0: drive timeout for unknown unit 1> > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?I2XDYX00.K21>