https://bugzilla.kernel.org/show_bug.cgi?id=47981
--- Comment #34 from Bjorn Helgaas <bhelg...@google.com> 2012-10-12 21:03:52 --- My inclination is to do nothing in Linux or ACPICA. Everything points to this being a BIOS issue, and it seems like such an egregious issue that it's not worth spending time or adding kernel bandaids to try to patch things up. For this particular issue of the boot failing because we can't get valid _CRS info for the PCI host bridges, booting with "pci=nocrs" is a reasonable workaround and seems sufficient. We could make the argument that Linux should be able to survive this by reassigning all the BARs to the values they contained at BIOS handoff. In fact, we do have code that's supposed to do that. My guess is that it failed in this case because we think there are no resources available on the PCI bus at all. We can't really fall back to some sort of default resources, because it's actually quite common to have buses with no resources -- these are often used for things like uncore devices that need only config registers and no MEM or IO space -- and in those cases, we don't want to assume default resources. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
