Solution fo "hm2 error finishing read" with no good PC

I need help because I don't know what to do with my PC.
At the moment linuxcnc displays ‘hm2 error finishing read’ every time I change the tool on my turret on my cnc lathe.
several weeks ago I had this message sometime.

below the latency of my pc and the ping for the ethernet.
 

I have disabled all the options that slow down latency in the bios/uefi.
I have followed the procedure to isolate a core for linuxcnc. and other procedure to reduce latency (IRQ affinity scripts / rt_setup).

but i have the problem ‘hm2 error finishing read’, is there any solution to remove this problem or the only solution is to replace the pc because nothing can be done?
 

The issue is the 5.835 ms maximum ping time (about 10X the usable maximum)

My guess is that you have a RealTek Ethernet interface on you PC which requires
and alternate driver (DKMS) be installed since the driver supplied with the 6.1 kernel has
real-time issues.

Instructions for this are in this thread:

forum.linuxcnc.org/27-driver-boards/5366...xcnc?start=20#310794

Before you do that is probably best to determine the actual Ethernet hardware with say:

lspci | grep -i ether



 

i did, but still the same.
i have done ping 10.10.10.10 during the nigh and i have lost some packet.

my hardware is Realtek RTL8111/RTL8168

Have you added

pcie.aspm=0 r8168.eee_enable=0 pcie_aspm=off idle=poll

to the kernel command line? (via grub)
Sometimes that is needed also.

To make sure you are running the dkms driver, try running this script: 

 

To run this, first

chmod +x edriver.txt

and then

./edriver.txt

(from the Downloads directory)

and paste the results here.

(not my script but nicely lists network drivers) 

i added the same as the google doc "r8168.aspm=0 r8168.eee_enable=0 pcie_aspm=off loglevel=3"
i changed and add " pcie.aspm=0 r8168.eee_enable=0 pcie_aspm=off idle=poll" but still the same "hm2 error finishing read" (I restarted the PC)

 

That looks like the standard realtek 8168 driver rather than the DKMS driver
so it sounds like the DKMS driver install did not work for some reason