On Fri, Jun 26, 2009 at 05:41:54PM -0700, Keith Mannthey wrote: > On Fri, 2009-06-26 at 15:16 -0600, Matthew Wilcox wrote: > > Linux gets hints from the BIOS in a number of different ways. You're > > probably using ACPI, so we'd look for a PNP0A03 device, then try to scan > > the bus that points to. > > Thanks, I have asked some BIOS (or I should say UFI) folks if they can > shed some light onto the situation. Great. > > Probably because you're telling it to scan PCI devices that the kernel > > doesn't know that it ought to scan. > > Is there anyway from module init context to tell the kernel to scan and > look to create a proper pci device out if it? Is there a way to create a > struct pci devices and add it back into the pool? I guess I need to dig > through the pci code a bit more. Yes, quite easy actually: call pci_scan_bus(0xff, &pci_root_ops, NULL); > At least one other person has seen this similar thing with the Zeons and > I don't think are running on IBM hardware. I have heard other core i7 > non Zeon cpus work just fine. "Xeons", not Zeons. I have a core i7 machine which doesn't find those devices (it's on an Asus Revolution motherboard). I managed to get it to discover the devices by booting with: pci=lastbus=255 This might work for you as a temporary workaround. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- 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
