On Mon, 02 Apr 2007 10:35:40 +0200, Rene Rebe said:
(Sorry for the late reply..)
> IIRC a MSI Megabook S270 (I formerly owned) BIOS notifies this
> "Critical temperature reached (128C)" when the battery run empty
> when the OS did no action due to battery low indications. I guess
> the BIOS peopl
On Tue, 03 Apr 2007, Jeremy Fitzhardinge wrote:
> Attached. Is there some tool for decoding the DSDT?
iasl. The documentation is the ACPI Specification.
> >> ezr:pts/1; cat /proc/acpi/ibm/thermal
> >> temperatures: 72 55 -128 65 40 -128 35 -128 51 53 -128 -128 -128 -128
> >> -128 -128
> >
> >
On 4/3/07, Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:
Attached. Is there some tool for decoding the DSDT?
iasl
http://www.intel.com/technology/iapc/acpi/downloads.htm
http://www.intel.com/technology/iapc/acpi/license2.htm
--
Who logs in to gdm? Not I, said the duck.
-
To unsubscribe from
On Sun, 01 Apr 2007, Jeremy Fitzhardinge wrote:
> > You can use ibm-acpi to properly track your thinkpad thermal sensors, load
> > it with the "experimental=1" parameter, and look at what gets exported at
> > /proc/acpi/ibm/thermal.
>
> Interesting. The first number corresponds with the ACPI THM0
On Sunday 01 April 2007 20:57:57 Kyle Moffett wrote:
> On Mar 31, 2007, at 02:36:08, Jeremy Fitzhardinge wrote:
> > When I run 2.6.21-rc5 + Andi's x86 patches + paravirt_ops patches,
> > I've been getting my machine shut down with critical thermal
> > shutdown messages:
> >
> > Mar 30 23:19:03
Henrique de Moraes Holschuh wrote:
> On Sun, 01 Apr 2007, Jeremy Fitzhardinge wrote:
>
>> control problems. Perhaps the ambient temperature was lower when I
>> reported success.
>>
>
> You can use ibm-acpi to properly track your thinkpad thermal sensors, load
> it with the "experimental=1"
On Sun, 01 Apr 2007, Jeremy Fitzhardinge wrote:
> control problems. Perhaps the ambient temperature was lower when I
> reported success.
You can use ibm-acpi to properly track your thinkpad thermal sensors, load
it with the "experimental=1" parameter, and look at what gets exported at
/proc/acpi/
Jeremy Fitzhardinge wrote:
> Alexey Starikovskiy wrote:
>
>> Could you try to unload or disable hardware sensors and check if it
>> helps?
>> CONFIG_I2C=m
>> CONFIG_I2C_ALGOBIT=m
>> CONFIG_I2C_ALGOPCA=m
>> CONFIG_I2C_I810=m
>> CONFIG_I2C_PIIX4=m
>> CONFIG_SENSORS_DS1337=m
>> CONFIG_SENSORS_DS137
On Sun, 01 Apr 2007, Pavel Machek wrote:
> ACPI is misdesigned, and lm_sensors can't cope with that.
Err, HOW exactly are you accessing the ThinkPad i2c buses directly? Or did
Lenovo change completely the hardware project of thinkpads in the X60?
Or did anyone add an lm-sensors that attach to the
On Sun, 01 Apr 2007, Pavel Machek wrote:
> Are you running lm_sensors?
lm-sensors can't confuse any recent thinkpad's thermal management. The i2c
buses that matter are all behind the EC, you have to ask the EC for data.
--
"One disk to rule them all, One disk to find them. One disk to bring
Kyle Moffett wrote:
> Well, 128C is more than hot enough to boil water and well above the
> thermal tolerances of most CPUs, so I would imagine that were your CPU
> actually that hot it wouldn't be capable of printing the "Critical
> temperature reached" messages, let alone properly rebooting.
Yes
On Mar 31, 2007, at 02:36:08, Jeremy Fitzhardinge wrote:
When I run 2.6.21-rc5 + Andi's x86 patches + paravirt_ops patches,
I've been getting my machine shut down with critical thermal
shutdown messages:
Mar 30 23:19:03 localhost kernel: ACPI: Critical trip point
Mar 30 23:19:03 localhost ke
Hi!
> > CONFIG_I2C=m
> > CONFIG_I2C_ALGOBIT=m
> > CONFIG_I2C_ALGOPCA=m
> > CONFIG_I2C_I810=m
> > CONFIG_I2C_PIIX4=m
> > CONFIG_SENSORS_DS1337=m
> > CONFIG_SENSORS_DS1374=m
> > CONFIG_SENSORS_EEPROM=m
> > CONFIG_SENSORS_PCF8574=m
> > CONFIG_SENSORS_PCA9539=m
> > CONFIG_SENSORS_PCF8591=m
> > CONFIG_
Hi!
> > When I run 2.6.21-rc5 + Andi's x86 patches + paravirt_ops patches, I've
> > been getting my machine shut down with critical thermal shutdown messages:
>
> Hmm, don't think there's anything either in x86 that would touch this code.
> But can you double check with plain rc5?
>
> > Mar 30
On Sat, Mar 31, 2007 at 11:28:46PM -0700, Jeremy Fitzhardinge wrote:
> That seems to have helped. If I watch
> /proc/acpi/thermal_zone/THM?/temperature, it seems stable even under
> load. I didn't try watching the thermal_zones when these options were
> enabled, but I presume the temperature wa
Alexey Starikovskiy wrote:
> Could you try to unload or disable hardware sensors and check if it
> helps?
> CONFIG_I2C=m
> CONFIG_I2C_ALGOBIT=m
> CONFIG_I2C_ALGOPCA=m
> CONFIG_I2C_I810=m
> CONFIG_I2C_PIIX4=m
> CONFIG_SENSORS_DS1337=m
> CONFIG_SENSORS_DS1374=m
> CONFIG_SENSORS_EEPROM=m
> CONFIG_SENS
On Saturday 31 March 2007 08:36, Jeremy Fitzhardinge wrote:
> When I run 2.6.21-rc5 + Andi's x86 patches + paravirt_ops patches, I've
> been getting my machine shut down with critical thermal shutdown messages:
Hmm, don't think there's anything either in x86 that would touch this code.
But can you
When I run 2.6.21-rc5 + Andi's x86 patches + paravirt_ops patches, I've
been getting my machine shut down with critical thermal shutdown messages:
Mar 30 23:19:03 localhost kernel: ACPI: Critical trip point
Mar 30 23:19:03 localhost kernel: Critical temperature reached (128 C),
shutting down.
Mar
18 matches
Mail list logo
