mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: perf: fuzzer: spinlock hang
Date: Wed, 17 Aug 2016 17:40:49 +0200	[thread overview]
Message-ID: <20160817154049.GU30192@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1608091140090.14556@macbook-air>

On Tue, Aug 09, 2016 at 11:51:48AM -0400, Vince Weaver wrote:
> 
> So still haswell/4.8-rc1, after 6 hours of fuzzing this is where the 
> system finally locked up permanently.
> 
> It looks like some sort of spinlock error.
> The logs continued being spammed with this stuff overnight until I 
> finally put it out of its misery, but I think just the beginning here
> is the relevant part.

That sadly looks vaguely familiar... I think its the point where I gave
up chasing bugs last year, because I was going soft in the head staring
at this stuff for several months non-stop.

It taking several hours to reproduce didn't help.

I suspect its something iffy with the Intel driver, because I could
never trigger it on AMD, but of course, no guarantees ...

I'll try and find some time again to chase this down once Alexander
sorts that AUX issue.

  reply	other threads:[~2016-08-17 15:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 15:51 Vince Weaver
2016-08-17 15:40 ` Peter Zijlstra [this message]
2016-08-18  4:36   ` 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=20160817154049.GU30192@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®