public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Frans Pop <elendil@planet.nl>
Cc: Trevor Hemsley <trevor.hemsley@ntlworld.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Temperature above threshold loop with 2.6.31.1
Date: Fri, 2 Oct 2009 19:57:45 +0200	[thread overview]
Message-ID: <20091002175745.GB14860@elte.hu> (raw)
In-Reply-To: <200910021938.09486.elendil@planet.nl>


* Frans Pop <elendil@planet.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@elte.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@elte.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

  reply	other threads:[~2009-10-02 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 13:42 Temperature above threshold loop with 2.6.31.1 Trevor Hemsley
2009-10-02 15:03 ` Frans Pop
2009-10-02 17:05   ` Ingo Molnar
2009-10-02 17:38   ` Frans Pop
2009-10-02 17:57     ` Ingo Molnar [this message]
2009-10-03 19:28       ` Trevor Hemsley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091002175745.GB14860@elte.hu \
    --to=mingo@elte.hu \
    --cc=elendil@planet.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trevor.hemsley@ntlworld.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox