From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lee Revell Subject: Re: Linux v2.6.16-rc6 Date: Sun, 12 Mar 2006 16:46:10 -0500 Message-ID: <1142199970.25358.173.camel@mindpipe> References: <1142189154.21274.20.camel@blaze.homeip.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: Received: from mustang.oldcity.dca.net ([216.158.38.3]:13030 "HELO mustang.oldcity.dca.net") by vger.kernel.org with SMTP id S1751689AbWCLVqP (ORCPT ); Sun, 12 Mar 2006 16:46:15 -0500 In-Reply-To: <1142189154.21274.20.camel@blaze.homeip.net> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Paul Blazejowski Cc: LKML , linux-ide@vger.kernel.org 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