Displaying 3 results from an estimated 3 matches for "clockflag".
Did you mean:
clockflags
2012 Aug 09
6
Strange issue with system time being off
Hi all,
I am having an issue with some older CentOS 5.3 servers. Every time
the server boots, it gives the error "Cannot access the hardware clock
by any known method", and then promptly sets the time 5 hours behind
the hardware clock, down to the second.
After the system is up. "hwclock" works fine. hwclock --debug does not
show any error at all.
The hardware clock is
2007 Oct 04
1
[PATCH 0/5] Boot protocol changes
...on address 0x4001000
Output to block
READ from sector 870151: 368 CentOS release 5 (Final)
Press 'I' to enter interactive startup.
[ 4.483371] hwclock[2049] general protection eip:804b593 esp:bfdb5330 error:0
/etc/rc.d/rc.sysinit: line 299: 2049 Segmentation fault /sbin/hwclock $CLOCKFLAGS
Setting clock (utc): Thu Oct 4 09:32:35 GMT 2007 [ OK ]
Starting udev: 64
Notify on address 0x4005000
Output to console
Notify on address 0x4005000
Output to console
Notify on address 0x4005000
Output to console
Notify on address 0x4001000
Output to block
READ from sector 870223: 4096
Notify o...
2007 Oct 04
1
[PATCH 0/5] Boot protocol changes
...on address 0x4001000
Output to block
READ from sector 870151: 368 CentOS release 5 (Final)
Press 'I' to enter interactive startup.
[ 4.483371] hwclock[2049] general protection eip:804b593 esp:bfdb5330 error:0
/etc/rc.d/rc.sysinit: line 299: 2049 Segmentation fault /sbin/hwclock $CLOCKFLAGS
Setting clock (utc): Thu Oct 4 09:32:35 GMT 2007 [ OK ]
Starting udev: 64
Notify on address 0x4005000
Output to console
Notify on address 0x4005000
Output to console
Notify on address 0x4005000
Output to console
Notify on address 0x4001000
Output to block
READ from sector 870223: 4096
Notify o...