Activity log for bug #102383

Date Who What changed Old value New value Message
2007-04-03 14:44:36 edschofield bug added bug
2007-04-03 14:47:33 edschofield description Binary package hint: linux-image-2.6.20-13-generic This may or may not be a duplicate of bug 26064, reported for Breezy (now closed). 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 boot options, such as hpet=off, clocksource=acpi_pm, clock=jiffies, and acpi=off, but these seem to have no effect. The problem seems to be with the upstream kernel sources, rather than the Ubuntu-specific patches, since it also occurs under Fedora Core 6 (with either 2.6.19 or 2.6.20). But the problem is resolved by using the mainline 2.6.21-rc5 kernel under Feisty. Binary package hint: linux-image-2.6.20-13-generic This may or may not be a duplicate of bug 26064, reported for Breezy (now closed). 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 boot options, such as hpet=off, clocksource=acpi_pm, clock=jiffies, and acpi=off, but these seem to have no effect. The problem seems to be with the upstream kernel sources, rather than the Ubuntu-specific patches, since it also occurs under Fedora Core 6 (with either 2.6.19 or 2.6.20). But the problem appears have been resolved in the mainline 2.6.21-rc5 kernel; the timer works normally on the same system with this kernel (self-compiled) but otherwise running Feisty.
2007-04-17 10:43:52 edschofield bug added attachment 'dmesg_noapic.log' (Output of dmesg using noapic boot parameter)
2007-04-17 10:47:04 edschofield bug assigned to linux (upstream)
2007-04-18 15:23:07 edschofield linux-source-2.6.20: status Unconfirmed Confirmed
2007-04-18 15:23:07 edschofield linux-source-2.6.20: statusexplanation Confirmed to affect kernel 2.6.20 on several different machines. Fixed by 2.6.21-rc5.
2007-07-25 23:50:32 Brian Murray linux-source-2.6.20: status Confirmed Incomplete
2007-07-25 23:50:32 Brian Murray linux-source-2.6.20: assignee brian-murray
2007-07-25 23:50:32 Brian Murray linux-source-2.6.20: statusexplanation Confirmed to affect kernel 2.6.20 on several different machines. Fixed by 2.6.21-rc5. Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducable with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed kernel. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.
2007-11-13 02:45:58 Brian Murray linux-source-2.6.22: importance Undecided Medium
2007-11-13 02:45:58 Brian Murray linux-source-2.6.22: status New Fix Released
2007-11-13 02:46:10 Brian Murray linux-source-2.6.20: status Incomplete Won't Fix
2007-11-13 02:46:10 Brian Murray linux-source-2.6.20: assignee brian-murray
2008-12-11 14:06:33 Pietro Battiston linux: status New Fix Released
2008-12-11 14:06:33 Pietro Battiston linux: statusexplanation so this is fixed