| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 2 Oct 2009 19:57:45 +0200 From: Ingo Molnar <mingo@...e.hu> To: Frans Pop <elendil@...net.nl> Cc: Trevor Hemsley <trevor.hemsley@...world.com>, linux-kernel@...r.kernel.org Subject: Re: Temperature above threshold loop with 2.6.31.1 * Frans Pop <elendil@...net.nl> wrote: > On Friday 02 October 2009, Frans Pop wrote: > > Trevor Hemsley wrote: > > > 1,666 notifications a second seems a little on the 'too frequent' side > > > of things to me :-) > > > > Looks like this may already be fixed in mainline by the following > > commit: commit b417c9fd8690637f0c91479435ab3e2bf450c038 > > Author: Ingo Molnar <mingo@...e.hu> > > Date: Tue Sep 22 15:50:24 2009 +0200 > > x86: mce: Fix thermal throttling message storm > > > > Can you confirm that please, either by compiling current git or by > > applying that commit on top of 2.6.31.1? > > If you want to apply it to .31.1 you'll also need this commit: > commit 3967684006f30c253bc6d4a6604d1bad4a7fc672 > Author: Ingo Molnar <mingo@...e.hu> > Date: Tue Sep 22 15:50:24 2009 +0200 > x86: mce: Clean up thermal throttling state tracking code Yes. The way to test this is to do this on top of a .31.1 tree: git cherry-pick 3967684006f30c253bc6d4a6604d1bad4a7fc672 git cherry-pick b417c9fd8690637f0c91479435ab3e2bf450c038 Ingo -- 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