This same issue can be seen by a WARNING bug at /build/buildd/linux-2.6.32/kernel/trace/ring_buffer.c:1984 rb_add_time_stamp.
Note that it seems that it is safe to ignore the warnings and oops messages, but it also seems safe to boot the kernel with the notsc to disable usage of the faulting TSC register. If anyone sees any adverse affects through either approach, please post your experiences here so we can further decide a best course of action. -- BUG: soft lockup - CPU#2 stuck for 0s! (during suspend/resume) https://bugs.launchpad.net/bugs/530487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
