linux-kernel - 2.6.19-rc2 - Cable detection problem in pata

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Oct 2006 18:29:43 -0500
From:	Walt H <walt_h@...ettotel.net>
To:	linux-kernel <linux-kernel@...r.kernel.org>
CC:	linux-ide@...r.kernel.org
Subject: 2.6.19-rc2 - Cable detection problem in pata_amd

OK, I just realized this isn't specifically related to 2.6.19-rc2 as
it's been around since 2.6.16 w/ Alan's PATA patches for me. I'm
currently running 2.6.17-ck kernel due to a couple hard-locks I
experienced in 2.6.19-rc2, which I haven't yet had time to mess with.

On bootup, the pata_amd driver mis-detects the cable connected to the
2nd port on my system as 40 wire and sets UDMA/33 for this drive. Prior
to using the libata patches, the system did correctly setup this drive
for UDMA/100.  The cable is a standard 80 conductor, flat IDE cable.
I've tried switching the cables around to see if it truly was a cable
issue, but it makes no difference.  The 2nd port always gets detected as
a non-80-wire cable.

For kicks, I commented out the ap->cbl = ATA_CBL_PATA40 definition in
pata_amd.c and set it to ATA_CBL_PATA80 and it's been running fine for
~24 hrs (2.6.17-ck).

Any ideas?

dmesg, lspci & config follows:

View attachment "dmesg.txt" of type "text/plain" (19661 bytes)

View attachment "lspci.txt" of type "text/plain" (11803 bytes)

View attachment "config" of type "text/plain" (38074 bytes)