[gutsy] incorrect time hwclock vs date.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Description:
Recently my system time (as reported by the date command and the clock-applet) has been losing about 2 minutes per hour. versus the real time (both hwclock and my watch, phone, etc - which are all reasonably in sync).
This started occuring ~ 1 week ago, without ntpd installed.
I installed ntpd to try and 'fix' the problem, however my system time is never updated and my clocks still drift apart (with the hwclock remaining correct).
I'm not sure of the source of the problem though its possibly:
1. A kernel bug - the original drift problem (though there hasn't been a recent kernel update AFAIK), or
2. ntpd, as it never syncs the clock to any servers. (time was over two hours out after leaving my pc on over the weekend).
hwclock is correct so i'm pretty sure its not a hw problem.
This is on an updated Gutsy release.
Expected behaviour:
Correct time (system time updates at the correct rate, or ntpd keeps it correct)
Actual behaviour:
Time loses ~2 minutes per hour.
Cheers,
Andrew
Ntpd never synchronizes here either. /var/log/daemon.log may indicate that it starts too early, here is a snippet which I hope is enough to determine what the problem is:
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Will activate connection 'eth0'. manager_ begin_transacti on(): dhcdbd not running! services.
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Device eth0 activation scheduled...
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) started...
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Apr 2 07:18:58 davidUbuntu NetworkManager: <WARN> nm_dhcp_
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) failure scheduled...
Apr 2 07:18:58 davidUbuntu NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Apr 2 07:18:59 davidUbuntu avahi-daemon[5336]: Found user 'avahi' (UID 106) and group 'avahi' (GID 114).
Apr 2 07:18:59 davidUbuntu avahi-daemon[5336]: Successfully dropped root privileges.
Apr 2 07:18:59 davidUbuntu avahi-daemon[5336]: avahi-daemon 0.6.20 starting up.
Apr 2 07:18:59 davidUbuntu avahi-daemon[5336]: Successfully called chroot().
Apr 2 07:18:59 davidUbuntu avahi-daemon[5336]: Successfully dropped remaining capabilities.
Apr 2 07:18:59 davidUbuntu avahi-daemon[5336]: No service file found in /etc/avahi/
Apr 2 07:18:59 davidUbuntu avahi-daemon[5336]: Network interface enumeration completed.
Apr 2 07:18:59 davidUbuntu avahi-daemon[5336]: Registering HINFO record with values 'I686'/'LINUX'.
Apr 2 07:18:59 davidUbuntu avahi-daemon[5336]: Server startup complete. Host name is davidUbuntu.local. Local service cookie is 3653946212.
Apr 2 07:18:59 davidUbuntu NetworkManager: <info> Activation (eth0) failed.
Apr 2 07:18:59 davidUbuntu NetworkManager: <info> Deactivating device eth0.
Apr 2 07:18:59 davidUbuntu NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'.
Apr 2 07:19:01 davidUbuntu NetworkManager: <info> Will activate connection 'eth0'.
Apr 2 07:19:01 davidUbuntu NetworkManager: <info> Device eth0 activation scheduled...
Apr 2 07:19:01 davidUbuntu NetworkManager: <info> Activation (eth0) started...
Apr 2 07:19:01 davidUbunt...