Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1176462 > unrolled thread

Re: perf: fuzzer triggered CPU lockup

Started byPeter Zijlstra <peterz@infradead.org>
First post2015-07-03 12:10 +0200
Last post2015-07-03 12:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: perf: fuzzer triggered CPU lockup Peter Zijlstra <peterz@infradead.org> - 2015-07-03 12:10 +0200

#1176462 — Re: perf: fuzzer triggered CPU lockup

FromPeter Zijlstra <peterz@infradead.org>
Date2015-07-03 12:10 +0200
SubjectRe: perf: fuzzer triggered CPU lockup
Message-ID<pI64V-7ct-13@gated-at.bofh.it>
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web