All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: 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 10:32:51 +0100	[thread overview]
Message-ID: <20090816093251.GA1027@srcf.ucam.org> (raw)
In-Reply-To: <20090816053735.GB1998@phenom2.trippelsdorf.de>

On Sun, Aug 16, 2009 at 07:37:35AM +0200, Markus Trippelsdorf wrote:
> On Sun, Aug 16, 2009 at 02:03:03AM +0100, Matthew Garrett wrote:
> > 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.

It's not - 2.6.29 had this behaviour, and it got broken in 2.6.30. This 
restores the status quo.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2009-08-16  9:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-15 10:29 [BUG] [hwmon] linux 2.6.31-rc6 regression 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 [this message]
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

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=20090816093251.GA1027@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.