On Thursday 04 February 2010 10:55:57 am Bjorn Helgaas wrote: > On Wednesday 03 February 2010 09:37:43 pm Larry Finger wrote: > > In addition to the above, my system now boots with "pci=use_crs", unlike when I > > filed the Bugzilla. > > Huh. From http://lkml.org/lkml/2009/6/24/11, I had assumed the main > problem was that we overflowed the 16-entry bus resource table, but > there must be more to it. > > If you can build and boot the linux-next branch with my patches and > collect the dmesg log, maybe it will have a clue. You can boot without > "pci=use_crs"; I don't think that will make any difference on your box. Thanks for testing these and collecting the dmesg log (http://bugzilla.kernel.org/attachment.cgi?id=24914). That log is from the PCI linux-next branch plus my patches, without using "pci=use_crs". On the current upstream (e.g., the c80d292 kernel you started with), we have PCI_BUS_NUM_RESOURCES == 16. Your _CRS returns 17 windows (the "pci_root PNP0A08:00 host bridge window" lines), so when you boot with "pci=use_crs", we should be discarding the last window, which is an important one: pci_root PNP0A08:00: host bridge window [mem 0xc0000000-0xfebfffff] Can you collect the dmesg log from the c80d292 kernel with "pci=use_crs"? I'm sorry to trouble you for this, but it still looks to me like that should fail, so I'd really like to understand why it's working. 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
