On 22.06.12 at 10:46, Jean Delvare
wrote: Le jeudi 21 juin 2012 à 21:39 -0400, Jeff Mahoney a écrit : -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 6/21/12 11:49 AM, Jean Delvare wrote:
Hi Cristian,
Le jeudi 21 juin 2012 à 09:31 -0400, Cristian Rodríguez a écrit :
After upgrading to 3.5rc3 I get the following warnings
[ 17.952055] ACPI Warning: 0x0000000000000830-0x0000000000000833 SystemIO conflicts with Region \PMRG 1 (20120320/utaddress-251) [ 17.952059] ACPI Warning: 0x0000000000000830-0x0000000000000833 SystemIO conflicts with Region \_SB_.PCI0.SBRG.SMIE 2 (20120320/utaddress-251) [ 17.952060] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 17.952061] lpc_ich: Resource conflict(s) found affecting iTCO_wdt [ 17.952065] ACPI Warning: 0x0000000000000828-0x000000000000082f SystemIO conflicts with Region \PMRG 1 (20120320/utaddress-251) [ 17.952066] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 17.952095] lpc_ich: Resource conflict(s) found affecting gpio_ich
How should I clear this conflict, which driver I have to blacklist ?
This is caused by the new driver for Intel GPIO pins. Blacklist driver "lpc_ich" if you want to get rid of these.
Or should we disable that completely?
I'm not sure what you mean exactly. Do you mean CONFIG_LPC_ICH=n? I see no good reason for that.
Also, there being two other drivers that select this, it would imply also disabling those (GPIO_ICH/gpio-ich.ko and ITCO_WDT/ iTCO_wdt.ko). What I find concerning is that there are resource conflicts reported among those. Jan
There will be machines out there where the BIOS doesn't hijack the resources and native drivers are useful, be it for the watchdog or GPIOs. I'll need the GPIOs on my own workstation at the very least, I've been waiting for months for the driver to go upstream, so please don't go disabling it now :p
If you think these warnings are too verbose and/or frightening, this can certainly be discussed and improved.
Anyway, ACPI resource conflicts are going to be more and more frequent and this is an issue that will require a general solution in cooperation with hardware vendors, ACPI people, and kernel developers. BIOS wants to control more and more things, locking OS out of the hardware. First it was hardware monitoring, then SMBus, now GPIOs and watchdog... what next?
-- Jean Delvare Suse L3
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org