LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 11-28-2006, 09:15 PM   #1
murrayphobbs
LQ Newbie
 
Registered: Nov 2006
Posts: 2

Rep: Reputation: 0
Question clock runs very fast on HP DL380 G4 with Redhat AS 4 64bit


Hi

my name is murray

we are running 4 HP ProLiant DL380 G4 Storage Servers - two running Redhat Enterprise AS version 4 64 bit and two running Windows 2003 Server

the linux boxes both exhibit the same problem - the clock runs up to 6 HOURS fast per day

at the moment i have a cronjob running on them both to sync with a local ntp server every 3 minutes

i've had a look around but have not found any reference to a problem of this extreme nature

any suggestions?

thanks
 
Old 11-29-2006, 02:47 PM   #2
macemoneta
Senior Member
 
Registered: Jan 2005
Location: Manalapan, NJ
Distribution: Fedora x86 and x86_64, Debian PPC and ARM, Android
Posts: 4,593
Blog Entries: 2

Rep: Reputation: 344Reputation: 344Reputation: 344Reputation: 344
This is usually solved by adding the kernel boot parameter "clock=pit". For example, in /boot/grub/grub.conf:

Code:
title xxxx (2.6.xx-x.xx.xxx)
        root (hd0,0)
        kernel /vmlinuz-2.6.xx-x.xxxx.xx ro root=LABEL=/ clock=pit quiet
        initrd /initrd-2.6.xx-x.xxxx.xxx.img
This sets the clock to use the programmable interrupt timer, and usually solves the problem (not always).
 
Old 11-30-2006, 12:10 AM   #3
murrayphobbs
LQ Newbie
 
Registered: Nov 2006
Posts: 2

Original Poster
Rep: Reputation: 0
Unhappy

re the below suggestion, no, thanks for the try, but it makes no apparent difference

murray


Quote:
Originally Posted by macemoneta
This is usually solved by adding the kernel boot parameter "clock=pit". For example, in /boot/grub/grub.conf:

Code:
title xxxx (2.6.xx-x.xx.xxx)
        root (hd0,0)
        kernel /vmlinuz-2.6.xx-x.xxxx.xx ro root=LABEL=/ clock=pit quiet
        initrd /initrd-2.6.xx-x.xxxx.xxx.img
This sets the clock to use the programmable interrupt timer, and usually solves the problem (not always).
 
Old 11-30-2006, 01:00 AM   #4
macemoneta
Senior Member
 
Registered: Jan 2005
Location: Manalapan, NJ
Distribution: Fedora x86 and x86_64, Debian PPC and ARM, Android
Posts: 4,593
Blog Entries: 2

Rep: Reputation: 344Reputation: 344Reputation: 344Reputation: 344
OK, the lesser seen issues are:

- if you are also seeing 50% CPU utilization when the machine is idle, use kernel parameter no_timer_check

- You can try the noapic kernel parameter

- You can try the notsc kernel parameter

In any case, you should also check for a BIOS update.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
UT 99 Goty runs too fast.... vbisis Linux - Games 21 04-10-2008 10:03 AM
Quake 3 runs TOO fast wick0r Linux - Games 15 02-21-2006 10:11 AM
Redhat 9 on HP DL380 G4 g_e62 Linux - Hardware 1 12-04-2005 07:46 AM
Clock Always Fast! Lagg Slackware 8 10-30-2005 07:29 PM
ntp hell: System clock runs twice as fast as it should do jimieee Linux - Software 0 01-23-2004 05:17 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 10:42 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration