Article View: comp.protocols.time.ntp
Article #834VxWorks NTP: MVME167 problem (Prev time adj didn't complete)
From: Tom Nicinski
Date: Mon, 14 Dec 1992 16:37
Date: Mon, 14 Dec 1992 16:37
10 lines
1067 bytes
1067 bytes
I'm using the VxWorks port of NTP on both a Motorala MVME147 and MVME167. I've
gotten the 147 to work reasonably well. But, on the 167, after 15 minutes or
so, I constantly get:
Previous time adjustment didn't complete
Since I'm not familiar with NTP, has anyone else seen this problem and solved
it. Our clock rate is 1000 Hz on both machines. NTPD is the only "user" task
operating on the machines (during our NTP tests), so there's nothing really to
steal the CPU away from timekeeping.
Technical Details
Message-ID:
<1gid8vINNepi@fnnews.fnal.gov>Path:
arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mp.cs.niu.edu!fnnews.fnal.gov!fndaud.fnal.gov!nicinskiShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mp.cs.niu.edu!fnnews.fnal.gov!fndaud.fnal.gov!nicinski From: nicinski@fndaud.fnal.gov (Tom Nicinski) Newsgroups: comp.protocols.time.ntp Subject: VxWorks NTP: MVME167 problem (Prev time adj didn't complete) Date: 14 Dec 1992 16:37:51 GMT Organization: Fermi National Accelerator Laboratory, Batavia IL Lines: 10 Distribution: world Message-ID: <1gid8vINNepi@fnnews.fnal.gov> NNTP-Posting-Host: fndaud.fnal.gov Keywords: VxWorks MVME167