Overheat event self fullfilling nightmare

[Faye Pearson <faye-6JSjyQ0Qj1ReoWH0uzbU5w@public.gmane.org>]

We've had some hot weather recently, this combined with me playing with
GLX on my laptop has meant I discovered the joys of CPU overheat.

Or rather.. not.

When the CPU gets hot enough to cause an event, it sends the event,
sends the event again, ad infinitum.  This causes the machine to run at
a load average which builds to 2.0 just trying to handle all these
events.

Is this a problem with my DSDT - not just sending the event *on* the
threshold but continuing while it's over - probably.

Is this also a problem with ACPI not limiting the number of repeat
events being logged?  I think it should accept n same events in m
seconds and flush remaining events of the same type until a different
event happens.

Any other opinions?  Any ideas where I should start looking in the DSDT
to find the code which manages this?


Faye

-- 
Faye Pearson,
Software Development Manager,
ClaraNET Ltd.       Tel 020 7903 3000

narcolepulacyi, n.:
	The contagious action of yawning, causing everyone in sight
	to also yawn.
		-- "Sniglets", Rich Hall & Friends


-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone?  Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390