linux-kernel - Re: pata_via appears to incorrectly detects 40-pin cable

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 May 2007 01:39:55 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Francis Russell <francisrussell@...penworld.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: pata_via appears to incorrectly detects 40-pin cable

On Thu, 17 May 2007 19:01:43 +0000 (GMT)
Francis Russell <francisrussell@...penworld.com> wrote:

> I'm testing Linux kernel version 2.6.22-rc1 using Debian Testing on an Acer Ferrari 3400 Laptop. This has a VIA IDE controller with the internal HDD and DVD writer attached. The via_pata module and SCSI disk support is compiled into the kernel and the old ATA subsystem is not. At bootup the log messages state that the main HDD is detected as being connected using a 40-pin cable which causes its speed to be limited to UDMA33 rather then UDMA100, the limit of the HD.  This works fine under the old ATA system.

The old drivers won't bother to tell you if they are limiting to UDMA33,
but they do also contain some BIOS mode snooping hacks which are unsafe
for hotplug, suspend/resume etc and libata doesn't use.

Does the laptop actually have 80 wire cables - did you see UDMA100
actually being used. If so can you send me an lspci -vxx and a dmesg.
Probably we need to add it to the list of devices using short 40 wire
cable tricks.

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/