From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Frederic Weisbecker <fweisbec@gmail.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 17:17:31 +0100 [thread overview]
Message-ID: <20100912161730.GA30698@sucs.org> (raw)
In-Reply-To: <20100912130637.GB5342@nowhere>
On Sun, Sep 12, 2010 at 03:06:39PM +0200, Frederic Weisbecker wrote:
>
> 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.
OK.
> 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.
An EeePC has only one CPU (so it's strictly UP only).
--
Sitsofe | http://sucs.org/~sits/
prev parent reply other threads:[~2010-09-12 16:17 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
2010-09-12 16:17 ` Sitsofe Wheeler [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=20100912161730.GA30698@sucs.org \
--to=sitsofe@yahoo.com \
--cc=corentincj@iksaif.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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