2.6.14-rc4-mm1 and later: second ata_piix controller is invisible

From: Max Kellermann (max_at_duempel.org)
Date: 10/25/05

  • Next message: David Howells: "Re: [PATCH] Add notification of page becoming writable to VMA ops" 
    Date:	Tue, 25 Oct 2005 11:56:46 +0200
To: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>

    Hi Andrew,

    since 2.6.14-rc4-mm1, my second ata_piix (SATA) controller does not
    show up in dmesg, effectively hiding /dev/sdb. 2.6.14-rc2-mm2 and
    older (with the same kernel config) were ok, the same for Linus'
    kernels: 2.6.14-rc5 without -mm1 has /dev/sdb, too.

    0000:00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150
    Storage Controller (rev 02) (prog-if 8f [Master SecP SecO PriP PriO])
    0000:00:1f.2 0101: 8086:24d1 (rev 02)

    This PCI device (on-board on an Asus P4 mainboard) has two SATA
    connectors, showing up as ata1/sda and ata2/sdb.

    dmesg from 2.6.14-rc5:

    libata version 1.12 loaded.
    ata_piix version 1.04
    ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 177
    PCI: Setting latency timer of device 0000:00:1f.2 to 64
    ata1: SATA max UDMA/133 cmd 0xEFE0 ctl 0xEFAE bmdma 0xEF60 irq 177
    ata2: SATA max UDMA/133 cmd 0xEFA0 ctl 0xEFAA bmdma 0xEF68 irq 177
    ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01
    87:4003 88:207f
    ata1: dev 0 ATA, max UDMA/133, 240121728 sectors:
    ata1: dev 0 configured for UDMA/133

    dmesg from 2.6.14-rc5-mm1:

    libata version 1.12 loaded.
    ata_piix version 1.04
    ACPI: PCI Interrupt 0000:00:1f.2[A] -> GSI 18 (level, low) -> IRQ 193
    PCI: Setting latency timer of device 0000:00:1f.2 to 64
    ata1: SATA max UDMA/133 cmd 0xEFE0 ctl 0xEFAE bmdma 0xEF60 irq 193
    ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01
    87:4003 88:207f
    ata1: dev 0 ATA-7, max UDMA/133, 240121728 sectors: LBA
    ata1: dev 0 configured for UDMA/133

    Need more information? I could try to disable a few patches from your
    -mm series if you name some.. it's too hard for me to guess which one
    could be responsible for the breakage.

    Max

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

  • Next message: David Howells: "Re: [PATCH] Add notification of page becoming writable to VMA ops"

    Relevant Pages