All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] unhide_ICH_SMBus: line 33:
Date: Tue, 15 Sep 2009 13:27:37 +0000	[thread overview]
Message-ID: <20090915152737.4d77623a@hyperion.delvare> (raw)
In-Reply-To: <4A9122E1.7010006@ribosome.natur.cuni.cz>

On Tue, 15 Sep 2009 15:11:39 +0200, Martin MOKREJ¦ wrote:
> Jean Delvare wrote:
> > This is exactly the symptom described in the blog post I sent you to.
> > http://hansdegoede.livejournal.com/7932.html
> > Did you read it?
> 
> I did and therefore it seemed to me the problem is with the driver.
> I haven't figured out I am using a wrong one. :( So I should probably
> go and read the FAQ again. ;-)
> 
> > 
> >> $ dmesg
> >> [cut]
> >> i801_smbus 0000:00:1f.3: PCI INT B -> Link[LNKB] -> GSI 11 (level, low) -> IRQ 11
> >> [cut]
> >>
> >> $ sensors
> >> ds1621-i2c-4-4c
> >> Adapter: SMBus I801 adapter at e800
> >> temp:     +51.00°C  (low  = +51.0°C, high = +51.0°C)  ALARM (LOW)
> > 
> > You don't really have a DS162x chip on your system, do you? The output
> > above is rather suspicious. Does the temperature value ever changes?
> 
> At the moment I have under 2.6.30.6:
> 
> # sensors
> ds1621-i2c-4-4c
> Adapter: SMBus I801 adapter at e800
> temp:     +64.00°C  (low  = +64.0°C, high = +64.0°C)  ALARM (HIGH)

Once again, input = low = high, this doesn't make any sense. This has
to be a misdetection. So I suggest that you stop loading the ds1621
driver.

As this was the only chip seen by sensors-detect on your system, this
simply means that lm-sensors' native drivers are of no use on your
system. The good news is that this means the ACPI conflicts policy
change in recent kernels doesn't affect you much.

> (...)
> Once again, it is ASUS L3C/S laptop.

On laptops, thermal management is almost always handled by ACPI. So
your best chances are the acpi "thermal" driver and its bridge driver
to lm-sensors (thermal_sys, CONFIG_THERMAL=m or y and
CONFIG_THERMAL_HWMON=y).

And there are also a number of drivers dedicated to Asus systems, such
as asus_atk0110, asus-laptop and asus_acpi. You should try them if you
haven't already.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2009-09-15 13:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-23 11:07 [lm-sensors] unhide_ICH_SMBus: line 33: Martin MOKREJŠ
2009-09-10  7:48 ` Jean Delvare
2009-09-15  8:00 ` Jean Delvare
2009-09-15 13:11 ` Martin MOKREJŠ
2009-09-15 13:27 ` Jean Delvare [this message]
2009-09-15 13:35 ` Luca Tettamanti
2009-09-15 15:43 ` Martin MOKREJŠ
2009-09-15 15:55 ` Jean Delvare
2009-09-15 16:33 ` Martin MOKREJŠ
2009-09-15 16:41 ` Martin MOKREJŠ
2009-09-15 16:55 ` Jean Delvare
2009-09-16 16:48 ` Martin MOKREJŠ
2009-09-16 16:56 ` Martin MOKREJŠ
2009-09-16 18:10 ` Jean Delvare

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=20090915152737.4d77623a@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.