Further investigations and testing indicate that the boot-option noapic provides an usable workaround. I've had the affected computer running with that boot-option for several hours, leaving it unattended with programs that I usually had running when the lockup occured for quite a while (this would usually trigger a lockup) and so far it seems like it is gone.
-- lockups with default (hpet) clocksource on 2.6.27-2-generic 64-bit https://bugs.launchpad.net/bugs/270798 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
