Mesa i76e error finishing read. Another Time with LinuxCNC 2.9.1

Yes, that connection is no longer managed by the network manager GUI

You should verify that irq coalescing is disabled with

ethtool -c [your_ethernet_device_name]

(because if you have a syntax error in the interfaces file, it
is unreported and will silently fail)

It´s running perfectly since 10 hours.
I also recheckt the setting with ethtool.

Just a small hint: After installation it wasn´t possible to run the command. You need to sudo ethtool -c [your_ethernet_device_name]

So for now the topic is solved I think.

Many thanks!

A long time ago the error was gone. Now on my final way to finish my mashine I am noticing this error again more and more. Because I am still setting setting up a lot of things I restarted linuxcnc and focusing on my work. 

Today it happens 2 times in about 15minutes. It happened when I was playing / changing the speed of the spindle drive. So I thought it could be an emi issue. I changed my wiring of the ethernet cable straight from pc to Mesa. Before it was interrupted on the wall of the cabinet with a feed trough connector (this connector was in contact with the cabinet potential earth). Inside was a unscreened 20cm ethernet cable to Mesa. This is now replaced by one screened ethernet cable from pc to Mesa, without using a feed trough connector. 

Few minutes later, after I did this. I got the next error "watchdog has bit" and a lot more faults, see attached. What is the initial fault? The packet loss on ethernet or has the watchdog trip something to do with the smartserial in this case? On smartserial is my handweel. Can I see somewhere on the pc how close I am for triggering one of these errors? If there is option, I will try to Analyse the emi noise and elite it. Spectrum Analyse and HF current probe is available, but I need an indicator when packages?! are lost or the delay increases. ​

The "Watchdog has bit" error typically indicates major latency issues on the host

What are your ping times if you ping the 7I76E?

ping -i .2 -c 4 10.10.10.10
sudo chrt 99 ping -i .001 -q 10.10.10.10

The first command populates the ARP cache so the ARP lookup doesn't add time to the first ping
The second command should be run for a few minutes (and the stopped with a control C)
 

If you have another hdd load 2.8.2 and see if that helps. I've got computers that run perfect on Debian 10 but have major latency issue on 12.

Here is the output of the console:

But in this case the Spindle Drive is off and Axis-controler are in STO mode / Standby.

I still have my servothread set to 2ms.
In the .ini file there is P = 744.158356898348. Sometimes I read it should be adjustet?

Trying 2.8 Version could be possible. But the hdd is hard to access. Maybe it´s easyier to do an image of this version and reinstall 2.8.

Are there any options to see if it´s an EMI issue? Because I feel the errors are popping up more, when the spindle is on and changing speed etc.