Hi,

I keep noticing the following messages in dmesg for 2 different hardware systems (one running Tumbleweed, the other one Leap 15.0). Hex addresses truncated for clarity:

TW:

Code:
[   42.463931] battery: ACPI: Battery Slot [BAT0] (battery present)
[   42.955476] ACPI Warning: SystemIO range 0x.... conflicts with OpRegion 0x.... (\GPIO) (20190215/utaddress-204)
[   42.955489] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   42.955491] ACPI Warning: SystemIO range 0x.... conflicts with OpRegion 0x.... (\GPIO) (20190215/utaddress-204)
[   42.955497] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   42.955499] lpc_ich: Resource conflict(s) found affecting gpio_ich
Leap:

Code:
[    9.450066] ACPI: Power Button [PWRF]
[    9.451507] ACPI Warning: SystemIO range .... conflicts with OpRegion .... (\PMIO) (20170303/utaddress-213)
[    9.451512] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    9.451514] ACPI Warning: SystemIO range .... conflicts with OpRegion .... (\_SB.PCI0.LPCB.GPBX) (20170303/utaddress-213)
[    9.451516] ACPI Warning: SystemIO range .... conflicts with OpRegion .... (\GPIO) (20170303/utaddress-213)
[    9.451518] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    9.451519] ACPI Warning: SystemIO range .... conflicts with OpRegion .... (\_SB.PCI0.LPCB.GPBX) (20170303/utaddress-213)
[    9.451521] ACPI Warning: SystemIO range .... conflicts with OpRegion .... (\GPIO) (20170303/utaddress-213)
[    9.451522] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    9.451523] ACPI Warning: SystemIO range .... conflicts with OpRegion .... (\_SB.PCI0.LPCB.GPBX) (20170303/utaddress-213)
[    9.451525] ACPI Warning: SystemIO range .... conflicts with OpRegion .... (\GPIO) (20170303/utaddress-213)
[    9.451527] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[    9.451527] lpc_ich: Resource conflict(s) found affecting gpio_ich
Searching the web I found that someone claims he has found a fix but what he actually links to looks more like a workaround and I am not sure how good it is as it involves blacklisting. Also "the known bug" mentioned there ends with a message "This isn't an error, there's nothing to fix". On Gentoo's forums someone suggests:

You can force the kernel to ignore it by passing acpi_enforce_resources=lax on the boot cmdline [...], it might make your hardware sensors work in Linux but it might also reduce stability.
I tried this on the TW system and the result changed a bit:

Code:
[   36.384906] battery: ACPI: Battery Slot [BAT0] (battery present)
[   36.466969] ACPI Warning: SystemIO range .... conflicts with OpRegion .... (\GPIO) (20190215/utaddress-204)
[   36.466981] ACPI: This conflict may cause random problems and system instability
[   36.466982] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[   36.466984] ACPI Warning: SystemIO range .... conflicts with OpRegion .... (\GPIO) (20190215/utaddress-204)
[   36.466990] ACPI: This conflict may cause random problems and system instability
[   36.466991] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
What I notice is that after setting the kernel parameter this disappeared:

Code:
lpc_ich: Resource conflict(s) found affecting gpio_ich
However I don't understand what they actually mean by "instability", what to expect etc.

My questions are:

1. What negative effect has this resource conflict? (i.e. why the warning, instability?)
2. How does one "use ACPI driver instead"?
3. Is this a bug or not? (i.e. should I report it)
4. What should I do (if anything needs to be done)?