On Tuesday 18 November 2008 12:25:34 am GARCIA DE SORIA LUCENA, JUAN JESUS wrote: > > -----Original Message----- > > From: Bjorn Helgaas [mailto:bjorn.helgaas@xxxxxx] > > Sent: Monday, November 17, 2008 20:29 > > To: GARCIA DE SORIA LUCENA, JUAN JESUS > > Cc: linux-pci@xxxxxxxxxxxxxxx; jbarnes@xxxxxxxxxxxxxxxx; Jiri > > Slaby; Gary Hade; JIMENEZ SHAW, FRANCISCO JAVIER > > Subject: Re: PCI bus conflict hang: how to avoid the > > allocation of an I/O range. > > > > I added your nice analysis from http://lkml.org/lkml/2008/11/12/60 > > to the bugzilla. > > > > Theoretically, ACPI should tell us about any non-PCI devices > > that might be in the 0x1000-0x1fff range. This command: > > $ grep . /sys/bus/pnp/devices/*/* > > should tell you about them. > > I'll look at it tonight. I know the firmware in my laptop is rather > flaky (for instance, it has two APIC tables, but I think that using > acpi_apic_instance=2 didn't help either). > > Would this mean that a customized DSDT piggy-backed on the initrd would > be a way in which the range could be pre-reserved? A customized DSDT could probably be used to reserve the range, but I don't think that's a good solution. If it turns out to be a BIOS bug, I think it would be better to add some kind of quirk that would work out of the box for everybody with that laptop. 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
