Smart Serial Comms Error - Since upgrade to 2.9.4

Hi All
I've had to rebuild my machine after an SSD failure, and decided to move into the future.
I installed 2.9.4 and copied in my machine config files, everything worked out an issue initially but with in a few minutes I started getting the following errors
 

The latancy seems ok, running for a long time with glxgears and watching video via youtube and copying larger files

 

I'm running a bit file which might be old, PCW made it up for me at least 4 years ago
7i80db_16_7i76x3D3p.bit

 

The root issue is not sserial related but latency related
(notice that the first error is a watchdog bite)

I would

1. Run a latency test

2. Check the network latency with:

sudo chrt 99 ping -i .001 -q -c 60000 10.10.10.10

or

sudo chrt 99 ping -i .001 -q -c 60000 192.168.1.121

(depending on 7I80 IP address setting)


 

Kept looking last night and ran the IRQ script found else where on this forum.
This seemed to improve things, I left LCNC running all night with glxgears and other things running and did not get the messages again.

Ping result
cnc@minimill:~$ sudo chrt 99 ping -i .001 -q -c 60000 10.10.10.10
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.

--- 10.10.10.10 ping statistics ---
60000 packets transmitted, 60000 received, 0% packet loss, time 60401ms
rtt min/avg/max/mdev = 0.056/0.084/7.709/0.139 ms

The issue maybe be fixed I'll see how we go actually using it today.

mjoconr wrote:

--- 10.10.10.10 ping statistics ---
60000 packets transmitted, 60000 received, 0% packet loss, time 60401ms
rtt min/avg/max/mdev = 0.056/0.084/7.709/0.139 ms

That is not good, at all.
If the PC has a RealTek network card, you will find a lot of replies here to install the DKMS drivers for it, i would skip that and try a new RT kernel, something like 6.11 or above.

I upgraded via backports to 6.12.22+bpo-rt-amd64, still get a 5ms max delay.

I ran it a few times
rtt min/avg/max/mdev = 0.053/0.116/5.600/0.269 ms
rtt min/avg/max/mdev = 0.054/0.099/4.908/0.216 ms
rtt min/avg/max/mdev = 0.054/0.106/4.672/0.241 ms

I've not had a warning since I ran the IRQ script.

We will see once I start actually cutting