HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- compaq nx9000 & fedora core 2/3test3 - clock slow
Operating System - Linux
1830735
Members
1842
Online
110015
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2004 06:13 AM
11-01-2004 06:13 AM
I have noticed since upgrading to fedora core 2, and also core 3test that the system clock on the laptop runs slow.
The clock ran normally under FC1. Under the latest two versions, the desktop clock (2.8.1), is set to internet time on machine bootup, but then quickly loses time. Today, with wireless network access running it is taking 70seconds to pass a real minute. But generally it's even slower than this: 75 - 90 seconds to pass one minute.
Re-setting system time using the ntp source fixes it, but it soon drifts away from the real time. Under winXP clock is OK.
I understand that the OS retrieves the RTC time at boot, and then free runs based on a timing loop, before writing the time back to RTC at os shutdown ?
So it seems the calibration of the delay loop is out of whack (both the kernels are 2.6 series). Where can it be fixed ?
[an interesting side effect is that I get apparent broadband download speeds 90/60 % better than my real connection speed ;-) ]
The clock ran normally under FC1. Under the latest two versions, the desktop clock (2.8.1), is set to internet time on machine bootup, but then quickly loses time. Today, with wireless network access running it is taking 70seconds to pass a real minute. But generally it's even slower than this: 75 - 90 seconds to pass one minute.
Re-setting system time using the ntp source fixes it, but it soon drifts away from the real time. Under winXP clock is OK.
I understand that the OS retrieves the RTC time at boot, and then free runs based on a timing loop, before writing the time back to RTC at os shutdown ?
So it seems the calibration of the delay loop is out of whack (both the kernels are 2.6 series). Where can it be fixed ?
[an interesting side effect is that I get apparent broadband download speeds 90/60 % better than my real connection speed ;-) ]
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2004 06:49 AM
11-01-2004 06:49 AM
Solution
I noticed similar problems after upgrading my HP ze4100 notebook to FC2. I was able to resolve the problem by adding the parameter
clock=pmtmr
to my kernel boot line. The kernel can use one of several different clock sources. On this hardware, pmtmr seems to be much more reliable than the default used in 2.6 kernels.
Bruce
clock=pmtmr
to my kernel boot line. The kernel can use one of several different clock sources. On this hardware, pmtmr seems to be much more reliable than the default used in 2.6 kernels.
Bruce
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2004 07:05 AM
11-01-2004 07:05 AM
Re: compaq nx9000 & fedora core 2/3test3 - clock slow
Bruce, will give this a try when my downloads finish...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2004 09:47 PM
11-01-2004 09:47 PM
Re: compaq nx9000 & fedora core 2/3test3 - clock slow
As Bruce suggested, in file:
/boot/grub/grub.conf, for my fedora boot entry, add
clock=pmtmr
to the kernel line.
My clock now runs to within 0.25 second over a minute, which is probably good enough without seeing eg how long it loses in a day.
Thanks Bruce.
/boot/grub/grub.conf, for my fedora boot entry, add
clock=pmtmr
to the kernel line.
My clock now runs to within 0.25 second over a minute, which is probably good enough without seeing eg how long it loses in a day.
Thanks Bruce.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP