MIME-Version: 1.0
Date: Sun, 13 Dec 2015 12:27:51 -0700
Message-ID: <CAO6TR8UFD+rVZfZxbiaQnxvaTtzp8p8L4N2GtAfGGktH+6t7gQ@mail.gmail.com>
Subject: Linux v3.11 and v3.12 bugs - history question
From: Jeff Merkey <linux.mdb@gmail.com>
To: gregkh@linuxfoundation.org, LKML <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1591
Lines: 39

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/