Bug 3057 - System clock still runs too fast
Summary: System clock still runs too fast
Status: REJECTED UNREPRODUCIBLE
Alias: None
Product: Timers
Classification: Unclassified
Component: Realtime Clock (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: john stultz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-12 12:20 UTC by Joshua Trimm
Modified: 2005-09-08 14:27 UTC (History)
2 users (show)

See Also:
Kernel Version: 2.6.8rc1
Subsystem:
Regression: ---
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Joshua Trimm 2004-07-12 12:20:34 UTC 
Distribution: 
Hardware Environment: IBM x440 dual Xeon w/ hyperthreading
Software Environment: Redhat 9 + kernel 2.6.8rc1
Redhat 9 + kernel 2.6.7-mm6

Problem Description:
System clock still runs too fast, Seems to be similar to bug 827 but patch does
not work. Power management is disabled in the .config and bios.


Steps to reproduce:
1. Compile kernel on IBM x440 series
2. Reboot and watch clock, speeds are doubled.
Comment 1 Joshua Trimm 2004-07-12 13:12:18 UTC 
Note: Correction, Architecture is IBM x225 model 8647-5AX
Comment 2 john stultz 2005-08-09 11:16:05 UTC 
Does this problem still occur with kernel 2.6.12 or greater?
Comment 3 Darrick J. Wong 2005-08-16 19:00:30 UTC 
Uh... I never noticed this problem on my x225 when I tested 2.6.11 way back
when.  System setup was dual P4 2.4GHz CPUs, 2GB RAM, acpi and hyperthreading
turned on, Debian Sarge with a vanilla Linus 2.6.11 kernel.
Comment 4 john stultz 2005-09-08 14:27:48 UTC 
Unable to reproduce and no input for a month. Please reopen if the problem 
appears with a current kernel.
Note You need to log in before you can comment on or make changes to this bug.