From: Chuck <chunkeey@web.de>
To: Marcin Dalecki <martin@dalecki.de>
Subject: Re: How's the nforce4 support in Linux?
Date: Sun, 27 Mar 2005 14:26:14 +0200
User-Agent: KMail/1.7.2
Cc: Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
References: <200503261701.08774.chunkeey@web.de> <1111850358.8042.34.camel@laptopd505.fenrus.org> <bf8a98cafc4141c67d3b4cabfde65ed2@dalecki.de>
In-Reply-To: <bf8a98cafc4141c67d3b4cabfde65ed2@dalecki.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200503271426.14670.chunkeey@web.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1044
Lines: 25

On Saturday, 26. March 2005 18:32, Marcin Dalecki wrote:
> On 2005-03-26, at 16:19, Arjan van de Ven wrote:
> > `
> >
> >> hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> >> hda: dma_intr: error=0x84 { DriveStatusError BadCRC
> >
> > BadCRC is 99% sure a cabling issue; either a bad/overheated cable or a
> > cable used at too high a speed for the cable.
>
> No. It is more likely that the timing programming between the disk and
> host controller
> are in a miss-match state. UDMA mode detection can come in to mind too.
> It makes sense to experiment with hdparm to see if the problem goes
> away in non
> Ultra DMA modes.

Thanks, I tried the cable that came with the drive  (it was still sealed) and 
experimented a little bit with hdparm...
Now, the problem seems to be gone...  
-
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/