[LinuxPPS] Re: [PATCH 1/1] LinuxPPS: Pulse per Second support for Linux

[Udo van den Heuvel]

Udo van den Heuvel wrote:
> Rodolfo Giometti wrote:
>> What about if you load ktimer?
> 
> I get messages but do these  numbers look OK?
> 
> pps_core: start sending reply to ID -4098...
> pps_core: ... reply sent (180)
> pps_core: capture assert seq #546 for source 0
> 8250: serial8250: PPS assert event at 789498 on source #0
> pps_core: New message from PID 10052 (flags 0)
> pps_core: PPS_FETCH: source 0
> pps_core: start sending reply to ID 10052...
> pps_core: ... reply sent (180)
> pps_core: capture clear seq #547 for source 0
> 8250: serial8250: PPS clear event at 789548 on source #0
> 
> ntpd has pid  10052  but reply goes elsewhere?

Even better to see:

#dmesg|grep sending
gives me:

pps_core: start sending reply to ID 10052...
pps_core: start sending reply to ID -4098...
pps_core: start sending reply to ID 10052...
pps_core: start sending reply to ID -4098...
pps_core: start sending reply to ID 10052...
pps_core: start sending reply to ID -4098...
pps_core: start sending reply to ID 10052...
pps_core: start sending reply to ID -4098...
pps_core: start sending reply to ID 10052...
pps_core: start sending reply to ID -4098...
pps_core: start sending reply to ID 10052...
pps_core: start sending reply to ID -4098...
pps_core: start sending reply to ID 10052...
pps_core: start sending reply to ID -4098...
pps_core: start sending reply to ID 10052...
pps_core: start sending reply to ID -4098...

how come every other (p)ID is negative?