diff --git a/patches.suse/x86-mce-Lower-throttling-MCE-messages-priority-to-wa.patch b/patches.suse/x86-mce-Lower-throttling-MCE-messages-priority-to-wa.patch new file mode 100644 index 0000000..531fa67 --- /dev/null +++ b/patches.suse/x86-mce-Lower-throttling-MCE-messages-priority-to-wa.patch @@ -0,0 +1,60 @@ +From: Benjamin Berg +Date: Wed, 9 Oct 2019 17:54:24 +0200 +Subject: x86/mce: Lower throttling MCE messages' priority to warning +Git-commit: 9c3bafaa1fd88e4dd2dba3735a1f1abb0f2c7bb7 +Patch-mainline: 5.5-rc1 +References: git-fixes + +On modern CPUs it is quite normal that the temperature limits are +reached and the CPU is throttled. In fact, often the thermal design is +not sufficient to cool the CPU at full load and limits can quickly be +reached when a burst in load happens. This will even happen with +technologies like RAPL limitting the long term power consumption of +the package. + +Also, these limits are "softer", as Srinivas explains: + +"CPU temperature doesn't have to hit max(TjMax) to get these warnings. +OEMs ha[ve] an ability to program a threshold where a thermal interrupt +can be generated. In some systems the offset is 20C+ (Read only value). + +In recent systems, there is another offset on top of it which can be +programmed by OS, once some agent can adjust power limits dynamically. +By default this is set to low by the firmware, which I guess the +prime motivation of Benjamin to submit the patch." + +So these messages do not usually indicate a hardware issue (e.g. +insufficient cooling). Log them as warnings to avoid confusion about +their severity. + + [ bp: Massage commit mesage. ] + +Signed-off-by: Benjamin Berg +Signed-off-by: Borislav Petkov +Reviewed-by: Hans de Goede +Tested-by: Christian Kellner +Cc: "H. Peter Anvin" +Cc: Ingo Molnar +Cc: linux-edac +Cc: Peter Zijlstra +Cc: Srinivas Pandruvada +Cc: Thomas Gleixner +Cc: Tony Luck +Cc: x86-ml +Link: https://lkml.kernel.org/r/20191009155424.249277-1-bberg@redhat.com +Signed-off-by: Jiri Slaby +--- + arch/x86/kernel/cpu/mcheck/therm_throt.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +--- a/arch/x86/kernel/cpu/mcheck/therm_throt.c ++++ b/arch/x86/kernel/cpu/mcheck/therm_throt.c +@@ -185,7 +185,7 @@ static void therm_throt_process(bool new + /* if we just entered the thermal event */ + if (new_event) { + if (event == THERMAL_THROTTLING_EVENT) +- pr_crit("CPU%d: %s temperature above threshold, cpu clock throttled (total events = %lu)\n", ++ pr_warn("CPU%d: %s temperature above threshold, cpu clock throttled (total events = %lu)\n", + this_cpu, + level == CORE_LEVEL ? "Core" : "Package", + state->count); diff --git a/series.conf b/series.conf index 9378038..c368a43 100644 --- a/series.conf +++ b/series.conf @@ -53668,6 +53668,7 @@ patches.suse/s390-mm-properly-clear-page_noexec-bit-when-it-is-not-supported patches.suse/s390-always-inline-current_stack_pointer.patch patches.suse/s390-unwind-drop-unnecessary-code-around-calling-ftrace_graph_ret_addr.patch + patches.suse/x86-mce-Lower-throttling-MCE-messages-priority-to-wa.patch patches.suse/kvm-svm-serialize-access-to-the-sev-asid-bitmap.patch patches.suse/kvm-svm-guard-against-deactivate-when-performing-wbinvd-df_flush.patch patches.suse/kvm-x86-introduce-vcpu-arch-xsaves_enabled