On Mon, 25 Oct 2010, Brandon Black wrote: > Having the same issue on c1.xlarge in us-east-1 (kernel crash on boot > related to intel_idle). I've booted the Maverick release AMI several > times on m1.large instances fine, but I seem to have a 50%+ failure rate > getting it to initially boot without crashing on c1.xlarge. You're
My experience is much lower than 50% failure rate. I've run literally hundreds of instances. This bug seems to hit in fits. The kernel team is interested in fixing these bugs. > going to need to roll new AMIs when/if this bug is fixed, because the > failure means inability boot far enough to get the kernel upgraded in > the first place. Agreed. > FWIW, I'm only even trying Maverick because of the unresolved kernel > issues with Lucid on EC2 that have been hard to pin down (divide by zero > panics in network-related areas of the kernel, apparent disk i/o lockups > triggered by runaway CPU load triggered by apt somehow, etc...). What's Could you please open a bug ? Use ubuntu-bug /boot/vmlinuz-$(uname -r). And please attach console output of a kernel panic. I've not personally seen the bug you're describing. > going on with kernels on EC2? Is anyone at Ubuntu actually testing > them? We do test the kernels, our test suite (https://code.launchpad.net/~ubuntu-on-ec2/ubuntu-on-ec2/ec2-test) can admittedly be improved, but prior to any release we launch dozens of instances, spanning all sizes in all regions. I recently began publishing test results at https://code.launchpad.net/~ubuntu-on-ec2/ubuntu-on-ec2/ec2-test-results . -- ec2 kernel crash invalid opcode 0000 [#1] https://bugs.launchpad.net/bugs/651370 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
