From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Julian Wollrath <julian.wollrath@stud.uni-goettingen.de>
Cc: linux-acpi@vger.kernel.org, Lv Zheng <lv.zheng@intel.com>,
Zhang Rui <rui.zhang@intel.com>
Subject: Re: New ACPI warnings with v3.16.0-rc1
Date: Thu, 19 Jun 2014 01:09:25 +0200 [thread overview]
Message-ID: <8028563.JQMq23p6sJ@vostro.rjw.lan> (raw)
In-Reply-To: <20140618235004.25295650@saldaea>
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
next prev parent reply other threads:[~2014-06-18 22:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-18 21:50 New ACPI warnings with v3.16.0-rc1 Julian Wollrath
2014-06-18 23:09 ` Rafael J. Wysocki [this message]
2014-06-18 22:58 ` Zhang Rui
2014-06-18 23:07 ` Zhang Rui
2014-06-18 23:38 ` Julian Wollrath
[not found] ` <20140619013921.5c05ded1@saldaea>
[not found] ` <20140625165603.391df68f@saldaea>
2014-06-25 23:33 ` Zhang Rui
2014-06-26 9:05 ` Julian Wollrath
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8028563.JQMq23p6sJ@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=julian.wollrath@stud.uni-goettingen.de \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rui.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox