From: Frederic Weisbecker <fweisbec@gmail.com>
To: Sitsofe Wheeler <sitsofe@yahoo.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Corentin Chary <corentincj@iksaif.net>
Subject: Re: EeePC 900 reboots/hangs when using using perf -a -f -g
Date: Sun, 12 Sep 2010 15:06:39 +0200 [thread overview]
Message-ID: <20100912130637.GB5342@nowhere> (raw)
In-Reply-To: <20100912112105.GA28420@sucs.org>
On Sun, Sep 12, 2010 at 12:21:05PM +0100, Sitsofe Wheeler wrote:
> On Sun, Sep 12, 2010 at 12:57:07PM +0200, Peter Zijlstra wrote:
> >
> > Bisect it?
>
> .35 shows the same issue (although I didn't recompile my perf binary). I
> don't know if this is a regression - it might always have been there...
Testing with a software event like page faults will test if it's related
to hardware events only or some of them.
For example if it doesn't happen in fault events, then let's try with some
others, just to see if we can narrow down to some particular events.
If it happens on faults it will be easier to debug because software events
don't happen in NMI (at least not the faults), so enabling RCU stalls checks
there will probably success to trigger a backtrace. Perhaps you can profile
only one CPU for that (-C 1, eeepc 900 are SMT, right?), so that there is
a free CPU to notice the stall and trigger the backtrace through remote NMIs.
next prev parent reply other threads:[~2010-09-12 13:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-12 10:28 EeePC 900 reboots/hangs when using using perf -a -f -g Sitsofe Wheeler
2010-09-12 10:57 ` Peter Zijlstra
2010-09-12 11:21 ` Sitsofe Wheeler
2010-09-12 12:46 ` Frederic Weisbecker
2010-09-12 16:21 ` Sitsofe Wheeler
2010-09-17 3:01 ` Frederic Weisbecker
2010-09-21 17:27 ` Sitsofe Wheeler
2010-10-02 21:03 ` Frederic Weisbecker
2010-10-24 12:50 ` Sitsofe Wheeler
2010-09-12 13:06 ` Frederic Weisbecker [this message]
2010-09-12 16:17 ` Sitsofe Wheeler
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=20100912130637.GB5342@nowhere \
--to=fweisbec@gmail.com \
--cc=corentincj@iksaif.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sitsofe@yahoo.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