public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: mingo@elte.hu, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: excessive MSR print out during boot.
Date: Thu, 22 Mar 2012 23:52:56 -0400	[thread overview]
Message-ID: <20120323035256.GA12180@redhat.com> (raw)
In-Reply-To: <CAE9FiQVJo_Oik-EThFyLVu15ULOKRVzr7HtM03KxXz0D3_gpBQ@mail.gmail.com>

On Thu, Mar 22, 2012 at 07:16:24PM -0700, Yinghai Lu wrote:
 > On Thu, Mar 22, 2012 at 7:00 PM, Dave Jones <davej@redhat.com> wrote:
 > > During bootup, I now have 162 messages like this..
 > >
 > > [    0.227346]  MSR0000001b: 00000000fee00900
 > > [    0.227465]  MSR00000021: 0000000000000001
 > > [    0.227584]  MSR0000002a: 00000000c1c81400
 > >
 > > commit 21c3fcf3e39353d4f21d50e257cc74f3204b1988 looks suspect.
 > > It claims that it will only print these out if show_msr= is passed,
 > > but that doesn't seem to be the case.
 > 
 > sorry abut that.
 > 
 > please check attached patch.
 > 
 > Thanks
 > 
 > Yinghai

 > diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
 > index ade9c79..b240323 100644
 > --- a/arch/x86/kernel/cpu/common.c
 > +++ b/arch/x86/kernel/cpu/common.c
 > @@ -998,7 +998,7 @@ void __cpuinit print_cpu_info(struct cpuinfo_x86 *c)
 >  	else
 >  		printk(KERN_CONT "\n");
 >  
 > -	__print_cpu_msr();
 > +	print_cpu_msr(c);
 >  }
 >  
 >  void __cpuinit print_cpu_msr(struct cpuinfo_x86 *c)

Looks like that did the trick, thanks!

Tested-by: Dave Jones <davej@redhat.com>

	Dave

      reply	other threads:[~2012-03-23  3:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-23  2:00 excessive MSR print out during boot Dave Jones
2012-03-23  2:16 ` Yinghai Lu
2012-03-23  3:52   ` Dave Jones [this message]

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=20120323035256.GA12180@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=yinghai@kernel.org \
    /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