On Sun, Sep 04, 2011 at 09:42:44PM +1200, Michal Ludvig wrote: > Hi Bjorn, > > On 09/02/2011 11:08 AM, Bjorn Helgaas wrote: > >Thanks! Can you reassign this to "Drivers/PCI" and set "Regression = > >yes"? I can't seem to do it myself. Also, the logs look like console > >logs, which don't include everything in the dmesg log unless you boot > >with "ignore_loglevel". Can you boot the failing one with > >"ignore_loglevel"? And maybe attach the "lspci -vv" output? > > Attached in bugzilla as requested. Let me know if you need something more. > https://bugzilla.kernel.org/show_bug.cgi?id=42002 I am looking into the issue. It looks like the address space collisions have left ->parent of some resources uncleared. [ 3.520023] pci 0000:00:1c.1: address space collision: [mem 0xfde00000-0xfdefffff 64bit pref] conflicts with PCI Bus 0000:00 [mem 0xf0000000-0xfed8ffff] [ 3.530010] pci 0000:00:1c.2: address space collision: [mem 0xfdf00000-0xfdffffff 64bit pref] conflicts with PCI Bus 0000:00 [mem 0xf0000000-0xfed8ffff] [ 3.540019] pci 0000:00:1c.3: address space collision: [mem 0xfeb00000-0xfebfffff] conflicts with PCI Bus 0000:00 [mem 0xf0000000-0xfed8ffff] This has confused allocate_resource() to believe that the resource needs to be reallocated with a bigger size. I will get back to you soon, probably with a patch. RP -- 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
