[LinuxPPS] Problem - refclock_nmea: time_pps_kcbind failed

Udo van den Heuvel udovdh at xs4all.nl
Fri Jun 2 12:14:40 CEST 2006


Philip M. White wrote:
> On Fri, Jun 02, 2006 at 05:30:04AM +0200, Udo van den Heuvel wrote:
>> Does dmesg show PPS timestamps etc?
> 
> I've been running ntpd all evening with this setup, and the clk_fault is
> consistent.  

Strange. I only get it when I have no PPS due to reception.

>Here's a snippet of my dmesg:
> 
> "pps_core":"pps"[82]: New message from PID 13131 (flags 0)
> "pps_core":"pps"[189]: PPS_FETCH: source 0
> "pps_core":"kapi"[158]: capture clear seq #23664 for source 0
> "8250":"8250"[1273]: serial8250: PPS clear event at 25520476
> "pps_core":"kapi"[147]: capture assert seq #23665 for source 0
> "8250":"8250"[1269]: serial8250: PPS assert event at 25521276
> "pps_core":"kapi"[158]: capture clear seq #23665 for source 0
> "8250":"8250"[1273]: serial8250: PPS clear event at 25521476
> "pps_core":"kapi"[147]: capture assert seq #23666 for source 0
> "8250":"8250"[1269]: serial8250: PPS assert event at 25522276
> "pps_core":"pps"[82]: New message from PID 13131 (flags 0)
> "pps_core":"pps"[189]: PPS_FETCH: source 0

> Do you get similar-looking output?

Yes, this looks good.
What does the ntpq -pn look like for the NMEA clock?



More information about the LinuxPPS mailing list