DEBUG=5 halrun now has a stream of messages:

[Michael Brown]

I have been having this nag on the new aarch64 project, so I decided to test if this was a local  arm64 issue

First I just had a "normal" DEBUG=5 halrun session (on a armhf mksocfpga), without (the new) noise

Then I did a 

sudo apt -y update && sudo apt -y upgrade

Apt Updated between these 2 commits:

machinekit-cnc-rt-preempt/stable 0.1.1560931733.git432e8f3-1~stretch armhf [upgradable from: 0.1.1559377986.gitd44b2de-1~stretch]

machinekit-hal-rt-preempt/stable 0.2.1567171065.git3591f6e-1~stretch armhf [upgradable from: 0.2.1560578992.git3008e4a-1~stretch]

Then I rebooted and just put in:

DEBUG=5 halrun.

2 seconds of output (It just keeps coming until I type exit)

machinekit@mksocfpga-nano-soc:~$ DEBUG=5 halrun                  
msgd:0 stopped
rtapi:0 stopped
rtapi_msgd command:  /usr/libexec/linuxcnc/rtapi_msgd --instance=0 --rtmsglevel=5 --usrmsglevel=5 --debug=5 --halsize=524288
rtapi_app command:  /usr/libexec/linuxcnc/rtapi_app_rt-preempt --instance=0 --debug=5
D: 19-09-14 20:08:34 zloop: register FD poller ((nil), 6)
D: 19-09-14 20:08:34 zloop: register ROUTER reader
D: 19-09-14 20:08:34 zloop: register timer id=1 delay=1000 times=0
D: 19-09-14 20:08:34 zloop polling for 1000 msec
D: 19-09-14 20:08:34 zloop: call ROUTER socket handler
request: type: MT_RTAPI_APP_PING
rtapicmd {
 instance: 0
}

reply: type: MT_RTAPI_APP_REPLY
note: "pid=2263 flavor=rt-preempt gcc=6.3.0 20170516 git=v0.2~-----~3591f6e"
retcode: 0

D: 19-09-14 20:08:34 zloop polling for 898 msec
D: 19-09-14 20:08:34 zloop: call ROUTER socket handler
request: type: MT_RTAPI_APP_PING
rtapicmd {
 instance: 0
}

reply: type: MT_RTAPI_APP_REPLY
note: "pid=2263 flavor=rt-preempt gcc=6.3.0 20170516 git=v0.2~-----~3591f6e"
retcode: 0

D: 19-09-14 20:08:34 zloop polling for 877 msec
D: 19-09-14 20:08:34 zloop: call ROUTER socket handler
request: type: MT_RTAPI_APP_PING
rtapicmd {
 instance: 0
}

reply: type: MT_RTAPI_APP_REPLY
note: "pid=2263 flavor=rt-preempt gcc=6.3.0 20170516 git=v0.2~-----~3591f6e"
retcode: 0

D: 19-09-14 20:08:34 zloop polling for 689 msec
halcmd: D: 19-09-14 20:08:35 zloop: call timer handler id=1
D: 19-09-14 20:08:35 zloop polling for 999 msec
D: 19-09-14 20:08:36 zloop: call timer handler id=1
D: 19-09-14 20:08:36 zloop polling for 999 msec
D: 19-09-14 20:08:37 zloop: call timer handler id=1
D: 19-09-14 20:08:37 zloop polling for 999 msec
D: 19-09-14 20:08:38 zloop: call timer handler id=1
D: 19-09-14 20:08:38 zloop polling for 999 msec
D: 19-09-14 20:08:39 zloop: call timer handler id=1
D: 19-09-14 20:08:39 zloop polling for 999 msec
D: 19-09-14 20:08:40 zloop: call timer handler id=1
D: 19-09-14 20:08:40 zloop polling for 999 msec
D: 19-09-14 20:08:41 zloop: call timer handler id=1
D: 19-09-14 20:08:41 zloop polling for 999 msec
D: 19-09-14 20:08:42 zloop: call timer handler id=1
D: 19-09-14 20:08:42 zloop polling for 999 msec
D: 19-09-14 20:08:43 zloop: call timer handler id=1
D: 19-09-14 20:08:43 zloop polling for 999 msec
exiD: 19-09-14 20:08:44 zloop: call timer handler id=1
D: 19-09-14 20:08:44 zloop polling for 999 msec
t
D: 19-09-14 20:08:45 zloop: call timer handler id=1
D: 19-09-14 20:08:45 zloop polling for 1000 msec
D: 19-09-14 20:08:45 zloop: call ROUTER socket handler
request: type: MT_RTAPI_APP_PING
rtapicmd {
 instance: 0
}

reply: type: MT_RTAPI_APP_REPLY
note: "pid=2263 flavor=rt-preempt gcc=6.3.0 20170516 git=v0.2~-----~3591f6e"
retcode: 0

D: 19-09-14 20:08:45 zloop polling for 889 msec
<commandline>:0: Realtime threads stopped
D: 19-09-14 20:08:46 zloop: call ROUTER socket handler
request: type: MT_RTAPI_APP_PING
rtapicmd {
 instance: 0
}

reply: type: MT_RTAPI_APP_REPLY
note: "pid=2263 flavor=rt-preempt gcc=6.3.0 20170516 git=v0.2~-----~3591f6e"
retcode: 0

D: 19-09-14 20:08:46 zloop polling for 113 msec
D: 19-09-14 20:08:46 zloop: call ROUTER socket handler
request: type: MT_RTAPI_APP_EXIT
rtapicmd {
 instance: 0
}

reply: type: MT_RTAPI_APP_REPLY
retcode: 0

machinekit@mksocfpga-nano-soc:~$

I have had this phenomenon for at least 12 days but thought it was related to the new aarch64 stuff however this is clearly not the case ....