mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stephane Eranian <eranian@google.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, peterz@infradead.org,
	markus@trippelsdorf.de, paulus@samba.org
Subject: Re: [PATCH] perf: fix assertion failure in x86_pmu_start()
Date: Tue, 07 Feb 2012 12:24:46 +0100	[thread overview]
Message-ID: <1328613886.3443.2.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> (raw)
In-Reply-To: <CABPqkBRwjwG0i+J_Qzgm+khHRD+LiT60vMEQA3w1MtPq-FFKLw@mail.gmail.com>

Le mardi 07 février 2012 à 11:40 +0100, Stephane Eranian a écrit :
> Eric,
> 
> How do you deal with that:
> 
> [    0.019998] Performance Events: PEBS fmt0+, Core2 events, Broken
> BIOS detected, complain to your hardware vendor.
> [    0.019998] [Firmware Bug]: the BIOS has corrupted hw-PMU resources
> (MSR 186 is 43003c)
> 
> Your BIOS is using a counter to count cycles for power savings tricks.
> That is conflicting
> with perf_events.

This was already discussed last year.

https://lkml.org/lkml/2011/3/24/552

Apparently all HP blades I have in my labs have the problem, whatever
option is chosen in BIOS.

On my machines, I set the BIOS to 'High performance', and cpus are on
highest available frequencies.




  reply	other threads:[~2012-02-07 11:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 20:53 Stephane Eranian
2012-02-07  8:34 ` Eric Dumazet
2012-02-07  8:41   ` Ingo Molnar
2012-02-07  8:55     ` Eric Dumazet
2012-02-07 10:25     ` Eric Dumazet
2012-02-07 10:31       ` Stephane Eranian
2012-02-07 10:36         ` Eric Dumazet
2012-02-07 10:40           ` Stephane Eranian
2012-02-07 11:24             ` Eric Dumazet [this message]
2012-02-07 11:27               ` Stephane Eranian
2012-02-07 11:36                 ` Ingo Molnar
2012-02-07 10:49         ` Ingo Molnar
2012-02-07 11:07           ` Stephane Eranian
2012-02-07  9:17   ` Stephane Eranian

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=1328613886.3443.2.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC \
    --to=eric.dumazet@gmail.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®