Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965408AbaLKWBj (ORCPT ); Thu, 11 Dec 2014 17:01:39 -0500 Received: from userp1040.oracle.com ([156.151.31.81]:19275 "EHLO userp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965310AbaLKWBi (ORCPT ); Thu, 11 Dec 2014 17:01:38 -0500 Message-ID: <548A141B.4000608@oracle.com> Date: Thu, 11 Dec 2014 17:00:59 -0500 From: Sasha Levin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Chris Mason CC: Linus Torvalds , Dave Jones , Mike Galbraith , Ingo Molnar , Peter Zijlstra , =?UTF-8?B?RMOibmllbCBGcmFnYQ==?= , "Paul E. McKenney" , Linux Kernel Mailing List Subject: Re: frequent lockups in 3.18rc4 References: <20141201230339.GA20487@ret.masoncoding.com> <1417529606.3924.26.camel@maggy.simpson.net> <1417540493.21136.3@mail.thefacebook.com> <20141203184111.GA32005@redhat.com> <20141205171501.GA1320@redhat.com> <1417806247.4845.1@mail.thefacebook.com> <20141211145408.GB16800@redhat.com> <548A122C.8000906@oracle.com> <1418335052.4845.17@mail.thefacebook.com> In-Reply-To: <1418335052.4845.17@mail.thefacebook.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Source-IP: ucsinet21.oracle.com [156.151.31.93] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/11/2014 04:57 PM, Chris Mason wrote: > On Thu, Dec 11, 2014 at 4:52 PM, Sasha Levin wrote: >> On 12/11/2014 04:49 PM, Linus Torvalds wrote: >>> On Thu, Dec 11, 2014 at 6:54 AM, Dave Jones wrote: >>>> > >>>> > So either one of those 'good's actually wasn't, or I'm just cursed. >>> Even if there was a good that wasn't, that last "bad" (6f929b4e5a02) >>> is already sufficient just on its own to say that likely v3.16 already >>> had the problem. >>> >>> Just do >>> >>> gitk v3.16..6f929b4e5a02 >>> >>> and cry. >>> >>> (or "git diff --stat -M v3.16...6f929b4e5a02" to see what that commit >>> brought in from the common ancestor). >>> >>> So I'd call that bisect a failure, and your "v3.16 is fine" is >>> actually suspect after all. Which *might* mean that it's some hardware >>> issue after all. Or there are multiple different problems, and while >>> v3.16 was fine, the problem was introduced earlier (in the common >>> ancestor of that staging tree), then fixed for 3.16, and then >>> re-introduced later again. >> >> Is it possible that Dave and myself were seeing the same problem after >> all? >> >> I'll go bisect it even further back... > > For both of you, I'm curious how long 3.18 lasts if you turn off the serial console (and netconsole) completely. I didn't try turning it off, but I tried switching debug level to critical which meant that nothing was going out. I still saw the same hang... Thanks, Sasha -- 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/