From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Richard Tillmore <rtillmore@gmail.com>
Cc: Robert Hancock <hancockrwd@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: resource piix4_smbus conflicts with ACPI region SMRG
Date: Fri, 4 Jun 2010 01:05:19 +0100 [thread overview]
Message-ID: <20100604000519.GA15830@srcf.ucam.org> (raw)
In-Reply-To: <AANLkTil9MQq-22Q8_0-J49B56EFUlTkUf5o4Lpd5BVum@mail.gmail.com>
On Thu, Jun 03, 2010 at 06:50:44PM -0500, Richard Tillmore wrote:
> On Mon, May 31, 2010 at 10:13 PM, Robert Hancock wrote:
> > You should be able to use acpi_enforce_resources=lax on the kernel
> > command line to allow the driver to load. The problem is that the
> > kernel can't tell if it's safe to allow a driver to access that
> > hardware since it may conflict with BIOS access (in some cases this
> > can cause serious problems like system overheating or spurious thermal
> > shutdowns if the BIOS also accesses the device to perform thermal
> > management) and so the default is to not allow it.
>
> I booted with acpi_enforce_resources=lax and I now can get my CPU
> temperature. So is my having to add acpi_enforce_resources=lax an
> effect of ACPI changes or bootmem changes?
ACPI changes. Your firmware indicates that ACPI makes use of the smbus
controller - since many smbus transactions involve writing an address
and then a value, and since we can't enforce locking between the kernel
and the firmware, it's not possible to prove that it's safe to allow the
kernel to touch these resources. Passing the kernel parameter disables
this check in cases where you know it's safe.
--
Matthew Garrett | mjg59@srcf.ucam.org
prev parent reply other threads:[~2010-06-04 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 22:12 resource piix4_smbus conflicts with ACPI region SMRG Richard Tillmore
2010-05-31 23:42 ` Robert Hancock
2010-06-01 2:36 ` Richard Tillmore
2010-06-01 3:13 ` Robert Hancock
2010-06-03 23:50 ` Richard Tillmore
2010-06-04 0:05 ` Matthew Garrett [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=20100604000519.GA15830@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rtillmore@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