On Thu, 2009-06-11 at 10:17 +0100, Berni Elbourn wrote:
Hai Zaar wrote:
On Wed, Jun 3, 2009 at 5:12 AM, Ben Hutchingsb...@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
Hai Zaar wrote:
On Wed, Jun 3, 2009 at 5:12 AM, Ben Hutchingsb...@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
On Wed, Jun 3, 2009 at 5:12 AM, Ben Hutchingsb...@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
On Wed, 2009-06-10 at 01:28 +0100, Robert McQueen wrote:
Hi Ben,
Ben Hutchings wrote:
Please try rebuilding the lenny kernel (linux-source-2.6.26) with this
patch applied and report whether it fixes the bug for you.
Thanks very much for this patch. We've deployed a kernel with it on our
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.
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-13
Severity: important
Tags: patch
* ISSUE
Lenny's kernel is subject to the bug described here:
http://lkml.org/lkml/2009/1/11/70
* ANALYSIS FIX
and fixed with this thread:
http://lkml.org/lkml/2009/1/15/107
(in particular with
6 matches
Mail list logo
