On Sat, Apr 2, 2011 at 6:14 AM, Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx> wrote: > > (Adding Cc: linux-pci) > > On Apr 01 Eugene Kanter wrote: > > This card works fine in windows on the same harware (dual boot). Is it > > supported by latest driver? No attached device is recognized in linux > > and no changes in dmesg after any device is attached. > > > > kernel 2.6.35.11-83.fc14.i686 > > # lsmod | grep -e 1394 -e firewire > > firewire_ohci 17697 0 > > firewire_core 37873 1 firewire_ohci > > crc_itu_t 1235 1 firewire_core > > > > $ lspci > > .. > > 02:00.0 PCI bridge: Texas Instruments XIO2000(A)/XIO2200(A) PCI Express-to-PCI Bridge (rev 03) > > 03:00.0 FireWire (IEEE 1394): Texas Instruments XIO2200(A) IEEE-1394a-2000 Controller (PHY/Link) (rev 01) > > .. > > > > $ dmesg > > [ 322.568277] pci 0000:02:00.0: supports D1 D2 > > [ 322.569858] pci 0000:03:00.0: reg 10: [mem 0x00000000-0x000007ff] > > [ 322.569960] pci 0000:03:00.0: reg 14: [mem 0x00000000-0x00003fff] > > [ 322.570605] pci 0000:03:00.0: supports D1 D2 > > [ 322.570629] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot > > [ 322.570691] pci 0000:03:00.0: PME# disabled > > [ 322.571378] pci 0000:02:00.0: PCI bridge to [bus 03-ff] > > [ 322.571479] pci 0000:02:00.0: bridge window [io 0x0000-0x0000] (disabled) > > [ 322.571542] pci 0000:02:00.0: bridge window [mem 0x00000000-0x000fffff] (disabled) > > [ 322.571642] pci 0000:02:00.0: bridge window [mem 0x00000000-0x000fffff pref] (disabled) > > [ 322.573648] ACPI: Delete PCI Interrupt Routing Table for 0000:03 > > [ 322.582436] pci 0000:02:00.0: BAR 14: can't assign mem (size 0x100000) > > [ 322.582482] pci 0000:03:00.0: BAR 1: can't assign mem (size 0x4000) > > [ 322.582508] pci 0000:03:00.0: BAR 0: can't assign mem (size 0x800) Was this card hot-plugged after boot? Does it make any difference if the card is present at boot? It looks like the BIOS didn't assign any resources to the 02:00.0 bridge that leads to the firewire device, and Linux wasn't able to assign anything either. Can you please attach the complete dmesg log? That will help figure out why we couldn't assign anything to the bridge. > > [ 326.502149] irq 9: nobody cared (try booting with the "irqpoll" option) > > ... > > [ 326.502246] handlers: > > [ 326.502248] [<c05ef6a2>] (acpi_irq+0x0/0x2e) > > [ 326.502256] Disabling IRQ #9 This makes me think maybe we got the IRQ to signal a hot-add of the firewire device, but possibly the ACPI hotplug driver isn't there to field it? If that's the case, it seems like we could do a better job of reporting the problem. Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
