From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Steven Noonan <steven@uplinklabs.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@elte.hu>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: bisected: 'perf top' causing soft lockups under Xen
Date: Fri, 10 Feb 2012 17:29:01 -0200 [thread overview]
Message-ID: <20120210192901.GK2526@infradead.org> (raw)
In-Reply-To: <CAKbGBLgj-k7=Oqy8JD1Dcuj_YRjP3H_7nV9a4Q8fCaMmyA5LTA@mail.gmail.com>
Em Fri, Feb 10, 2012 at 11:27:23AM -0800, Steven Noonan escreveu:
> > [ 160.172856] iwlwifi 0000:02:00.0: L1 Enabled; Disabling L0S
> > [ 160.172984] iwlwifi 0000:02:00.0: Radio type=0x1-0x2-0x0
>
> It actually gets even more interesting. Once I did 'perf test' under
> Xen, and I waited for it to finish, perf suddenly works fine. I can
> re-run 'perf test -v 3' with no hangs, and can now run 'perf top' with
> no issue. Bizarre.
Heck, I keep wishing people use perf test more often to figure out bugs
sooner, but this side effect was surprising! ;-)
- Arnaldo
prev parent reply other threads:[~2012-02-10 19:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 2:32 bisected: 'perf top' causing soft lockups under Xen Steven Noonan
2012-02-10 16:12 ` Konrad Rzeszutek Wilk
2012-02-10 17:24 ` Peter Zijlstra
2012-02-10 17:28 ` Peter Zijlstra
2012-02-10 19:04 ` Konrad Rzeszutek Wilk
2012-02-11 2:34 ` Ben Guthro
2012-02-12 20:50 ` Steven Noonan
2012-02-15 8:57 ` Steven Noonan
2012-02-15 9:25 ` Peter Zijlstra
2012-02-15 9:32 ` Steven Noonan
2012-02-15 17:14 ` Konrad Rzeszutek Wilk
2012-02-15 16:17 ` Konrad Rzeszutek Wilk
2012-03-20 15:23 ` Konrad Rzeszutek Wilk
2012-03-20 15:33 ` Peter Zijlstra
2012-02-10 19:14 ` Steven Noonan
2012-02-10 19:27 ` Steven Noonan
2012-02-10 19:29 ` Arnaldo Carvalho de Melo [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=20120210192901.GK2526@infradead.org \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=steven@uplinklabs.net \
/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;
as well as URLs for NNTP newsgroup(s).