Polygon... Oddly, this is black-box testing -- someone made changes to what appears to be a kernel support feature (even though the support crowd doesn't acknowledge). You think it is a tsc thing, cores never need to sync -- actually true fact is that they cannot sync. I suppose that log is informational only -- and anyone who says differently will tell you they 'believe in fairies'... even if some of us know they exist.
re-examine your system -- you started something, obviously is close enough to the standard roll-out as all of us, that is (by logic) triggering a non-standard kernel embedded sub-system that did not exist 'live' in Intrepid Ibez, and was standard on the jaunty jackalope rollout. Those are the similarities I see. purely random freezes... with my system, I get nothing.... but I'm a Windows Programmer, and (by default) don't know shit. I would imagine that the power of the event-driven OS is superseeding the requirement of a ALT-CTL-F1 and gain a login. I know some people were talking about being able to use some REIS something ... to try to regain control... the kernel writers need to keep a 10% reserve for 'critical OS' determined messages... event driven sucks sometimes. but really you aim to create another version of XP without the funding, and following (software).... I have killed my Jaunty, and have gone back to 8.10. No worries, it will be good for many weeks -- but I love the improvements that I did experience! -- Clocksource tsc unstable leads to lockups in Ubuntu Jaunty https://bugs.launchpad.net/bugs/355155 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
