http://bugzilla.opensuse.org/show_bug.cgi?id=1194083 Bug ID: 1194083 Summary: Package temperature above threshold, cpu clock throttled Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: openSUSE Leap 15.3 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: opendreas@gmail.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 854816 --> http://bugzilla.opensuse.org/attachment.cgi?id=854816&action=edit dmesg On boot and shutdown I get the following warnings [3.207895] mce: CPU0: Core temperature above threshold, cpu clock throttled (total events = 1) [3.207896] mce: CPU6: Core temperature above threshold, cpu clock throttled (total events = 1) [3.207897] mce: CPU6: Package temperature above threshold, cpu clock throttled (total events = 1) [3.207932] mce: CPU0: Package temperature above threshold, cpu clock throttled (total events = 1) [3.207939] mce: CPU9: Package temperature above threshold, cpu clock throttled (total events = 1) [3.207941] mce: CPU8: Package temperature above threshold, cpu clock throttled (total events = 1) [3.207942] mce: CPU2: Package temperature above threshold, cpu clock throttled (total events = 1) [3.207943] mce: CPU3: Package temperature above threshold, cpu clock throttled (total events = 1) [3.207944] mce: CPU7: Package temperature above threshold, cpu clock throttled (total events = 1) [3.207945] mce: CPU1: Package temperature above threshold, cpu clock throttled (total events = 1) [3.207947] mce: CPU5: Package temperature above threshold, cpu clock throttled (total events = 1) [3.207948] mce: CPU11: Package temperature above threshold, cpu clock throttled (total events = 1) [3.207949] mce: CPU4: Package temperature above threshold, cpu clock throttled (total events = 1) [3.207951] mce: CPU10: Package temperature above threshold, cpu clock throttled (total events = 1) I saw many similar messages on the Internet. These warnings disappear starting with kernel 5.4, so this problem has been fixed. Is it possible to backport this fix? -- You are receiving this mail because: You are the assignee for the bug.