public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, sensors@Stimpy.netroedge.com
Subject: Re: Kernel 2.6.9 & adm1021 & i2c_piix4 temperature monitoring
Date: Tue, 9 Nov 2004 19:18:44 +0100	[thread overview]
Message-ID: <20041109191844.112a04cb.khali@linux-fr.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0411091216120.3869@p500>

> How has it been re-worked, is the option no longer valid?

The option is still valid, but the init process is way less aggressive.
Chip isn't arbitrarily reset/reconfigured anymore, and temperature
limits are preserved. Thus what the option was trying to prevent is
probably not happening anymore in the first place.

> I believe it was along early 2.6.x and possibly 2.6.5-2.6.6 that I
> tried it without the option and the machine will shut itself off (due
> to lm-sensors/etc writing "their" values for what is too hot, forcing
> the machine to shutdown).
>
> $ sensors
> max1617-i2c-0-1a
> Adapter: SMBus PIIX4 adapter at 0850
> Board:       +45 C  (low  =   -55 C, high =  +127 C)
> CPU:         +41 C  (low  =   -55 C, high =  +110 C)
> 
> If I run without the option, the values change to something like -20 C
> to 50 or 60C, hence, when you compile a kernel it heats up and the box
> shuts itself off, with no warning at all, just powers off.

That part of the init process was actually removed in 2.6.6. Believe me,
you are not the only one to have complained about that nasty behavior.

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

      reply	other threads:[~2004-11-09 18:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 14:13 Kernel 2.6.9 & adm1021 & i2c_piix4 temperature monitoring Justin Piszcz
2004-11-08 15:02 ` Jean Delvare
2004-11-09 17:19   ` Justin Piszcz
2004-11-09 18:18     ` Jean Delvare [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=20041109191844.112a04cb.khali@linux-fr.org \
    --to=khali@linux-fr.org \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sensors@Stimpy.netroedge.com \
    /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