From: Julian Wollrath <jwollrath@web.de>
To: Zhang Rui <rui.zhang@intel.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-acpi@vger.kernel.org, Lv Zheng <lv.zheng@intel.com>
Subject: Re: New ACPI warnings with v3.16.0-rc1
Date: Thu, 19 Jun 2014 01:38:30 +0200 [thread overview]
Message-ID: <20140619013830.265e74cd@saldaea> (raw)
In-Reply-To: <1403132844.30783.33.camel@rzhang1-toshiba>
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
next prev parent reply other threads:[~2014-06-18 23:38 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
2014-06-18 22:58 ` Zhang Rui
2014-06-18 23:07 ` Zhang Rui
2014-06-18 23:38 ` Julian Wollrath [this message]
[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=20140619013830.265e74cd@saldaea \
--to=jwollrath@web.de \
--cc=linux-acpi@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rjw@rjwysocki.net \
--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