Re: OOPS with 2.6.21rc2-git (ata: conflict with ide0/1)

[Jeff Garzik]

Tejun Heo wrote:
> [cc'ing Greg, Hi]
>
> Kok, Auke wrote:
> > Attached dmesg. config.gz. here's the OOPS part.
> >
> > ata_piix 0000:00:1f.2: version 2.10
> > ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
> > ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
> > ata: 0x1F0 IDE port busy
> > ata: conflict with ide0
> > BUG: at drivers/pci/pci.c:846 pcim_pin_device()
> >  [<c023838c>] pcim_pin_device+0x4c/0x60
> >  [<c0371af6>] ata_pci_init_one+0x2d6/0x380
> >  [<c023b968>] pci_get_device+0x18/0x20
> >  [<c0378651>] piix_check_450nx_errata+0x31/0x110
> >  [<c0238b90>] pci_intx+0x20/0x90
> >  [<c0378a97>] piix_init_one+0x117/0x200
> >  [<c023afca>] pci_call_probe+0xa/0x10
> >  [<c023b01e>] __pci_device_probe+0x4e/0x60
> >  [<c023b056>] pci_device_probe+0x26/0x60
> >  [<c0295a94>] really_probe+0xb4/0x170
> >  [<c023afa8>] pci_match_device+0xa8/0xc0
> >  [<c0295c28>] driver_probe_device+0xc8/0xd0
> >  [<c0465521>] klist_next+0x61/0xc0
> >  [<c0295d30>] __driver_attach+0x80/0x90
> >  [<c0294d0a>] bus_for_each_dev+0x3a/0x60
> >  [<c0295d56>] driver_attach+0x16/0x20
> >  [<c0295cb0>] __driver_attach+0x0/0x90
> >  [<c029532f>] bus_add_driver+0x5f/0x110
> >  [<c023b3d2>] __pci_register_driver+0x82/0xc0
> >  [<c05c0b91>] piix_init+0x11/0x20
> >  [<c059ab11>] do_initcalls+0x41/0x130
> >  [<c0158acc>] register_irq_proc+0x9c/0xc0
> >  [<c01b4462>] proc_mkdir_mode+0x42/0x60
> >  [<c059ac30>] init+0x0/0xa0
> >  [<c059ac7c>] init+0x4c/0xa0
> >  [<c0104e7f>] kernel_thread_helper+0x7/0x18
> >  =======================
> > ata: 0x170 IDE port busy
> > ata: conflict with ide1
> > ata_piix: probe of 0000:00:1f.2 failed with error -16
> > ata_piix 0000:00:1f.5: MAP [ P0 P2 P1 P3 ]
>
> Patch pending in Greg's queue.

Which patch?

Since this affects libata directly, and since devres came in via libata, 
I would rather that libata bugs not get /too/ blocked by patches in 
other trees.

	Jeff



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/