Re: Overheating is *not* dangerous Re: Changing temperature trip points

Pavel Machek
2002-11-03T22:38:22Z

Hi!

> The point that I, and it would seem Dominik too, am trying to make is
> that you can't always rely on this sort of stuff. My laptop didn't shut
> down when it was in danger, and it doesn't have any sort of
> throttling

Your laptop is still alive, so I do not think it was in
danger. [Athlon/900 seems to work stable at 83Celsius. Celeron/300
worked stable up to 95Celsius. I do not know why you think 70Celsius
is too much for celeron].

> safeguard, nor is there anything that can be changed in the BIOS. My
> desktop allows you to set a shutdown temperature, but by default it's
> left blank, so the system would happily slag itself unless there is
> direct user intervention. User intervention is not guaranteed, nor is a
> nicely behaved BIOS that watches for this sort of thing.

*If* fan on your desktop dies (1st hardware bug), and
your ACPI bios is broken (2nd hardware bug), and
you configure trip points but forget polling frequency (2 hw bugs and
user error), and
your CPU does not have thermal protection (it has to according to ACPI
specs -- 3 hw bugs and user error)
you can cook your cpu (given its older athlon).

Okay but even if we compensated for your user error, still 3 hw bugs
and one software bug would cook your machine (kernel crash).

If hw vendor made 3 hardware errors... I guess he deserves to have
that machine cooked.
Pavel
--
Casualities in World Trade Center: ~3k dead inside the building,
cryptography in U.S.A. and free speech in Czech Republic.