From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Calvin Walton <calvin.walton@gmail.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Zeev Tarantov <zeev.tarantov@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] [hwmon] linux 2.6.31-rc6 regression
Date: Sun, 16 Aug 2009 17:24:08 +0200 [thread overview]
Message-ID: <20090816152408.GA1951@phenom2.trippelsdorf.de> (raw)
In-Reply-To: <1250432893.7591.5.camel@ayu>
On Sun, Aug 16, 2009 at 10:28:13AM -0400, Calvin Walton wrote:
> On Sun, 2009-08-16 at 07:37 +0200, Markus Trippelsdorf wrote:
> > On Sun, Aug 16, 2009 at 02:03:03AM +0100, Matthew Garrett wrote:
> > > On Sat, Aug 15, 2009 at 01:29:48PM +0300, Zeev Tarantov wrote:
> > >
> > > > [ 3.276720] w83627ehf: Found W83627DHG chip at 0x290
> > > > [ 3.276894] ACPI: I/O resource w83627ehf [0x295-0x296] conflicts
> > > > with ACPI region HWRE [0x290-0x299]
> > > > [ 3.277171] ACPI: Device needs an ACPI driver
> > >
> > > The hwmon driver is attempting to allocate a region that's also used by
> > > your ACPI firmware. There's no way to synchronise access between the
> > > kernel and the firmware, so allowing both is potentially racy - we've
> > > seen numerous cases where the combination results in the system
> > > incorrectly generating critical temperatuer shutdowns, for instance,
> > > when some other indexed access gets interpreted as the temperature or
> > > when the hwmon chip's state machine is confused. The failure of hwmon to
> > > bind is a feature here, not a bug. You can override it with
> > > acpi_enforce_resources=no on the kernel command line.
> >
> > But we don't introduce »features« that break hardware monitoring on
> > numerous machines in rc6 normally, IIRC.
> > If this so important and critical to you, than just add a »hyperstrict«
> > parameter to acpi_enforce_resources or make »lax« the default.
>
> Note that, as this is an ASUS board, there is actually an ACPI firmware
> driver available that will let you do hardware monitoring in a way that
> doesn't conflict with the firmware - give the "ASUS ATK0110 ACPI hwmon"
> driver a try.
Thanks for the hint. I had to patch lm_sensors, but now everything is
working fine. The output of sensors is also much nicer.
(http://lists.lm-sensors.org/pipermail/lm-sensors/2008-June/023606.html)
--
Markus
prev parent reply other threads:[~2009-08-16 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 10:29 Zeev Tarantov
2009-08-15 10:43 ` Markus Trippelsdorf
2009-08-16 1:03 ` Matthew Garrett
2009-08-16 5:37 ` Markus Trippelsdorf
2009-08-16 9:32 ` Matthew Garrett
2009-08-16 14:39 ` Stefan Richter
2009-08-16 14:41 ` Matthew Garrett
2009-08-16 13:38 ` Alan Cox
2009-08-16 14:28 ` Calvin Walton
2009-08-16 15:24 ` Markus Trippelsdorf [this message]
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=20090816152408.GA1951@phenom2.trippelsdorf.de \
--to=markus@trippelsdorf.de \
--cc=calvin.walton@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=zeev.tarantov@gmail.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
all inboxes | Powered by JetHome®