- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- clock backward ?
Operating System - Linux
1753814
Members
7848
Online
108805
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
Discussions
Discussions
Forums
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
тАО09-18-2007 04:20 AM
тАО09-18-2007 04:20 AM
clock backward ?
Hi gurus,
I'm kind of lost on this one. Suppose I issue `date` every second. This is what I get:
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:30 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:30 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:31 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:33 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:34 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:30 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:31 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:31 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:32 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:33 EDT 2007
Its always +4 seconds -4 seconds and once in a while the system can go forward one more second.
This is a newly installed box, running for about a week. The hardware is not new though.
Some more infos:
root@hostname:/boot# uname -a
Linux "hostname" 2.6.15-28-386 #1 PREEMPT Wed Jul 18 22:50:32 UTC 2007 i686 GNU/Linux
root@hostname:/boot# uptime
11:25:55 up 3 days, 15:07, 2 users, load average: 1.77, 3.00, 2.32
root@hostname:/boot# cat /proc/interrupts
CPU0
0: 70562794 IO-APIC-edge timer
1: 735 IO-APIC-edge i8042
4: 1547 IO-APIC-edge serial
7: 0 IO-APIC-edge parport0
8: 4 IO-APIC-edge rtc
9: 1 IO-APIC-level acpi
14: 312227 IO-APIC-edge ide0
15: 5244779 IO-APIC-edge ide1
177: 0 IO-APIC-level uhci_hcd:usb3
185: 38190485 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb4, i915@pci:0000:00:02.0
193: 37 IO-APIC-level uhci_hcd:usb2
201: 4 IO-APIC-level ehci_hcd:usb5
209: 0 IO-APIC-level Intel ICH5
217: 553389 IO-APIC-level eth0
NMI: 0
LOC: 131310810
ERR: 0
MIS: 0
Somebody has any clue about what is going on?
Btw, there is no cron job for ntpdate or else...
I'm kind of lost on this one. Suppose I issue `date` every second. This is what I get:
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:30 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:30 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:31 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:33 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:34 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:30 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:31 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:31 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:32 EDT 2007
root@autogouverneur01:/boot# date
Tue Sep 18 11:24:33 EDT 2007
Its always +4 seconds -4 seconds and once in a while the system can go forward one more second.
This is a newly installed box, running for about a week. The hardware is not new though.
Some more infos:
root@hostname:/boot# uname -a
Linux "hostname" 2.6.15-28-386 #1 PREEMPT Wed Jul 18 22:50:32 UTC 2007 i686 GNU/Linux
root@hostname:/boot# uptime
11:25:55 up 3 days, 15:07, 2 users, load average: 1.77, 3.00, 2.32
root@hostname:/boot# cat /proc/interrupts
CPU0
0: 70562794 IO-APIC-edge timer
1: 735 IO-APIC-edge i8042
4: 1547 IO-APIC-edge serial
7: 0 IO-APIC-edge parport0
8: 4 IO-APIC-edge rtc
9: 1 IO-APIC-level acpi
14: 312227 IO-APIC-edge ide0
15: 5244779 IO-APIC-edge ide1
177: 0 IO-APIC-level uhci_hcd:usb3
185: 38190485 IO-APIC-level uhci_hcd:usb1, uhci_hcd:usb4, i915@pci:0000:00:02.0
193: 37 IO-APIC-level uhci_hcd:usb2
201: 4 IO-APIC-level ehci_hcd:usb5
209: 0 IO-APIC-level Intel ICH5
217: 553389 IO-APIC-level eth0
NMI: 0
LOC: 131310810
ERR: 0
MIS: 0
Somebody has any clue about what is going on?
Btw, there is no cron job for ntpdate or else...
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2007 05:19 AM
тАО09-18-2007 05:19 AM
Re: clock backward ?
Is it NTP running on your system, what do you have in /var/log/messages? What is your configuration in /etc/sysconfig/clock. Once I had a similar problem and setting UTC and ARC to false solved the problem, if I remember well.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2007 05:59 AM
тАО09-18-2007 05:59 AM
Re: clock backward ?
Thanks,
ntp is not running. /var/log/messages doesnt show anything useful.
Even if I sync the hardware clock and soft clock with hwclock --systohc it starts to drift right away.
I think it's acpi I need to turn off but a reboot seems to have fixed the problem. I'll keep an eye on this system to see if it happens again.
ntp is not running. /var/log/messages doesnt show anything useful.
Even if I sync the hardware clock and soft clock with hwclock --systohc it starts to drift right away.
I think it's acpi I need to turn off but a reboot seems to have fixed the problem. I'll keep an eye on this system to see if it happens again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2007 11:26 AM
тАО09-18-2007 11:26 AM
Re: clock backward ?
A reboot solved the problem.
The system is responsive and the clock has not drifted in 5 hours uptime. Could Apic be the culprit?
The system is responsive and the clock has not drifted in 5 hours uptime. Could Apic be the culprit?
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP