diff options
| author | Duncan Laurie <dlaurie@chromium.org> | 2012-07-16 14:40:50 -0700 |
|---|---|---|
| committer | Gerrit <chrome-bot@google.com> | 2012-07-16 17:49:10 -0700 |
| commit | a42edb86c59cbc145eb99bd5b65bbd1f5567320e (patch) | |
| tree | c3e59e99ec54c2f1872adee930a66fac16f29c5a /common/thermal.c | |
| parent | 0e6daeb6ab5c8d27163be2f7350f5de56276a6ad (diff) | |
| download | chrome-ec-a42edb86c59cbc145eb99bd5b65bbd1f5567320e.tar.gz | |
Print console messages for overtemp and shutdown
I have a system with bad temperature sensors and the EC is
constantly shutting the system down, but provides no
visible indication that it is doing so.
I have serious concerns about the EC behavior in this case
as it seems to be doing things it shouldn't. However just
providing indication via the console about what it is doing
is at least useful for development and debug.
BUG=none
TEST=boot on system with bad temp sensors and see that
the EC indicates it is initiating a shutdown.
[14.008340 critical temperature; shutting down]
[14.008660 x86 power force shutdown]
[14.009153 LPC RESET# asserted]
Change-Id: I6beeb269a135bd8c245c0357670fe29648d48968
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/27553
Reviewed-by: Randall Spangler <rspangler@chromium.org>
Diffstat (limited to 'common/thermal.c')
| -rw-r--r-- | common/thermal.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/common/thermal.c b/common/thermal.c index fa54b3123b..7d2640a1ad 100644 --- a/common/thermal.c +++ b/common/thermal.c @@ -105,6 +105,8 @@ static void smi_sensor_failure_warning(void) static void overheated_action(void) { if (overheated[THRESHOLD_POWER_DOWN]) { + cprintf(CC_CHIPSET, + "[%T critical temperature; shutting down]\n"); x86_power_force_shutdown(); return; } |