Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1290679 > unrolled thread

Linux v3.11 and v3.12 bugs - history question

Started byJeff Merkey <linux.mdb@gmail.com>
First post2015-12-13 20:30 +0100
Last post2015-12-13 22:00 +0100
Articles 3 — 1 participant

Back to article view | Back to linux.kernel

Contents

  Linux v3.11 and v3.12 bugs - history question Jeff Merkey <linux.mdb@gmail.com> - 2015-12-13 20:30 +0100
    Re: Linux v3.11 and v3.12 bugs - history question Jeff Merkey <linux.mdb@gmail.com> - 2015-12-13 21:40 +0100
      Re: Linux v3.11 and v3.12 bugs - history question Jeff Merkey <linux.mdb@gmail.com> - 2015-12-13 22:00 +0100

#1290679 — Linux v3.11 and v3.12 bugs - history question

FromJeff Merkey <linux.mdb@gmail.com>
Date2015-12-13 20:30 +0100
SubjectLinux v3.11 and v3.12 bugs - history question
Message-ID<qFkvg-433-13@gated-at.bofh.it>
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/

[toc] | [next] | [standalone]

#1290693

FromJeff Merkey <linux.mdb@gmail.com>
Date2015-12-13 21:40 +0100
Message-ID<qFlAZ-4IZ-1@gated-at.bofh.it>
In reply to#1290679
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 <linux.mdb@gmail.com> 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/

[toc] | [prev] | [next] | [standalone]

#1290702

FromJeff Merkey <linux.mdb@gmail.com>
Date2015-12-13 22:00 +0100
Message-ID<qFlUm-4PZ-11@gated-at.bofh.it>
In reply to#1290693
I found it.  Added to the patches -- fixed.  Different incarnation of
the bug in 3.12 vs. 3.11 -- same bug though ...



On 12/13/15, Jeff Merkey <linux.mdb@gmail.com> wrote:
> 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 <linux.mdb@gmail.com> 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/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web