Hi all,

I have been working on BUG#399 (
https://support.ntp.org/bugs/show_bug.cgi?id=399)
A working level patch is submitted at NTP bugzilla.

I have been testing the patch with Accord GPS Clock and a consistent
observation
has been made as shown below (a slice of ntp.log)

----------------------------------------------------------------------------------------------------------------
28 Mar 23:48:45 ntpd[12199]: kernel time sync status change 2107
28 Mar 23:57:29 ntpd[12199]: kernel time sync error 2307
28 Mar 23:57:46 ntpd[12199]: kernel time sync status change 2107
29 Mar 00:00:00 ntpd[12199]: Arguments to clocktime() : 89, 23, 59, 59, 0,
3415737599, 3408134400, 3221223076
29 Mar 00:00:00 ntpd[12199]: clock GPS_NMEA(0) event 'clk_badtime' (0x06)
29 Mar 00:00:00 ntpd[12199]: peer GPS_NMEA(0) event 'event_peer_clock'
(0x85) status 'reach, conf, sel_sys.peer, 2 events, event_peer_clock'
(0x9625)
29 Mar 00:00:00 ntpd[12199]: refclock_nmea.c:788 : timecode length = 80,
$GPGGA,235959.9,1719.9132,N,07829.5489,E,1,07,01.0 ,00450.0,M,-071.6
,M,00,0000*7D

29 Mar 00:00:01 ntpd[12199]: kernel time sync error 2307
29 Mar 00:00:01 ntpd[12199]: clock GPS_NMEA(0) event 'clk_okay' (0x00)
29 Mar 00:00:01 ntpd[12199]: peer GPS_NMEA(0) event 'event_peer_clock'
(0x85) status 'reach, conf, sel_sys.peer, 3 events, event_peer_clock'
(0x9635)
29 Mar 00:00:16 ntpd[12199]: kernel time sync status change 2107
29 Mar 00:02:45 ntpd[12199]: kernel time sync error 2307
29 Mar 00:03:03 ntpd[12199]: kernel time sync status change 2107
----------------------------------------------------------------------------------------------------------------


At the transition to a new day, when the time rolls from 233539.9 to
000000.X,
ntpd reports the event 'clk_badtime' (0x06).

Is this behavior consistent with other GPS receivers ?