Bug 8825
Summary: | Sysem clock runs too slow | ||
---|---|---|---|
Product: | Other | Reporter: | Stefan Frings (stefan) |
Component: | Bug Tracker | Assignee: | Bug Me Administrator (bugme-admin) |
Status: | CLOSED INVALID | ||
Severity: | normal | ||
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.18-4 | Subsystem: | |
Regression: | --- | Bisected commit-id: |
Description
Stefan Frings
2007-07-29 15:49:13 UTC
RedHat recommends the boot option notsc on system with PowerNow Capable Processors (like my AMD). The warning message about "instable timer source" does not occure anymore. I need to monitor this a while to see if the system clock speed is correct now. 2.6.18 is very old, and it looks also like this is a distro kernel, not a mainline kernel, in which case you need to file it with the distro. I assume, the kernel version does not matter. Anyway, I opened already a bug report for my debian distribution. Redhat writes that the tsc timer is broken on PowerNow capableCPU's, see http://kbase.redhat.com/faq/FAQ_85_6993.shtm using the "notsc" boot option (as RedHat recommends), does not help. I also tried to the "noapic" option but this causes a dramatic slowdown during boot until freezes. The problem does not occur anymore on my machine with a very recent 2.26 kernel. |