New ACPI warnings with v3.16.0-rc1

New ACPI warnings with v3.16.0-rc1

[Julian Wollrath]

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?


Thank you for your time, with best regards,
Julian Wollrath

Re: New ACPI warnings with v3.16.0-rc1

[Zhang Rui]

On Thu, 2014-06-19 at 01:09 +0200, Rafael J. Wysocki wrote:
> 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?

please attach the acpidump output.

thanks,
rui
> 
> 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
> 

Re: New ACPI warnings with v3.16.0-rc1

[Zhang Rui]

On Thu, 2014-06-19 at 01:09 +0200, Rafael J. Wysocki wrote:
> 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?
> 
BTW, there is indeed one new driver that invokes
acpi_check_resource_conflict() between 3.15 and 3.16-rc1.
could you please check if CONFIG_SENSORS_NCT6683 is set in your config?
If yes, does the warning messages go away if CONFIG_SENSORS_NCT6683=n?

thanks,
rui

> 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
> 

Re: New ACPI warnings with v3.16.0-rc1

[Rafael J. Wysocki]

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

Re: New ACPI warnings with v3.16.0-rc1

[Julian Wollrath]

Hi,

> BTW, there is indeed one new driver that invokes
> acpi_check_resource_conflict() between 3.15 and 3.16-rc1.
> could you please check if CONFIG_SENSORS_NCT6683 is set in your
> config? If yes, does the warning messages go away if
> CONFIG_SENSORS_NCT6683=n?
CONFIG_SENSORS_NCT6683 is not set.

I just look into the dmesg output again and saw the following:
[   14.560580] lpc_ich: Resource conflict(s) found affecting gpio_ich

Then I checked the git log and stumbled upon commit 62cf2cdb99c7e (mfd:
lpc_ich: Enable GPIO for Panther Point). Since I have a Panther Point
chipset, that commit is possibly to blame, since now that driver can
also handle Panther Point. The only problem is, that CONFIG_LPC_ICH
gets auto-enabled by having CONFIG_ITCO_WDT (Intel Watchdog support)
enabled and it can not be disabled without disabling the watchdog
support.

> please attach the acpidump output.
Done.


Cheers,
Julian

Re: New ACPI warnings with v3.16.0-rc1

[Zhang Rui]

On Wed, 2014-06-25 at 16:56 +0200, Julian Wollrath wrote:
> Hmm, lets hope, this mail reaches the mailing list.
> 
yes, but I can not see your original post, thus I'm not clear what the
problems/warnings are.
please re-send your original email to the list.

thanks,
rui
> Am Thu, 19 Jun 2014 01:39:21 +0200
> schrieb Julian Wollrath <jwollrath@web.de>:
> 
> > Hi,
> > 
> > > > please attach the acpidump output.
> > > Done.
> > sorry, now it really is attached.
> > 
> > 
> > Cheers,
> > Julian

Re: New ACPI warnings with v3.16.0-rc1

[Julian Wollrath]

Am Thu, 26 Jun 2014 07:33:09 +0800
schrieb Zhang Rui <rui.zhang@intel.com>:

> On Wed, 2014-06-25 at 16:56 +0200, Julian Wollrath wrote:
> > Hmm, lets hope, this mail reaches the mailing list.
> > 
> yes, but I can not see your original post, thus I'm not clear what the
> problems/warnings are.
> please re-send your original email to the list.
The original post (and the threas beloning to it can be found under
http://marc.info/?i=20140618235004.25295650%20()%20saldaea or below.

Please note also, what if wrote in a follow up:
> I just look into the dmesg output again and saw the following:
> [   14.560580] lpc_ich: Resource conflict(s) found affecting gpio_ich
>
> Then I checked the git log and stumbled upon commit 62cf2cdb99c7e
> (mfd: lpc_ich: Enable GPIO for Panther Point). Since I have a Panther
> Point chipset, that commit is possibly to blame, since now that
> driver can also handle Panther Point. The only problem is, that
> CONFIG_LPC_ICH gets auto-enabled by having CONFIG_ITCO_WDT (Intel
> Watchdog support) enabled and it can not be disabled without
> disabling the watchdog support.

Cheers,
Julian

Original message:
Subject: New ACPI warnings with v3.16.0-rc1
Date: Wed, 18 Jun 2014 23:50:04 +0200

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?


Thank you for your time, with best regards,
Julian Wollrath