[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20151204104815.GA21529@pd.tnic>
Date: Fri, 4 Dec 2015 11:48:15 +0100
From: Borislav Petkov <bp@...e.de>
To: kernel test robot <ying.huang@...ux.intel.com>,
Tony Luck <tony.luck@...el.com>
Cc: Andi Kleen <ak@...ux.intel.com>, lkp@...org,
LKML <linux-kernel@...r.kernel.org>,
linux-edac <linux-edac@...r.kernel.org>,
Tony Luck <tony.luck@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: [lkp] [x86/mce] 81ffdcdd97:
kmsg.CPU61:Package_temperature_above_threshold,cpu_clock_throttled(total_events=#)
On Fri, Dec 04, 2015 at 09:20:39AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 81ffdcdd97d94110627caa81c23d5d780083731d ("x86/mce: Fix thermal throttling reporting after kexec")
>
> This may be the intended behavior, just FYI.
Should be...
Let me get this straight - before this commit, the messages don't
appear, yes?
Looking at the hunk and AFAICT, it checks APIC_LVTTHMR[VEC] and it did
bail out if something was there != 0 before.
With this check removed, we go and actually init.
So I can imagine BIOS programming stuff in it already and us not even
initializing thermal throttling due to that. And this commit actually
*fixed* it on baremetal too.
But that would be crazy, BIOS would never do something like that?!</sarcasm>
Tony?
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists