Giant deadlock related to twe
Doug White
dwhite at gumbysoft.com
Thu Aug 26 11:07:59 PDT 2004
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 at gumbysoft.com | www.FreeBSD.org
More information about the freebsd-current
mailing list