| 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
| ||
|
Message-ID: <20090603131407.57c490ed@lxorguk.ukuu.org.uk> Date: Wed, 3 Jun 2009 13:14:07 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Grozdan <neutrino8@...il.com> Cc: Robert Hancock <hancockrwd@...il.com>, linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org Subject: Re: Kernel 2.6.30rc7 limits IDE to UDMA33 > ACPI: PCI Interrupt Link [ALKA] disabled and referenced, BIOS bug > ACPI: PCI Interrupt Link [ALKA] enabled at IRQ 20 > pata_via 0000:00:0f.0: PCI INT A -> Link[ALKA] -> GSI 20 (level, low) -> IRQ 20 > scsi0 : pata_via > scsi1 : pata_via > ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xdc00 irq 14 > ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xdc08 irq 15 > ata1.00: ATA-7: Maxtor 6Y080L0, YAR41BW0, max UDMA/133 > ata1.00: 160086528 sectors, multi 16: LBA > ata1.01: ATA-5: ST340016A, 3.10, max UDMA/100 > ata1.01: 78165360 sectors, multi 16: LBA > ata1.00: limited to UDMA/33 due to 40-wire cable > ata1.01: limited to UDMA/33 due to 40-wire cable The via driver hasn't changed its cable detect handling between 2.6.27 and now. The actual detection is done by the BIOS either by setting flags or via ACPI. To trace it down I'd need to at minimum to know exactly which kernel the behaviour you see changed. -- 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/
Powered by blists - more mailing lists