From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Stephane Eranian <eranian@gmail.com>,
kan.liang@intel.com
Subject: Re: perf: fuzzer triggered CPU lockup
Date: Fri, 3 Jul 2015 12:08:09 +0200 [thread overview]
Message-ID: <20150703100809.GF19282@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1507022327020.16899@vincent-weaver-1.umelst.maine.edu>
On Thu, Jul 02, 2015 at 11:31:15PM -0400, Vince Weaver wrote:
> On Thu, 2 Jul 2015, Vince Weaver wrote:
>
> > The fuzzer just turned this up. This is the first part; a huge amount of
> > CPU lockup messages, rcu stalls, and spinlock lockup suspected messages
> > followed beyond what I've posted here but eventually the machine recovered (?)
>
> > [20602.134103] [<ffffffff8102f676>] ? intel_pmu_drain_pebs_nhm+0x176/0x2e0
>
> after a reboot I am still getting these, in addition to the other
> intel_pmu_drain_pebs_nhm related warning. Do I need to try to bisect this
> down?
I think I have a fairly good idea which patches to blame for that;
there's been a rework of the pebs code there. Let me go have a look.
prev parent reply other threads:[~2015-07-03 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 21:02 perf: fuzzer triggered CPU lockup Vince Weaver
2015-07-03 3:31 ` Vince Weaver
2015-07-03 10:08 ` Peter Zijlstra [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=20150703100809.GF19282@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=eranian@gmail.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.