Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Jul 2002 18:26:59 -0700
From:      Darren Pilgrim <dmp@pantherdragon.org>
To:        Ian Dowse <iedowse@maths.tcd.ie>
Cc:        stable@FreeBSD.org
Subject:   Re: READ_BIG problems
Message-ID:  <3D41F6E3.D9E3BFA0@pantherdragon.org>
References:  <200207252206.aa43155@salmon.maths.tcd.ie>

next in thread | previous in thread | raw e-mail | index | archive | help
Ian Dowse wrote: 
> In message <3D406319.1136A6EA@iae.nl>, Hans Ottevanger writes:
> >acd0: READ_BIG command timeout - resetting
> >ata1: resetting devices .. done
> >acd0: READ_BIG command timeout - resetting
> >ata1: resetting devices .. done
> 
> Could people seeing this and other ATA problems try the patch below?
> This should fix some unlikely races that could potentially be
> responsible for these problems, though I suspect it will not make
> any difference.

Is there a specific problem with certain drives (meaning certain
interface logic or drive mechanisms), or is this another one of
those, "This is why you shouldn't use El Cheapo hardware with a
real OS," deals?

I was having the same READ_BIG timeout errors with a generic 50x
drive.  Replacing the drive with a decent drive (Toshiba XM-6402B)
fixed the problem.  I can put the 50x drive back in if you want
another tester for the patch, btw.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3D41F6E3.D9E3BFA0>