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, 20 Jul 2007 16:02:01 +0200
From:	Gabriel C <nix.or.die@...glemail.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Felipe Contreras <felipe.contreras@...il.com>,
	lkml <linux-kernel@...r.kernel.org>,
	Jeff Garzik <jeff@...zik.org>
Subject: Re: ata_piix broken in 2.6.22

Alan Cox wrote:
> O> ata_piix 0000:00:1f.2: version 2.11
>> ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
>> ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 16 (level, low) -> IRQ 16
>> ata_piix 0000:00:1f.2: 0x1F0 IDE port busy
>> ata_piix 0000:00:1f.2: 0x170 IDE port busy
>> ata_piix 0000:00:1f.2: no available legacy port
> 
> You appear to have old IDE compiled in as well and finding the device
> first

Alan ,

But this is allowed now and for me, after removing CONFIG_SATA_INTEL_COMBINED option
some other options combos may be illegal and removing it broke a lot working setups.

On <2.6.22 you got on your SATA/PATA controller with CONFIG_IDE=y , ATA=y ( ATA_X=y and even BLK_DEV_X=y) the

SATA disk as SATA and PATA one as IDE now you get the SATA disk as 'IDE' too which gives you almost 3-4MB/s speed.

Is such a config legall for you for an SATA/IDE combo controller in >=2.6.22 ?

CONFIG_BLK_DEV_IDE_SATA=n
CONFIG_IDE=y
ATA=y
BLK_DEV_PIIX=y(or m doesn't matter )
ATA_PIIX=y

IMO after removing CONFIG_SATA_INTEL_COMBINED you guys introduced an real conflict with the IDE subsystem.

The only way to get libata working with such a config is to boot ideX=noprobe.


Regards,

Gabriel
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ