From: Dave Hansen <dave@sr71.net>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andi Kleen <ak@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
eranian@google.com
Subject: Re: NMIs induced by 'perf top' hogging all CPU time
Date: Fri, 10 May 2013 13:10:17 -0700 [thread overview]
Message-ID: <518D5429.3020609@sr71.net> (raw)
In-Reply-To: <20130510102911.GB31235@dyad.programming.kicks-ass.net>
On 05/10/2013 03:29 AM, Peter Zijlstra wrote:
> On Thu, May 09, 2013 at 04:29:16PM -0700, Dave Hansen wrote:
>> If I boot a recent kernel (bb9055b) and run 'perf top' on my machine, it
>> hangs. It is 100% reproducible; it happens every single time. If I'm
>> lucky, I'll get some of the hardlockup detection messages on the console.
>
> Are you implicitly saying it worked as expected on previous kernels?
Yes, it works on older kernels. 3.6.11 works, for instance.
This hardware is quite effective at finding bugs. It makes bisecting
very challenging as not a lot of random mainline versions boot.
prev parent reply other threads:[~2013-05-10 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 23:29 NMIs induced by 'perf top' hogging all CPU time Dave Hansen
2013-05-10 10:29 ` Peter Zijlstra
2013-05-10 20:10 ` Dave Hansen [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=518D5429.3020609@sr71.net \
--to=dave@sr71.net \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.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