On Wednesday, June 18, 2014 11:50:04 PM Julian Wollrath wrote: > Hi, Hi, > with v3.16.0-rc1 I get the following warnings, which I did not occur > with v3.15.1: > [ 14.558365] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042f conflicts with OpRegion 0x0000000000000400-0x000000000000047f (\_SB_.PCI0.LPC_.PMIO) (20140424/utaddress-258) > [ 14.558377] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver > [ 14.558386] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\_SB_.PCI0.LPC_.LPIO) (20140424/utaddress-258) > [ 14.558392] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver > [ 14.558395] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\_SB_.PCI0.LPC_.LPIO) (20140424/utaddress-258) > [ 14.558401] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver > [ 14.558403] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x000000000000057f (\_SB_.PCI0.LPC_.LPIO) (20140424/utaddress-258) > [ 14.558409] ACPI: If an ACPI driver is available for this device, > you should use it instead of the native driver > > How can one find out, what the native driver is, and if there is an > ACPI driver? These are resource conflicts and I'm not sure why there were not there before. Perhaps we introduced a new driver trying to reserve system I/O ranges claimed by the ACPI core already. I agree that the second part of the message is not very useful, though. Rui and Lv (CCed) should be able to help you diagnose this problem further. Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
