I'd like to re-open this bug for Feisty. We have four Core 2 duo machines with an Intel Q965 chipset that are all losing ticks at about three seconds per minute (three hours per day). This appears to be an upstream kernel bug with both 2.6.19 and 2.6.20, since this occurs for us with both Feisty and Fedora Core 6 (with either 2.6.19 or 2.6.20 kernel). This occurs both with and without the proprietary nvidia kernel module.
The full dmesg log is attached. The relevant lines seem to be: [ 92.801333] Losing some ticks... checking if CPU frequency changed. [ 2240.211414] warning: many lost ticks. [ 2240.211416] Your time source seems to be instable or some driver is hogging i nterupts [ 2240.211425] rip _spin_unlock_irqrestore+0x8/0x10 As a stab in the dark, I've tried a few clock= boot options, such as clock=jiffies shown here, but these seem to have no effect. ** Attachment added: "dmesg log showing lost ticks" http://librarian.launchpad.net/7057259/dmesg.log -- Losing ticks on amd64 https://launchpad.net/bugs/26064 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
