Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933354AbaLBWKf (ORCPT ); Tue, 2 Dec 2014 17:10:35 -0500 Received: from mail-qg0-f48.google.com ([209.85.192.48]:47289 "EHLO mail-qg0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933029AbaLBWKe convert rfc822-to-8bit (ORCPT ); Tue, 2 Dec 2014 17:10:34 -0500 MIME-Version: 1.0 In-Reply-To: <547e36d1.c54ae00a.2571.fffffd13@mx.google.com> References: <20141201191431.GA17385@linux.vnet.ibm.com> <547ccf74.a5198c0a.25de.26d9@mx.google.com> <20141201230813.GE25340@linux.vnet.ibm.com> <547dec29.c71f8c0a.33d1.11d9@mx.google.com> <20141202170407.GK25340@linux.vnet.ibm.com> <547df364.236a8c0a.7b2d.ffffac67@mx.google.com> <20141202184202.GM25340@linux.vnet.ibm.com> <547e0947.c332e00a.23bf.ffffa8bd@mx.google.com> <20141202191143.GN25340@linux.vnet.ibm.com> <547e11fa.8778e00a.3439.ffffa88c@mx.google.com> <20141202205636.GQ25340@linux.vnet.ibm.com> <547e36d1.c54ae00a.2571.fffffd13@mx.google.com> Date: Tue, 2 Dec 2014 14:10:33 -0800 X-Google-Sender-Auth: mkUYAN-H2skkeUM_ZcUOU3qtyhk Message-ID: Subject: Re: frequent lockups in 3.18rc4 From: Linus Torvalds To: =?UTF-8?Q?D=C3=A2niel_Fraga?= Cc: "Paul E. McKenney" , Linux Kernel Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Dec 2, 2014 at 2:01 PM, Dâniel Fraga wrote: > > Of course! I applied your patch to 3.17 stock kernel and after > stressing it (compiling with -j8 and watching videos on Youtube) to > trigger the bug I got the following: So it appears that you can recreate this much more quickly than DaveJ can recreate his issue. The two issues may be entirely unrelated, but the it is certainly quite possible that they have some relation to each other, and the timing is intriguing, in that 3.17 seems to be the first kernel release this happened in. So at this point I think I'd ask you to just go back to your bisection that you apparently already started earlier. I take it 3.16 worked fine, and that's what you used as the good base for your bisect? Even if it's something else than what DaveJ sees (or perhaps *particularly* if it's something else), bisecting when it started would be very worthwhile. There's 13k+ commits in between 3.16 and 3.17, so a full bisect should be around 15 test-points. But judging by the timing of your emails, you can generally reproduce this relatively quickly.. Linus -- 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/