From: Jani Aho <jani.aho@bonetmail.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org, i2c@lm-sensors.org
Subject: Re: Sensors broke between 2.6.16.16 and 2.6.16.17 - SOLVED
Date: Sun, 13 Aug 2006 08:47:13 +0200 [thread overview]
Message-ID: <44DECAF1.8020902@bonetmail.com> (raw)
In-Reply-To: <44DE4EC8.8090404@gmail.com>
Jiri Slaby wrote:
> Jani Aho wrote:
>> Hi
>>
>> The sensors on my motherboard stopped working between 2.6.16.16 and
>> 2.6.16.17. The latest kernel version I have tried is 2.6.17.8 and it
>> still has the same problem.
>>
>> The motherboard is an ASUS P4PE and it uses the asb100 and i2c-i801
>> modules to get sensor information.
>>
>> A diff in /sys between a bad (2.6.17.8) and a good (2.6.16.16) kernel
>> gives:
>
> And is there any diff in dmesgs of those 2 kernels?
>
Problem solved.
The only related message in the dmesg diff was:
--- dmesg.bad 2006-08-13 08:21:21.000000000 +0200
+++ dmesg.good 2006-08-13 08:17:53.000000000 +0200
+PCI: Enabled i801 SMBus device
Looking at the changelog for 2.6.16.17, I found this patch:
commit a9cacd682ed7c031fa05b1d1367a3b3221813932
Author: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Date: Mon May 15 09:44:33 2006 -0700
[PATCH] smbus unhiding kills thermal management
Do not enable the SMBus device on Asus boards if suspend is used. We do
not reenable the device on resume, leading to all sorts of undesirable
effects, the worst being a total fan failure after resume on Samsung P35
laptop.
This fixes bug #6449 at bugzilla.kernel.org.
For some strange reason I had ACPI Sleep States enabled, so I disabled
it, recompiled the kernel and hey presto, the sensors are back.
Thanks for taking your time on this none problem
Jani
prev parent reply other threads:[~2006-08-13 6:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-12 17:20 Sensors broke between 2.6.16.16 and 2.6.16.17 Jani Aho
2006-08-12 21:58 ` Jiri Slaby
2006-08-13 6:47 ` Jani Aho [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=44DECAF1.8020902@bonetmail.com \
--to=jani.aho@bonetmail.com \
--cc=i2c@lm-sensors.org \
--cc=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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