To clarify, I'm pretty sure whether this happens depends on the Amazon hardware the instance is being run on.
My warning was that, while the instance was currently running on hardware that causes the problem, if it was stopped and then started later, it might not end up on the same hardware, and therefore the bug might not happen that launch. If I have the problem on a running instance, and just reboot it, though, I've always had it again -- I assume Amazon doesn't move the instance if you're just rebooting it. So if an instance is encountering the problem, it'll continue happening no matter how many times you reboot it. But if you shut it down, it might not happen when it's started next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1349883 Title: dmesg time wildly incorrect on paravirtual EC2 instances. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
