diff options
| author | Dmitry Torokhov <dmitry.torokhov@gmail.com> | 2009-08-09 21:44:49 -0700 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2009-08-11 09:54:17 +0200 |
| commit | 0d01f31439c1e4d602bf9fdc924ab66f407f5e38 (patch) | |
| tree | ab877b3089ac4202d113e4d77d1ed9c511527022 /include/linux/console_struct.h | |
| parent | 3e03bbeac541856aaaf1ce1ab0250b6a490e4099 (diff) | |
| download | kernel-crypto-0d01f31439c1e4d602bf9fdc924ab66f407f5e38.tar.gz kernel-crypto-0d01f31439c1e4d602bf9fdc924ab66f407f5e38.tar.xz kernel-crypto-0d01f31439c1e4d602bf9fdc924ab66f407f5e38.zip | |
x86, mce: therm_throt - change when we print messages
My Latitude d630 seems to be handling thermal events in SMI by
lowering the max frequency of the CPU till it cools down but
still leaks the "everything is normal" events.
This spams the console and with high priority printks.
Adjust therm_throt driver to only print messages about the fact
that temperatire returned back to normal when leaving the
throttling state.
Also lower the severity of "back to normal" message from
KERN_CRIT to KERN_INFO.
Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
Acked-by: H. Peter Anvin <hpa@zytor.com>
LKML-Reference: <20090810051513.0558F526EC9@mailhub.coreip.homeip.net>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'include/linux/console_struct.h')
0 files changed, 0 insertions, 0 deletions