Date: Wed, 28 Feb 2007 16:55:32 -0500 (EST)
From: Gerhard Mack <gmack@innerfire.net>
To: Charles Shannon Hendrix <shannon@widomaker.com>
cc: linux-kernel@vger.kernel.org
Subject: solved Re: 2.6.20 SATA error
In-Reply-To: <20070228163204.16c21f29@daydream.goid.lan>
Message-ID: <Pine.LNX.4.64.0702281649590.5096@mtl.rackplans.net>
References: <Pine.LNX.4.64.0702280739510.21113@mtl.rackplans.net>
 <20070228111412.4d8a2d72@daydream.goid.lan> <Pine.LNX.4.64.0702281220510.12067@mtl.rackplans.net>
 <20070228163204.16c21f29@daydream.goid.lan>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1249
Lines: 37

On Wed, 28 Feb 2007, Charles Shannon Hendrix wrote:

> On Wed, 28 Feb 2007 13:25:00 -0500 (EST)
> Gerhard Mack <gmack@innerfire.net> wrote:
> 
>  
> > > In another thread, I think they were saying it was either a SATA chipset
> > > driver bug, or a problem in libata core.
> > 
> > I also have an nforce4.
> 
> On another mailing list, someone with an Intel chipset is reporting the same
> problem, and also that others without nforce chipsets are seeing it.

I was reaching inside my computer to check something and heared the thing 
click and got the same error message.

Turns out the adaptor that goes between SATA drive and the old style power 
connector was loose on the drive side.  Doesn't seem to me like it was 
very snug fitting to begin with.  I changed it to one of the proper SATA 
connectors comming off the power supply and it doesn't do that anymore.

Sorry for the false alarm, 

	Gerhard

--
Gerhard Mack

gmack@innerfire.net

<>< As a computer I find your faith in technology amusing.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/