registry team mailing list archive

[Stefan Bader <stefan.bader@xxxxxxxxxxxxx>]

Sim, this patch was part of 2.6.26, so beside all other things that have
gone into 10.04 (which is based on 2.6.32) this is part of it as well.
As all the comments from various sources indicate this problem was not
seen after 2.6.26, so 10.04 should be fine.

The patches test kernels would be for people that need to stay on Hardy
and want to see whether this would fix the issue in Hardy (though there
is no guarantee). As stated above, there is no clear reason what would
have caused the problem between the two mentioned kernel versions, but
on the other hand the patch found handled some lockup problem. But that
is all things to consider for Hardy.

** Also affects: linux (Ubuntu Hardy)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Hardy)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Hardy)
       Status: New => Triaged

** Changed in: linux (Ubuntu Hardy)
     Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)

** Changed in: linux (Ubuntu)
       Status: Triaged => Fix Released

** Changed in: linux (Ubuntu)
     Assignee: Stefan Bader (stefan-bader-canonical) => (unassigned)

-- 
Server 8.04 LTS: soft lockup - CPU#1 stuck for 11s! [bond1:3795] - bond - bond0
https://bugs.launchpad.net/bugs/245779
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.