Bug 65939

Summary: clock runs extra fast
Product: [Retired] Red Hat Linux Reporter: Bill Nottingham <notting>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DEFERRED QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: mingo, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-10-17 03:52:53 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:
Bug Depends On:    
Bug Blocks: 67218, 79579, 100644    
Attachments:
Description Flags
dmidecode output
none
lspci output
none
dmesg output
none
/proc/interrupts none

Description Bill Nottingham 2002-06-04 15:54:12 UTC
With 2.4.18-0.40smp, the clock on this machine runs (roughly) twice as fast.

If booted with 'noapic', it works OK.

Comment 1 Bill Nottingham 2002-06-04 16:01:11 UTC
Created attachment 59524 [details]
dmidecode output

Comment 2 Bill Nottingham 2002-06-04 16:01:43 UTC
Created attachment 59525 [details]
lspci output

Comment 3 Bill Nottingham 2002-06-04 16:01:55 UTC
Created attachment 59527 [details]
dmesg output

Comment 4 Bill Nottingham 2002-06-04 16:02:14 UTC
Created attachment 59529 [details]
/proc/interrupts

Comment 5 Arjan van de Ven 2002-06-05 09:49:08 UTC
Ingo: could this be that the timer irq is routed to 2 cpu's ?

Comment 6 Jay Turner 2002-11-20 20:30:21 UTC
Can we close this out now?

Comment 7 Bill Nottingham 2002-11-20 20:32:51 UTC
Well, depends how well the current kernel works on this box. Haven't tried recently.

Comment 8 Bill Nottingham 2003-10-17 03:52:53 UTC
Deferred, I think that box is dead.