From: Linus Torvalds <torvalds@linux-foundation.org>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Regression: Linux 2.6.31-rc7 lost sensors on asus mobo
Date: Fri, 21 Aug 2009 20:47:12 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0908212041130.3158@localhost.localdomain> (raw)
In-Reply-To: <200908212309.31505.gene.heskett@verizon.net>
On Fri, 21 Aug 2009, Gene Heskett wrote:
>
> From messages when I attempt to access the it87:
So what was the last kernel that worked ok for you?
> 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
There haven't been any changes to the it87 driver since 2.6.30, nor do I
see any ACPI changes that would be relevant. Of course, if you used to
build without any ACPI support at all, that region conflict wouldn't have
shown up, so it _could_ be config-dependent, but that sounds unliklely
too.
Linus
next prev parent reply other threads:[~2009-08-22 3:47 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 [this message]
2009-08-22 12:56 ` Gene Heskett
2009-08-22 6:12 ` Robert Hancock
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
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=alpine.LFD.2.01.0908212041130.3158@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome