Prev: [PATCH V3 -recall-] x86, UV: BAU performance and error recovery
Next: lp_events: an lternitive to suspend blocker user mode and kernel API
From: Matthew Garrett on 3 Jun 2010 20:10
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(a)srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2
Prev: [PATCH V3 -recall-] x86, UV: BAU performance and error recovery
Next: lp_events: an lternitive to suspend blocker user mode and kernel API