Richard Todd <rmtodd_at_ichotolot.servalan.com> wrote: > I just today updated my system to the most recent -current. Upon rebooting, > I noticed that NTP seemed to be seriously confused: Support for my serially attached DCF77 receiver (server 127.127.8.0 mode 14) reference clock is also broken. ntpd logs the supposedly received time stamp every minute: Aug 24 13:14:20 lorvorc ntpd[32943]: parse: convert_rawdcf: parity check FAILED for "--#--#-#---##--R-D--S--4812-p-2----P----1-1-4--48-12-812--P__" Aug 24 13:15:22 lorvorc ntpd[32943]: parse: convert_rawdcf: parity check FAILED for "##-#-#--###--#-R--M-s1248---P----1-p--4--2--4----11-----4-p?_" Aug 24 13:16:24 lorvorc ntpd[32943]: parse: convert_rawdcf: parity check FAILED for "##-#--###--#-#--A--LS12---2-p--4---p1-48--124-248-12--1--8P??" However, this is random garbage. I've truss(1)ed ntpd and the bits it actually reads from the serial port are correct. Somehow they don't make it into the time stamp. > This is on a Core2Duo system running FreeBSD in i386 mode. amd64 here. -- Christian "naddy" Weisgerber naddy_at_mips.inka.deReceived on Sun Aug 24 2008 - 09:33:25 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:34 UTC