[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160301112013.GR6357@twins.programming.kicks-ass.net>
Date: Tue, 1 Mar 2016 12:20:13 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: "Liang, Kan" <kan.liang@...el.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Ingo Molnar <mingo@...nel.org>,
Andi Kleen <andi@...stfloor.org>,
Stephane Eranian <eranian@...gle.com>,
Wang Nan <wangnan0@...wei.com>,
"zheng.z.yan@...el.com" <zheng.z.yan@...el.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] Core2 cpu triggers hard lockup with perf test
On Tue, Mar 01, 2016 at 12:06:51PM +0100, Jiri Olsa wrote:
> >
> > [ Jiri, can you disable that stupid panic on hard lockup and let it run
> > for a while, see if all the lockup msgs hit the same IP? Also, can you
> > look where exactly that IP lives in the code? ]
>
> im on it..
Thanks!
> also the patch that makes this happen just
> enlarge the buffer for PEBS:
>
> 156174999dd1 perf/intel/x86: Enlarge the PEBS buffer
>
> but I did not find anyaPEBS buffer lenght limitations in SDM
Probably just makes it easier to tickle.
Powered by blists - more mailing lists