Bug 184593

Summary: System clock runs way too fast with kernel-2.6.15-1.2032_FC5
Product: [Fedora] Fedora Reporter: John Thacker <johnthacker>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 5CC: jfrieben, pfrields, redhat-bugzilla, tmraz, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-30 05:13:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg with kernel-2.6.15-1.2038_FC5 (clock too fast)
none
dmidecode with kernel-2.6.15-1.2038_FC5
none
dmesg with kernel-2.6.15-1.2009.4.2_FC5 (works) none

Description John Thacker 2006-03-10 02:41:00 UTC 
Description of problem:
After updating to kernel-2.6.15-1.2032_FC5, I noticed that my system clock
started running WAY too fast.  I gained an entire hour in about a day.  (The
clock runs so fast it can't stay in sync with NTP servers.)  My hardware clock
is perfectly fine.  Rebooting to kernel-2.6.15-1.2009.4.2_FC5 makes it work
perfectly.

Version-Release number of selected component (if applicable):
kernel-2.6.15-1.2032_FC5

How reproducible:
Every time

Steps to Reproduce:
1. Boot in that kernel
  
Actual results:
System clock runs way too fast

Expected results:
System clock runs normally

Additional info:
It works perfectly fine on the previous kernel, kernel-2.6.15-1.2009.4.2_FC5,
both before and after rebooting to it.
Comment 1 John Thacker 2006-03-10 17:27:36 UTC 
Problem persists on todays kernel-2.6.15-1.2038_FC5.  Rebooting to
kernel-2.6.15-1.2009.4.2_FC5 again works fine.  Any particular information that
would be helpful?
Comment 2 Dave Jones 2006-03-10 21:37:27 UTC 
dmesg and dmidecode output please ?
Comment 3 John Thacker 2006-03-11 00:42:48 UTC 
Created attachment 125969 [details]
dmesg with kernel-2.6.15-1.2038_FC5 (clock too fast)
Comment 4 John Thacker 2006-03-11 00:43:15 UTC 
Created attachment 125970 [details]
dmidecode with kernel-2.6.15-1.2038_FC5
Comment 5 John Thacker 2006-03-11 00:45:11 UTC 
Created attachment 125971 [details]
dmesg with kernel-2.6.15-1.2009.4.2_FC5 (works)

I didn't enter the nolapic keyword but it seems like it was disabled by
default.
Comment 6 John Thacker 2006-03-11 01:18:20 UTC 
Booting with 'noapic' makes it work fine.  I can add another dmesg if it would help.
Comment 7 Joachim Frieben 2006-03-13 08:40:37 UTC 
Looks like a duplicate of Bug #55223 albeit striking uni-processor
kernels, too, now. I had reopened Bug #55223 on 2006-03-05 after
observing the same regression which had occurred some time in
January 2006.
Comment 8 John Thacker 2006-03-30 05:13:06 UTC 
Seems to be working fine with kernel-2.6.16-1.2080_FC5 even without noapic.  Thanks!
Comment 9 John Thacker 2006-04-20 23:48:54 UTC 

*** This bug has been marked as a duplicate of 55223 ***