Hi,
Thank you for taking the time to open a bug report.
Just for clarity, the issue here is with:
us-east-1 ami-7e28ca17 canonical ubuntu-hardy-8.04-i386-server-20091130
And the bug opener has found that they can fix the issue by using the jaunty
kernels, which were never officially released by Canonical. (aki-20c12649
canonical-beta-us/vmlinuz-2.6.27-22-xen-i386-us.manifest.xml).
The ami itself for hardy is not the newest release, but the kernel it
uses is the newest released kernels for hardy (ubuntu-kernels-us
/ubuntu-hardy-i386-linux-
image-2.6.24-10-xen-v-2.6.24-10-kernel.img.manifest.xml).
to help us debug the issue, could you please
a.) give any information you have on how you can reproduce this issue
b.) try to reproduce on one of the hardy daily build amis. The latest daily
build image of hardy uses a substantially newer kernel. I would suggest trying
to reproduce on:
us-east-1 ami-22cc3e4b canonical ubuntu-hardy-daily-i386-server-20110314
which uses kernel:
us-east-1 aki-7e15e617 canonical
ubuntu-hardy-i386-linux-image-2.6.24-28-xen-v-2.6.24-28.86-kernel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/705562
Title:
ami-6836dc01 8.04 32 bit AMI kernel lock bug
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
