I've verified this:
* start instance of (t1.micro)
# us-east-1 ami-548c783d ebs/ubuntu-maverick-10.10-amd64-server-20101007.1
* ssh instance, install kernel reboot
% wget
https://launchpad.net/ubuntu/+archive/primary/+files/linux-image-2.6.35-24-virtual_2.6.35-24.42_amd64.deb
% sudo dpkg -i linux-image-2.6.35-24-virtual_2.6.35-24.42_amd64.deb
% sudo reboot
* ssh instance again, verify in new kernel, then shutdown
% $ uname -a
Linux ip-10-202-31-117 2.6.35-24-virtual #42-Ubuntu SMP Thu Dec 2 05:15:26
UTC 2010 x86_64 GNU/Linux
% sudo poweroff
* for each type c1.xlarge, m2.2xlarge
$ ec2-stop-instances ${IID}
$ ec2-modify-instance-attribute --instance-type ${ITYPE} ${IID}
$ ec2-start-instances ${IID}
# 5 times test reboot (note, the cpu info hopefully
# shows E5506 where it failed before)
$ for i in 1 2 3 4 5; do ssh $EC2_HOST "uname -a; uptime;
grep "Xeon" /proc/cpuinfo | head -n 1; sudo reboot" &&
echo "$i: passed" || echo "$i: failed"; sleep 2m; done
$ ssh $EC2_HOST sudo poweroff
I got an instance with X5550 in both c1.xlarge and m2.2xlarge and
successfully rebooted and connected 5 times in a row.
** Tags added: verification-done
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/651370
Title:
ec2 kernel crash invalid opcode 0000 [#1]
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
