linux-kernel - Re: libata limiting to UDMA/33 instead of UDMA/100

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

Message-ID: <20070610170810.71677857@the-village.bc.nu>
Date:	Sun, 10 Jun 2007 17:08:10 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Udo A. Steinberg" <us15@...inf.tu-dresden.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: libata limiting to UDMA/33 instead of UDMA/100

On Sat, 9 Jun 2007 13:21:24 +0200
"Udo A. Steinberg" <us15@...inf.tu-dresden.de> wrote:

> Hi,
> 
> After switching an older machine over from the PDC20265 PATA driver to the
> libata driver pata_pdc202xx_old my HDDs are now limited to UDMA/33. With the
> old driver they were happily running with UDMA/100.

...

> 
> I'm including the relevant kernel output for both cases below.

Thanks.

> scsi0 : pata_pdc202xx_old
> scsi1 : pata_pdc202xx_old
> ata1: PATA max UDMA/100 cmd 0x00019400 ctl 0x00019002 bmdma 0x00018000 irq 0
> ata2: PATA max UDMA/100 cmd 0x00018800 ctl 0x00018402 bmdma 0x00018008 irq 0
> ata1.00: ata_hpa_resize 1: sectors = 60036480, hpa_sectors = 60036480
> ata1.00: ATA-5: IBM-DTLA-307030, TX4OA5AA, max UDMA/100
> ata1.00: 60036480 sectors, multi 16: LBA 
> ata1.01: ata_hpa_resize 1: sectors = 241254720, hpa_sectors = 241254720
> ata1.01: ATA-6: IC35L120AVV207-0, V24OA63A, max UDMA/100
> ata1.01: 241254720 sectors, multi 16: LBA48 
> ata1.00: limited to UDMA/33 due to 40-wire cable
> ata1.01: limited to UDMA/33 due to 40-wire cable

What sort of cable is actually in use here ?

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/