Neue Hardware und schlechter Latency Test

More
3 years 3 months ago #276536 by chris@cnc

There are still peaks
In the BIOS, everything that has to do with speed step, energy management or is unnecessary is turned off.
C-Step in BIOS is C0, smaller is not possible.
I had the same problems and built a new kernel from the kernel.org source. If you want, you could test this core.
Download all three files.
drive.google.com/drive/folders/1HceAcPQd...u4zS9?usp=drive_link and install in this way 
Code:
open terminal cd "your download folder" sudo dpkg -i linux-image-6.4.0-rt6-linuxcnc_6.4.0-1_amd64.deb sudo dpkg -i linux-headers-6.4.0-rt6-linuxcnc_6.4.0-1_amd64.deb  sudo dpkg -i linux-libc-dev_6.4.0-1_amd64.deb and reboot

Please Log in to join the conversation.

More
3 years 3 months ago #276549 by WKS-3D
Thank you :)
I don't need to run all the commands in the "notes" file, just the ones you mentioned here?
Code:
open terminal cd "your download folder" sudo dpkg -i linux-image-6.4.0-rt6-linuxcnc_6.4.0-1_amd64.deb sudo dpkg -i linux-headers-6.4.0-rt6-linuxcnc_6.4.0-1_amd64.deb  sudo dpkg -i linux-libc-dev_6.4.0-1_amd64.deb and reboot

I will make a backup and try the whole thing.
Did it do anything for you? What kind of system do you use?

Greetings
Olli

Please Log in to join the conversation.

More
3 years 3 months ago #276553 by chris@cnc
I use Debian 12 on an HP 800 G3 SFF. And you installed the 6.1.0*rt*amd64 kernel. So i guess you use the same operating system.
The notes are a message to me about how i did it. And it's from an earlier version.  You only install the *.deb files. And yes, it improves the latency times and also the response time to the mesa card.
You can show it in the terminal.
"halcmd show param *.tmax"  or seach in halshow
Also, useful command is "sudo dmesg --color=always | less -R "
This will show kernel log errors marked in red. The most common reason for this issue is difficult hardware, like nvidia or onboard graphic cards, or some network cards. 

Please Log in to join the conversation.

More
3 years 3 months ago #276554 by rodw
I think you will be fine for a mesa card without doing  anything more.
Please do this tweak as it should help.:
linuxcnc.org/docs/2.9/html/getting-start...weaks_x86_amd64_only
Make 1 change
Isolcpus=2,3 shown there is best for the latency test but its not the best for me as cards where network latency is more important.
Make it isolcpus=3 instead.

Also do the first two steps here and report the results here.
linuxcnc.org/docs/2.9/html/getting-start...ltek_network_drivers

If it says it is an R8111 driver, continue on and install the  r8168-dkms driver

I had a user implement these steps 2 days ago on a 2 core machine and he has since completed over 14 hours continuous machining with a single fault. :)
You should not need to install a newer kernel

Please Log in to join the conversation.

More
3 years 3 months ago #276555 by WKS-3D
driver: e1000e
version: 6.4.0-rt6-linuxcnc
firmware-version: 0.8-4
expansion-rom-version:
bus-info: 0000:00:1f.6
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

It should be a Intel-Card (I219LM)

At this moment there is no mesa card connected but it has a fixed IP (10.10.10.1/8)
The network adapter for my normal network is a USB to LAN adapter.

I changed "isolcpus to 3"

The latency test shows peaks:
Servo thread max jitter = 155602
Base thread max jitter = 336079

Please Log in to join the conversation.

More
3 years 3 months ago #276561 by tommylight
There was no need to do any of the above, now you have worse latency than you had with 6.1 kernel.
It was perfectly OK with latency-histogram, should have just done a test without base period.

Please Log in to join the conversation.

More
3 years 3 months ago #276562 by chris@cnc
I would try Isolcpus=2,3. I have the e1000e network nic on my laptop too. Not the best choice for that but the 6.4. Kernel version is more stable as the 6.1. I test it several times.
Try what show the tmax times to your mesa card.
If you not get the "error finishing read" could it be working.

to test ping latency 
sudo chrt 99 ping -i .001 -q 10.10.10.10
forum.linuxcnc.org/27-driver-boards/4837...rite?start=20#266420

Last idea.  Ping times could be improved to set the coalescing setting.
To check if it's enabled, use command 
ethtool -c eth0
If line "rx-usecs" not return ":0"
Try this
sudo ethtool -C "your net card"  rx-usecs 0
It's better follow the instruction from the hm2 driver
linuxcnc.org/docs/2.9/html/man/man9/hm2_...FACE%20CONFIGURATION

Please Log in to join the conversation.

More
3 years 3 months ago #276563 by WKS-3D
This is the latency test ~1h
 

Attachment not found



This is the  PING-Result from the Mesa-Card (7i92TM)
Code:
PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data. 64 bytes from 10.10.10.10: icmp_seq=1 ttl=64 time=0.273 ms 64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.140 ms 64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.138 ms 64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.140 ms 64 bytes from 10.10.10.10: icmp_seq=5 ttl=64 time=0.137 ms 64 bytes from 10.10.10.10: icmp_seq=6 ttl=64 time=0.141 ms 64 bytes from 10.10.10.10: icmp_seq=7 ttl=64 time=0.140 ms 64 bytes from 10.10.10.10: icmp_seq=8 ttl=64 time=0.148 ms 64 bytes from 10.10.10.10: icmp_seq=9 ttl=64 time=0.148 ms 64 bytes from 10.10.10.10: icmp_seq=10 ttl=64 time=0.139 ms 64 bytes from 10.10.10.10: icmp_seq=11 ttl=64 time=0.137 ms 64 bytes from 10.10.10.10: icmp_seq=12 ttl=64 time=0.139 ms 64 bytes from 10.10.10.10: icmp_seq=13 ttl=64 time=0.139 ms 64 bytes from 10.10.10.10: icmp_seq=14 ttl=64 time=0.139 ms 64 bytes from 10.10.10.10: icmp_seq=15 ttl=64 time=0.140 ms 64 bytes from 10.10.10.10: icmp_seq=16 ttl=64 time=0.138 ms 64 bytes from 10.10.10.10: icmp_seq=17 ttl=64 time=0.139 ms 64 bytes from 10.10.10.10: icmp_seq=18 ttl=64 time=0.139 ms 64 bytes from 10.10.10.10: icmp_seq=19 ttl=64 time=0.139 ms

Please Log in to join the conversation.

More
3 years 3 months ago #276565 by WKS-3D
but in Probe Basic Lathe after a short time a window opens with the message:
Code:
Unexpected realtime delay on task  0 with period 100000 This Message  will only display once per  session. Run the Latency Test and  resolve before continuing.

I have now actually done everything that was described to me above

Please Log in to join the conversation.

More
3 years 3 months ago #276566 by tommylight
Ping is OK, latency is not OK.
Hold down SHIFT button after power on, choose "advanced options ..... " see if you can choose the 6.1 kernel and try latency test again.

Please Log in to join the conversation.

Time to create page: 0.079 seconds
Powered by Kunena Forum