From: Robert Hancock <hancockrwd@gmail.com>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Regression: Linux 2.6.31-rc7 lost sensors on asus mobo
Date: Sat, 22 Aug 2009 00:12:25 -0600 [thread overview]
Message-ID: <4A8F8C49.2030406@gmail.com> (raw)
In-Reply-To: <200908212309.31505.gene.heskett@verizon.net>
On 08/21/2009 09:09 PM, Gene Heskett wrote:
> On Friday 21 August 2009, Linus Torvalds wrote:
>> You know the drill, so all together now: "Another week, another -rc
>> kernel".
>
> Another rebuild didn't help:
>
> Thinking it didn't load it87, I tried again:
>
> [root@coyote 3.002005]# modprobe it87
> FATAL: Error inserting it87 (/lib/modules/2.6.31-rc7/kernel/drivers/hwmon/it87.ko): Device or resource busy
> [root@coyote 3.002005]# sensors
> No sensors found!
> Make sure you loaded all the kernel drivers you need.
> Try sensors-detect to find out which these are.
>
> Been there, done that, no joy.
>
> From messages when I attempt to access the it87:
> Aug 21 22:59:37 coyote kernel: [ 572.507928] it87: Found IT8716F chip at 0x290, revision 1
> Aug 21 22:59:37 coyote kernel: [ 572.507937] it87: in3 is VCC (+5V)
> Aug 21 22:59:37 coyote kernel: [ 572.507939] it87: in7 is VCCH (+5V Stand-By)
> Aug 21 22:59:37 coyote kernel: [ 572.508232] ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region IP__ [0x295-0x296]
> Aug 21 22:59:37 coyote kernel: [ 572.508234] ACPI: Device needs an ACPI driver
>
> From uname -a
> Linux coyote.coyote.den 2.6.31-rc7 #2 SMP PREEMPT Fri Aug 21 22:37:38 EDT 2009 i686 athlon i386 GNU/Linux
>
> .config is attached, in case I've screwed the moose.
>
The ACPI AML on your machine indicates that the BIOS may attempt to
access the it87 hardware, and the kernel now by default blocks it87 from
requesting those ports as it may conflict with what the BIOS is trying
to do. On some machines, the ACPI BIOS accesses hardware monitoring
chips itself to manage ACPI thermal zones, etc. and the conflicting
access can cause incorrect temperature readings and other bad behavior.
You can try acpi_enforce_resources=lax on the kernel command line to
restore the previous behavior. Or for some Asus boards, you can try the
asus_atk0110 ACPI driver instead of it87.
next prev parent reply other threads:[~2009-08-22 6:12 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-22 1:26 Linux 2.6.31-rc7 Linus Torvalds
2009-08-22 3:09 ` Regression: Linux 2.6.31-rc7 lost sensors on asus mobo Gene Heskett
2009-08-22 3:47 ` Linus Torvalds
2009-08-22 12:56 ` Gene Heskett
2009-08-22 6:12 ` Robert Hancock [this message]
2009-08-22 10:54 ` Stefan Richter
2009-08-22 13:48 ` Gene Heskett
2009-08-22 14:38 ` Stefan Richter
2009-08-22 19:55 ` Gene Heskett
2009-08-22 13:40 ` Gene Heskett
2009-08-23 10:56 ` Linux 2.6.31-rc7 Geert Uytterhoeven
2009-08-26 5:06 ` KOSAKI Motohiro
2009-08-25 17:25 ` mailing54
2009-08-25 18:11 ` Linus Torvalds
2009-08-25 21:37 ` mailing54
2009-08-25 22:07 ` Linus Torvalds
[not found] ` <1251239637.26348.20.camel@gaiman.anholt.net>
2009-08-26 1:51 ` Zhenyu Wang
2009-08-26 3:33 ` Linus Torvalds
2009-08-26 3:47 ` Dave Airlie
2009-08-26 4:13 ` Linus Torvalds
2009-08-26 4:58 ` Dave Airlie
2009-08-26 17:12 ` Linus Torvalds
2009-08-26 17:18 ` Jesse Barnes
2009-08-26 6:26 ` Eric Anholt
2009-08-26 6:35 ` Dave Airlie
2009-08-26 3:58 ` Zhenyu Wang
2009-08-26 4:20 ` Linus Torvalds
2009-09-10 5:47 ` Zhenyu Wang
2009-08-26 10:09 ` ykzhao
2009-08-30 22:01 ` Tino Keitel
-- strict thread matches above, loose matches on Subject: below --
2009-08-22 4:48 Regression: Linux 2.6.31-rc7 lost sensors on asus mobo Zeev Tarantov
2009-08-22 13:34 ` Gene Heskett
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=4A8F8C49.2030406@gmail.com \
--to=hancockrwd@gmail.com \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--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