Subject: Re: Linux v2.6.16-rc6
From: Lee Revell <rlrevell@joe-job.com>
To: Paul Blazejowski <paulb@blazebox.homeip.net>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
In-Reply-To: <1142189154.21274.20.camel@blaze.homeip.net>
References: <1142189154.21274.20.camel@blaze.homeip.net>
Content-Type: text/plain
Date: Sun, 12 Mar 2006 16:46:10 -0500
Message-Id: <1142199970.25358.173.camel@mindpipe>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1120
Lines: 31

On Sun, 2006-03-12 at 13:45 -0500, Paul Blazejowski wrote:
> On recent kernel 2.6.15.6 (or any 2.6.15.x) and latest testing
> 2.6.16-rc6 libata detects and sets wrong UDMA modes for one of the
> SATA-1 drives. This seems to be a bug.
> 
> My setup is as follows:
> 
> ASUS A8N-SLI-Premium Nforce4 mainboard
> AMD Athlon X2 CPU running SMP
> GCC 3.3.6
> Slackware 10.2 Linux
> 
> The drives are used in RAID1 array (dmraid), they are WDC-WD2000JD
> series purchased few months apart. Sata is compiled in the kernel as
> module sata_nv and functions properly, no errors or any other anomalies
> were noticed but the UDMA mode detection seem wrong on the second drive.
> 
> Drive one reports ata3: dev 0 configured for UDMA/100 while drive two
> ata4: dev 0 configured for UDMA/133

This bug report is still somewhat unclear.

What are the correct modes you expect to see?

Lee

-
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/