Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752427AbbLMUbE (ORCPT ); Sun, 13 Dec 2015 15:31:04 -0500 Received: from mail-ig0-f195.google.com ([209.85.213.195]:36393 "EHLO mail-ig0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752080AbbLMUbD (ORCPT ); Sun, 13 Dec 2015 15:31:03 -0500 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 13 Dec 2015 13:31:01 -0700 Message-ID: Subject: Re: Linux v3.11 and v3.12 bugs - history question From: Jeff Merkey To: gregkh@linuxfoundation.org, LKML Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1953 Lines: 51 Hi Greg, I think I found it. Going back through all the commits on linux-stable. I love this git thing, it's totally fucking cool. What a great idea, it's such a time and labor saving tool, it only took me ten years to start using it. Jeff On 12/13/15, Jeff Merkey wrote: > Hi Greg, > > You might know the answer to this and save me days of running down > bugs in old kernels. > > I am completing full regression testing of the mdb debugger on all > linux versions back to 2.6.37 and I am am almost done. I've > encountered some nasty bugs in these two linux release lines. These > bugs are documented all over the web about these versions. > > https://forum.blackmagicdesign.com/viewtopic.php?f=12&t=37186 > https://bugzilla.redhat.com/show_bug.cgi?id=990955 > https://lkml.org/lkml/2013/8/12/31 > > I would like to put a fix into my patches for them to make them stable > enough to use. The bug is: > > BUG: scheduling while atomic: swapper/0/0/0x10000100 > > across several functions which shows up when I have held the > processsors in the debugger for several minutes but only if I take a > breakpoint AT INTERRUPT. It does not show up otherwise. It shows > up when I exit the debugger on either v3.11 or v3.12. > > I've tracked it down to a linux bug, and it does not affect any other > versions. > > Do you recall what caused this bug (I have seen comments its in > several drivers) and point me to the commit that fixed it or thread > because as near as I can tell, it affects these versions ONLY. I have > seen the "BUG scheduling while atomic" fire off on other functions on > these versions but only on these two releases. > > Any help would be appreciated. > -- 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/