On Thu, 7 Jun 2007 11:33:12 -0700 "Miles Lane" <[EMAIL PROTECTED]> wrote:
> Andrew, is it okay to debug this with the MM tree? I see this with > Linus' kernels as well. It's a long-standing issue, but I have always > just used pci=assign-busses in the past. > Dunno, but let's not miss an opportunity to bug the PCI maintainer. > > [ 0.215128] PCI: Transparent bridge - 0000:00:1e.0 > [ 0.215142] PCI: Scanning behind PCI bridge 0000:02:09.0, config > 000000, pass 0 > [ 0.215158] PCI: Scanning behind PCI bridge 0000:02:09.0, config > 000000, pass 1 > [ 0.215184] PCI: Bus #03 (-#06) is hidden behind transparent bridge > #02 (-#02) (try 'pci=assign-busses') > [ 0.215187] Please report the result to linux-kernel to fix this > permanently > [ 0.215192] PCI: Bus scan for 0000:02 returning with max=06 > [ 0.215199] PCI: Scanning behind PCI bridge 0000:00:1e.0, config > 020200, pass 1 > [ 0.215209] PCI: Bus scan for 0000:00 returning with max=06 > Does the kernel otherwise work OK with and without pci=assign-busses? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
