From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Paul Mackerras <paulus@samba.org>
Subject: Re: perf: another perf_fuzzer generated lockup
Date: Wed, 27 May 2015 14:52:12 +0200 [thread overview]
Message-ID: <20150527125212.GB3644@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1505080025560.26907@vincent-weaver-1.umelst.maine.edu>
On Fri, May 08, 2015 at 12:40:48AM -0400, Vince Weaver wrote:
>
> This is a new one I think, I hit it on the haswell machine running
> 4.1-rc2.
>
Vince, should I still be running fast_repro99.sh ? Or is there another
preferred way to start the beast?
next prev parent reply other threads:[~2015-05-27 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-08 4:40 perf: another perf_fuzzer generated lockup Vince Weaver
2015-05-09 0:04 ` Stephane Eranian
2015-05-11 21:19 ` Vince Weaver
2015-05-27 12:52 ` Peter Zijlstra [this message]
2015-05-27 13:58 ` Vince Weaver
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=20150527125212.GB3644@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=vincent.weaver@maine.edu \
/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