Messages in this thread | | | Date | Fri, 20 Jul 2007 17:04:03 +0300 | From | "Felipe Contreras" <> | Subject | Re: ata_piix broken in 2.6.22 |
| |
On 7/20/07, Gabriel C <nix.or.die@googlemail.com> wrote: > Felipe Contreras wrote: > > Hi, > > Hi , > > > > > Since I updated to 2.6.22 everything has been slower and I think this > > is the reason: > > > > 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 > > > > I tried to apply the patch d583bc18812f8da52bf25eef9cd111e5fd46a6ab, > > but I get a similar error: > > > > 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 > > PCI: Unable to reserve I/O region #1:8@1f0 for device 0000:00:1f.2 > > ata_piix 0000:00:1f.2: failed to request/iomap BARs for port 0 (errno=-16) > > PCI: Unable to reserve I/O region #3:8@170 for device 0000:00:1f.2 > > ata_piix 0000:00:1f.2: failed to request/iomap BARs for port 1 (errno=-16) > > ata_piix 0000:00:1f.2: no available native port > > > > I think I'm not the only one with that problem: > > http://www.dellcommunity.com/supportforums/board/message?board.id=sw_linux&thread.id=10825 > > > > Any hints? > > > > Guessing you are using and SATA/PATA controller ? > > Combined mode got removed in 2.6.22 and depending on your config things will break. > > As example CONFIG_IDE=y BLK_DEV_PIIX=y , ATA=y , ATA_PIIX=Y worked in <2.6.22 but won't on .22. > > If you want to use libata try to boot with ideX=noprobe ideY=noprobe
Oh, that's it!
I tried CONFIG_IDE=n and now ata_piix is working just fine.
Would a note in CONFIG_ATA be pertinent? Or did I miss some piece of documentation?
Thanks.
-- Felipe Contreras - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |