Somehow I had hoped to find some way to understand why the fix works (or
what exactly goes wrong without it). But then other things and bad long-
time memory (sort of) came into play and this has not really progressed
much. So I try to actually get this into Precise at least (since no
testing seems to have found any bad side effects). Still need to follow-
up on this for current kernels (if the testcase still fails there).
** Also affects: linux (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux-lts-backport-oneiric (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Precise)
Status: New => In Progress
** Changed in: linux (Ubuntu Precise)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Precise)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
** Changed in: linux-lts-backport-oneiric (Ubuntu Precise)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1011792
Title:
Kernel lockup running 3.0.0 and 3.2.0 on multiple EC2 instance types
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1011792/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
