Ticket #945 (closed task)

Opened 7 years ago

Xeon p4 shut down due to overheating (Examined/Solved - lm-sensors 2.6.3-5/linux 2.4.18-smp)

Reported by: contact Owned by: somebody
Priority: minor Milestone:
Component: hardware Version:
Keywords: Cc:

Description

Greetings,

Recently added a second xeon p4 1.7 processor to our workstation at same time

added lm-sensors package. After about 5 min of heavy use the computer would

shut down due to a "thermal event" Dell replaced the cpus twice and then the

motherboard (service contracts are nice). After carefully rereading the docs, I

see that xeon support is alpha. My computer is reading 2 temp numbers for each

processor, I believe it is the second higher number that is triggering the

shutdown. Any ideas on disabling this? I could set the temp limit higher, but

is this the right thing to do?

Thanks,

David:x

Sorry, I forgot to mention that I'm talking about the adm1021(max1617) chip.

# I2C module options

alias char-major-89 i2c-dev

options adm1021 ignore=1,0x18

Also, how do the original max and min values for this chip get set

(min=20,max=60)? The 'set' statement for this chip is commented out

in

sensors.conf. I guess what I'm asking is, how is that the computer

runs fine

without the lm-sensors modules, but upon inserting adm1021 into the

kernel, the

computer is now poised to shutdown after several minutes of hard cpu

use.

Thanks again,

David

:x

--- The xeon looks like a adm1021 with only one sensor instead of two.

We should probably do a separate driver but we haven't yet.

The adm1021 driver sets the initial limits, it's hardcoded.

And there's currently no way to change it or disable the

initialization other than recompiling. Sorry.

If you either change the limits in the driver or

uncomment the limits in sensors.conf and run

sensors -s after inserting the module you should be OK.

You may wish to contact

Philip Pokorny <ppokorny@…>,

he has a separate driver he is working on.

Follow up via email, ref. your ticket #

MDS 6/23/02

Note: See TracTickets for help on using tickets.