From: Len Brown <lenb@kernel.org>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, lm-sensors@lm-sensors.org
Subject: Re: Revert "ACPICA: Remove obsolete acpi_os_validate_address interface"
Date: Tue, 11 Aug 2009 23:43:39 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0908112331250.8449@localhost.localdomain> (raw)
In-Reply-To: <20090803074620.GA2285@phenom2.trippelsdorf.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2400 bytes --]
(cc: lm-sensors)
> > Revert "ACPICA: Remove obsolete acpi_os_validate_address interface"
> >
> > This reverts commit f9ca058430333c9a24c5ca926aa445125f88df18.
> >
> > which caused a regression:
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=13620
> >
>
> This revert breaks it8720 hardware monitoring on my machine:
>
> ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region ECRE [0x290-0x2af]
> ACPI: Device needs an ACPI driver
Thanks for the report, but I don't have a simple answer for you.
The mechanism that is restored to 2.6.29 behaviour here
is intended to address an extremely severe bug in Linux
where native sensor drivers access the same registers
as AML, causing fun things like change of temperature units and
spurious critical thermal shutdowns.
The commit that we reverted here was an oversight in 2.6.30,
and so the current plan is to revert that commit in 2.6.30.stable too.
The mechanism prevents the sensor driver from loading when
such a potential conflict is detected.
If you can attach the output of acpidump from your machine
to a new bugzilla entry, we can verify that the mechanism
is indeed not mistaken on your box.
thanks,
Len Brown, Intel Open Source Technology Center
> Reverting the revert solves the problem:
>
> markus@phenom2 ~ % sensors
> it8720-isa-0290
> Adapter: ISA adapter
> in0: +0.00 V (min = +0.00 V, max = +4.08 V) ALARM
> in1: +1.65 V (min = +0.00 V, max = +4.08 V)
> in2: +1.14 V (min = +0.00 V, max = +4.08 V)
> in3: +3.09 V (min = +0.00 V, max = +4.08 V)
> in4: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM
> in5: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM
> in6: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM
> in7: +4.08 V (min = +0.00 V, max = +4.08 V) ALARM
> in8: +3.41 V
> fan1: 1175 RPM (min = 0 RPM)
> fan2: 1175 RPM (min = 0 RPM)
> fan3: 859 RPM (min = 0 RPM)
> temp1: +37.0°C (low = -1.0°C, high = +127.0°C) sensor = thermistor
> temp2: +41.0°C (low = -1.0°C, high = +127.0°C) sensor = thermistor
> temp3: -128.0°C (low = -1.0°C, high = +127.0°C) sensor = disabled
> cpu0_vid: +1.550 V
>
> k10temp-pci-00c3
> Adapter: PCI adapter
> temp1: +37.8°C
>
> dmesg and .config is attached.
>
> --
> Markus
>
prev parent reply other threads:[~2009-08-12 3:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 17:12 [git pull request] ACPI patches for 2.6.31-rc5 Len Brown
2009-08-03 7:46 ` Markus Trippelsdorf
2009-08-12 3:43 ` Len Brown [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=alpine.LFD.2.00.0908112331250.8449@localhost.localdomain \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=markus@trippelsdorf.de \
--cc=torvalds@linux-foundation.org \
/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®