From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752901AbcHQPkv (ORCPT ); Wed, 17 Aug 2016 11:40:51 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:40022 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752145AbcHQPku (ORCPT ); Wed, 17 Aug 2016 11:40:50 -0400 Date: Wed, 17 Aug 2016 17:40:49 +0200 From: Peter Zijlstra To: Vince Weaver Cc: linux-kernel@vger.kernel.org, Alexander Shishkin , Ingo Molnar , Arnaldo Carvalho de Melo Subject: Re: perf: fuzzer: spinlock hang Message-ID: <20160817154049.GU30192@twins.programming.kicks-ass.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.