Messages in this thread | | | Subject | Re: [BUG] [hwmon] linux 2.6.31-rc6 regression | From | Calvin Walton <> | Date | Sun, 16 Aug 2009 10:28:13 -0400 |
| |
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.
-- Calvin Walton <calvin.walton@gmail.com>
-- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |