On Wed, 27 Mar 2002, Maciej W. Rozycki wrote:
> How can't it be critical? Your system is overheating. It is about to
> fail -- depending on the configuration, it'll either crash or be shut down
> by hardware (consider fire in the server room as well). Either way the
> condition should be caught ASAP, for proper steps to be taken by the OS
> and/or the operator. Otherwise it might have no second chance to get
> reported and the system will die silently -- you'll not know the reason
> until you get at the console (or its remains). It may be too late then.
I didn't mean to say that the condition was not critical, i meant that the
interrupt generated is used for notification purposes, and in its current
state the interrupt handler only provides information rather than taking
measures due to the condition. The condition in this case is handled
automatically by the hardware and we just receive notification via an
interrupt getting triggered. However i have taken your suggestion and
moved the vector.
Cheers,
Zwane
--
http://function.linuxpower.ca
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Mar 31 2002 - 22:00:13 EST