ntp for amd64 is broken

[psl]

Binary package hint: ntp

Ubuntu 8.04.1 server, ntp 4.2.4p4+dfsg-3ubuntu2, amd64. amd64 is important here.

ntp at amd64 system doesn't work. i686 Ubuntu system works great but Ubuntu AMD64 system doesn't work. My TZ is Europe/Prague.

$ ntp -v ntp.ubuntu.com; date; uname -a
20 Nov 11:52:50 ntpdate[14269]: ntpdate 4.2.4p4@1.1520-o Fri Mar 7 20:36:59 UTC 2008 (1)
20 Nov 11:52:51 ntpdate[14269]: adjust time server 91.189.94.4 offset -0.005494 sec
Sat Nov 20 11:52:51 CET 2280
Linux ubuntu64 2.6.24-19-server #1 SMP Wed Aug 20 18:43:06 UTC 2008 x86_64 GNU/Linux

System time is set to nonsense (Nov 2280...). Correct date is 6 Sep 2008.

From my point of view, this is critical issue. I run this test under VMware ESX server...

[psl (slansky)]

correct command line for test is this one (ntpdate, not ntp...)
$ ntpdate -v ntp.ubuntu.com; date; uname -a

[psl (slansky)]

I fixed time manuly with date and I can see that ntpdate doesn't update it. So it looks as I see the same issue as described in #238805.

[psl (slansky)]

I am not sure what I observe here, it is more complicated.

1) system time was wrong year 2280, ntpdate cannot fix it (and it reports offest -0.005494 sec)
2) system time was wrong, year 2009, ntpdate fixed it (offset reported was something like -31542056.85).

Maybe it is some bug in ntp. I think now, that this bug is not duplacte of #238805.

[psl (slansky)]

I cannot repeat the same scenario at i686, I cannot set year 2280 at i686 system.

AMD64:
$ date 110300102280
Wed Nov 3 00:10:00 UTC 2280
$ ntpdate -v ntp.ubuntu.com; date
20 Nov 11:37:01 ntpdate[14368]: ntpdate 4.2.4p4@1.1520-o Fri Mar 7 20:36:59 UTC 2008 (1)
20 Nov 11:37:01 ntpdate[14368]: adjust time server 91.189.94.4 offset -0.008843 sec
Sat Nov 20 11:37:01 UTC 2280

i386:
$ date 110300102280
date: invalid date '110300102280'

[psl (slansky)]

I have a problem with ntpdate that cannot fix incorrect time at 64-bit Ubuntu server, it reports that year 2280 is OK (offset only -0.008843 sec). This has to be a bug in ntpdate/ntpd. (ntpd was running on the system all the time)

I checked if the wrong time was on my server from the beginning or if it was set up latter. I was able to find a lines in /var/log/messages those indicate that wrong ime was created by some incident:

Sep 4 01:53:18 ubuntu64 kernel: [ 34.900778] lo: Disabled Privacy Extensions
Sep 4 01:53:18 ubuntu64 kernel: [ 35.814779] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov 18 08:28:51 ubuntu64 kernel: [ 1036.211444] Clocksource tsc unstable (delta = 149951476369 ns)
Nov 18 08:28:51 ubuntu64 kernel: [ 4637.400352] Time: acpi_pm clocksource has been installed.
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713320] CPU 0:
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713321] Modules linked in: iptable_filter ip_tables x_tables ipv6 lp loop af_packet evdev container parport_pc button serio_raw ac parport shpchp i2c_piix4 i2c_core psmouse pcspkr pci_hotplug intel_agp reiserfs sr_mod cdrom sg sd_mod ata_piix ata_generic floppy pata_acpi mptspi mptscsih mptbase scsi_transport_spi libata e1000 scsi_mod thermal processor fan fbcon tileblit font bitblit softcursor fuse
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713423] Pid: 4516, comm: postgres Not tainted 2.6.24-19-server #1
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713425] RIP: 0010:[floppy:_spin_lock_irqsave+0x15/0x30] [floppy:_spin_lock_irqsave+0x15/0x30] _spin_lock_irqsave+0x15/0x30
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713430] RSP: 0018:ffff81001e8bb960 EFLAGS: 00000286
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713431] RAX: 0000000000000286 RBX: ffff81001d7ac000 RCX: 00000000c0000100
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713433] RDX: ffff81001e8ba000 RSI: ffff81001e8bb9a8 RDI: ffff81001d7ac000
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713434] RBP: ffff81001cc4a340 R08: ffff81001e8ba000 R09: 0000000000000000
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713435] R10: ffff81000100cc60 R11: 0000000000000001 R12: 0000000000000000
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713437] R13: ffff81001f582d00 R14: 0000000000000000 R15: ffff81001e852000
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713439] FS: 00007f47f55d8700(0000) GS:ffffffff805c4000(0000) knlGS:0000000000000000
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713441] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713442] CR2: 00000000009a2f90 CR3: 000000001ccda000 CR4: 00000000000006e0
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713447] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713451] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713452]
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713453] Call Trace:
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713456] [lock_timer_base+0x34/0x70] lock_timer_base+0x34/0x70
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713460] [try_to_del_timer_sync+0x18/0x60] try_to_del_timer_sync+0x18/0x60
Nov 18 08:28:51 ubuntu64 kernel: [ 4648.713462] [shpchp:del_timer_sync+0x10/0...

[psl (slansky)]

I replicated this issue in 64-bit ArchLinux. The issue (ntpdate doesn't synchronise time when year is in far future) is not Ubuntu specific.

[psl (slansky)]

Bug entered to NTP bugzilla.

https://support.ntp.org/bugs/show_bug.cgi?id=1061