RE: clockspeed on amd64 problems

Ethan Erchinger <[email protected]> Tue, 11 May 2004 15:48:51 -0700
Newsgroups gmane.comp.lib.libtai
Message-ID <[email protected]>
I have run clockspeed on an Opteron platform, without issue.  I was running
it in 32-bit mode however (read as: running a 32-bit OS/Rhat 7.3). You
should be able to use clockspeed compiled for a i386 Linux distro on any
x86-64 Linux distro.

Regards
Ethan

-----Original Message-----
From: Vincent Danen [mailto:[email protected]] 
Sent: Tuesday, May 11, 2004 3:18 PM
To: [email protected]
Subject: clockspeed on amd64 problems

Sorry if this has been brought up before, but I can't seem to find any 
archives for this mailing list linked off the webpage.

I'm having a problem running sntpclock on amd64, and getting some wierd 
results with taiclock.  When I run sntpclock, I get a segfault.  The 
strace output is:

[vdanen@titan vdanen]$ strace sntpclock 136.159.2.2
execve("/usr/bin/sntpclock", ["sntpclock", "136.159.2.2"], [/* 39 vars 
*/]) = 0
open("/etc/leapsecs.dat", O_RDONLY|O_NONBLOCK) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=176, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 
0) = 0x2a95556000
time(NULL)                              = 1084313464
getpid()                                = 17207
getppid()                               = 17206
open("/dev/urandom", O_RDONLY)          = 4
read(4, "\351\32[:", 4)                 = 4
read(3, 0xffffffff95556028, 176)        = -1 EFAULT (Bad address)
close(3)                                = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

When I use taiclock against a properly setup taiclockd (on an x86 box) 
I get:

[vdanen@titan vdanen]$ taiclock 10.0.5.30|clockview
before: 2081-04-01 03:12:44.769652000000000000
after:  2081-04-01 03:03:46.349832000000000000

But if I do the same thing on the x86 box I get:

root@dionysus root]# taiclock 10.0.5.30|clockview
before: 2004-05-11 16:14:04.243967000000000000
after:  2004-05-11 16:14:04.243965000000000000

I can only suspect some math problems due to the 64bit processor... 
does this mean clockspeed (as is) doesn't work on amd64 processors?

I'm putting together a Linux distribution and wanted to get rid of ntpd 
altogether in favour of clockspeed, but looking at this I'm not sure if 
it's possible (the distro supports x86 and amd64 so I can either use 
clockspeed (working on both) or forget it and go back to ntpd).

Any assistance or info would be appreciated.  Thanks.

-- 
OpenSLS - Secure Linux Server: http://opensls.org/
"lynx -source http://linsec.ca/vdanen.asc | gpg --import"
{FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7  66F9 2043 D0E5 FE6F 2AFD}