On Thu, Mar 24, 2011 at 05:58:30PM -0700, Bjorn Helgaas wrote: > On Thu, Mar 24, 2011 at 11:27 AM, Jonathan McDowell > <noodles@xxxxxxxx>wrote: > > > On Wed, Mar 23, 2011 at 10:50:20PM -0700, Bjorn Helgaas wrote: > > > > I assume that since you don't have a standard BIOS, you don't have > > > ACPI? > > > > Nope. Nor DMI. As previously mentioned there is a custom ASIC, but > > it's hidden behind these bridges. > > > > Thanks. Looks like your box doesn't even have PCI BIOS, so > pcibios_last_bus == -1 until pci_fixup_serverworks() updates it, so we > only scan bus 00. > > Another option would be to boot with "pci=lastbus=0xff". If you just > have a box or two, that might be the easiest solution, but I guess I'm > not opposed to a quirk like this. It's a firmware workaround, not a > hardware bug, and the message is irrelevant and possibly distracting > on machines with decent firmware, but it's not terrible. I've managed to get detection of the non-standard BIOS working, so I can actually quirk much more specifically now for my purposes. I don't believe there's any need to take this upstream if no one else is reporting problems. J. -- "This sentence no verb." -- Robin Stevens, ox.talk This .sig brought to you by the letter T and the number 42 Product of the Republic of HuggieTag -- 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
