Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751458AbaLERPp (ORCPT ); Fri, 5 Dec 2014 12:15:45 -0500 Received: from mx1.redhat.com ([209.132.183.28]:41884 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750965AbaLERPn (ORCPT ); Fri, 5 Dec 2014 12:15:43 -0500 Date: Fri, 5 Dec 2014 12:15:01 -0500 From: Dave Jones To: Linus Torvalds Cc: Chris Mason , Mike Galbraith , Ingo Molnar , Peter Zijlstra , =?iso-8859-1?Q?D=E2niel?= Fraga , Sasha Levin , "Paul E. McKenney" , Linux Kernel Mailing List Subject: Re: frequent lockups in 3.18rc4 Message-ID: <20141205171501.GA1320@redhat.com> Mail-Followup-To: Dave Jones , Linus Torvalds , Chris Mason , Mike Galbraith , Ingo Molnar , Peter Zijlstra , =?iso-8859-1?Q?D=E2niel?= Fraga , Sasha Levin , "Paul E. McKenney" , Linux Kernel Mailing List References: <547bbe36.48548c0a.105c.779c@mx.google.com> <20141201191431.GA17385@linux.vnet.ibm.com> <547ccf74.a5198c0a.25de.26d9@mx.google.com> <20141201230339.GA20487@ret.masoncoding.com> <1417529606.3924.26.camel@maggy.simpson.net> <1417540493.21136.3@mail.thefacebook.com> <20141203184111.GA32005@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 03, 2014 at 10:45:57AM -0800, Linus Torvalds wrote: > On Wed, Dec 3, 2014 at 10:41 AM, Dave Jones wrote: > > > > I've been stuck on this kernel for a few days now trying to prove it > > good/bad one way or the other, and I'm leaning towards good, given > > that it recovers, even though the traces look similar. > > Ugh. But this does *not* happen with 3.16, right? Even the non-fatal case? > > If so, I'd be inclined to call it "bad". But there might well be two > bugs: one that makes that NMI watchdog trigger, and another one that > then makes it be a hard lockup. I'd think it would be good to figure > out the "NMI watchdog starts triggering" one first, though. A bisect later, and I landed on a kernel that ran for a day, before spewing NMI messages, recovering, and then.. http://codemonkey.org.uk/junk/log.txt I could log in, but every command I tried (even shell built-ins) just printed 'bus error'. I saw those end_request messages in an earlier bisect, I wonder if there was an actual bug that got fixed where allowed non-root to try and do bad things to raw devices. It's always sector 0 too. Yet again, I'm wondering if this whole thing is just signs of early hardware death. Dave -- 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/