On Thu, Aug 02, 2012 at 04:00:42PM +0200, Arend van Spriel wrote: > On 08/02/2012 03:45 PM, Josh Boyer wrote: > > # > > # Broadcom specific AMBA > > # > > CONFIG_BCMA=m > > CONFIG_BCMA_BLOCKIO=y > > CONFIG_BCMA_HOST_PCI_POSSIBLE=y > > CONFIG_BCMA_HOST_PCI=y > > CONFIG_BCMA_DRIVER_GMAC_CMN=y > > # CONFIG_BCMA_DEBUG is not set > > As you indicated not seeing anything on the bcma bus (in kernel log, you > mean?) I was wondering about BCMA_HOST_PCI flag, but that looks fine. > Not sure why you have BCMA_DRIVER_GMAC_CMN enabled. Grabbing straws. > > I actually had a similar behaviour and noticed a PCI bridge port was > missing. Do you see that also with lspci? Hm. I can't recall the full lspci output before this problem showed up, but I do have dmesg output from before and now. Comparing them, I see: [ 0.639235] pci_bus 0000:02: busn_res: [bus 02] is inserted under [bus 00-ff] [ 0.639284] pci 0000:02:00.0: [14e4:4727] type 00 class 0x028000 [ 0.639321] pci 0000:02:00.0: reg 10: [mem 0xfe500000-0xfe503fff 64bit] [ 0.639550] pci 0000:02:00.0: supports D1 D2 [ 0.639551] pci 0000:02:00.0: PME# supported from D0 D3hot D3cold [ 0.641078] pci 0000:00:1c.0: PCI bridge to [bus 02] [ 0.641091] pci 0000:00:1c.0: bridge window [mem 0xfe500000-0xfe5fffff] from before, and: [ 0.636241] pci_bus 0000:02: busn_res: [bus 02] is inserted under [bus 00-ff] [ 0.636244] pci 0000:00:1c.0: PCI bridge to [bus 02] [ 0.636342] pci_bus 0000:03: busn_res: [bus 03] is inserted under [bus 00-ff] now. So it seems 1434:4727 is missing now. How very very odd. <5 minutes later> OK, so I physically unplugged the machine from the wall and let it sit for 5 minutes. When I plugged it back in, that PCI bridge port magically reappeared. I guess that's good news. Thanks for suffering through with me. I'll go test Seth's patches now. I hate computers. josh -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
