On Wed, Jun 3, 2009 at 5:12 AM, Ben Hutchings<ben@decadent.org.uk> wrote:
You found some scheduling changes made post-2.6.28 which seemed to deal
with this bug. However, that cannot be the full story because they are
modifying code which was added after 2.6.26.
The attached patch combines a bug fix made between 2.6.26 and .28 with
most of the changes you identified. Based on my reading of commit
messages and discussion, I think this makes a coherent set of changes.
However there have been many other changes to the scheduler in this time
and I cannot say for sure whether any of those are also required as I do
not have any great knowledge of it.
Please try rebuilding the "lenny" kernel (linux-source-2.6.26) with this
patch applied and report whether it fixes the bug for you.
Thank you for response!
I've applied the patch to most recent lenny kernel and booted it. If
in two weeks the problem does not occur, I will assume that the bug is
gone (I will let you know).
Thanks again!