[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160315153830.GA6356@twins.programming.kicks-ass.net>
Date: Tue, 15 Mar 2016 16:38:30 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Vince Weaver <vince@...ter.net>
Cc: mingo@...nel.org, alexander.shishkin@...ux.intel.com,
eranian@...gle.com, linux-kernel@...r.kernel.org,
dvyukov@...gle.com, andi@...stfloor.org, jolsa@...hat.com,
panand@...hat.com, sasha.levin@...cle.com, oleg@...hat.com,
Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH 00/12] perf: more fixes
On Thu, Mar 10, 2016 at 09:44:30AM -0500, Vince Weaver wrote:
> On Thu, 10 Mar 2016, Peter Zijlstra wrote:
>
> > On Wed, Feb 24, 2016 at 06:45:39PM +0100, Peter Zijlstra wrote:
> >
> > Boris, who has been running syz-kaller on AMD hardware and was hitting a
> > very similar bug with the AMD-IBS code, says its not fixed it for him,
> > so maybe there's still more to find.
>
> sorry I am not being much help with this big syz-kaller bug hunt, but I
> just wanted to chime in that there's a (probably the same) long standing
> IBS bug that perf_fuzzer hits all the time too, it was bad enough
> that I had to stop running perf_fuzzer on my AMD box.
Running perf_fuzzer on that AMD box is still producing lots of fail, I
seen long strings of dazed and confused msgs, indicating we have a
'spurious' NMI problem somewhere.
And occasionally it locks up..
So we're not there yet.
Powered by blists - more mailing lists