Mesa hm2/hm2_7i96s.0: error finishing read

More
3 years 11 months ago #256096 by scotth
The ping times are about the same on Debian, but no errors.

sh@debian:~$ uname -a
Linux debian 4.19.0-17-rt-amd64 #1 SMP PREEMPT RT Debian 4.19.194-2 (2021-06-21) x86_64 GNU/Linux


sh@debian:~$ ping 10.10.10.10
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.477 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.399 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.279 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.280 ms
64 bytes from 10.10.10.10: icmp_seq=5 ttl=64 time=0.305 ms
64 bytes from 10.10.10.10: icmp_seq=6 ttl=64 time=0.309 ms
64 bytes from 10.10.10.10: icmp_seq=7 ttl=64 time=0.312 ms
64 bytes from 10.10.10.10: icmp_seq=8 ttl=64 time=0.312 ms
64 bytes from 10.10.10.10: icmp_seq=9 ttl=64 time=0.328 ms
64 bytes from 10.10.10.10: icmp_seq=10 ttl=64 time=0.319 ms
64 bytes from 10.10.10.10: icmp_seq=11 ttl=64 time=0.310 ms
64 bytes from 10.10.10.10: icmp_seq=12 ttl=64 time=0.306 ms
64 bytes from 10.10.10.10: icmp_seq=13 ttl=64 time=0.270 ms
64 bytes from 10.10.10.10: icmp_seq=14 ttl=64 time=0.208 ms
64 bytes from 10.10.10.10: icmp_seq=15 ttl=64 time=0.356 ms
64 bytes from 10.10.10.10: icmp_seq=16 ttl=64 time=0.302 ms
64 bytes from 10.10.10.10: icmp_seq=17 ttl=64 time=0.301 ms
64 bytes from 10.10.10.10: icmp_seq=18 ttl=64 time=0.361 ms
64 bytes from 10.10.10.10: icmp_seq=19 ttl=64 time=0.253 ms
64 bytes from 10.10.10.10: icmp_seq=20 ttl=64 time=0.328 ms
64 bytes from 10.10.10.10: icmp_seq=21 ttl=64 time=0.284 ms
64 bytes from 10.10.10.10: icmp_seq=22 ttl=64 time=0.314 ms
64 bytes from 10.10.10.10: icmp_seq=23 ttl=64 time=0.283 ms
64 bytes from 10.10.10.10: icmp_seq=24 ttl=64 time=0.306 ms
64 bytes from 10.10.10.10: icmp_seq=25 ttl=64 time=0.361 ms
64 bytes from 10.10.10.10: icmp_seq=26 ttl=64 time=0.388 ms
64 bytes from 10.10.10.10: icmp_seq=27 ttl=64 time=0.312 ms

--- 10.10.10.10 ping statistics ---
27 packets transmitted, 27 received, 0% packet loss, time 656ms
rtt min/avg/max/mdev = 0.208/0.317/0.477/0.050 ms

Please Log in or Create an account to join the conversation.

More
3 years 11 months ago #256101 by PCW
It looks like you do not have IRQ coalescing disabled
try the ping times after:

sudo ethtool -C [your-ethernet-device-name] rx-usecs 0

Please Log in or Create an account to join the conversation.

More
3 years 11 months ago #256110 by scotth
This is on Debian

sh@debian:~$ sudo ethtool -C eno1 rx-usecs 0
[sudo] password for sh:
sudo: ethtool: command not found

Please Log in or Create an account to join the conversation.

More
3 years 11 months ago #256112 by scotth
Yes, found it, and it makes a lot of difference.

64 bytes from 10.10.10.10: icmp_seq=62 ttl=64 time=0.178 ms
64 bytes from 10.10.10.10: icmp_seq=63 ttl=64 time=0.189 ms
64 bytes from 10.10.10.10: icmp_seq=64 ttl=64 time=0.168 ms
64 bytes from 10.10.10.10: icmp_seq=65 ttl=64 time=0.205 ms
64 bytes from 10.10.10.10: icmp_seq=66 ttl=64 time=0.211 ms
64 bytes from 10.10.10.10: icmp_seq=67 ttl=64 time=0.198 ms
64 bytes from 10.10.10.10: icmp_seq=68 ttl=64 time=0.206 ms
^C
--- 10.10.10.10 ping statistics ---
68 packets transmitted, 68 received, 0% packet loss, time 654ms
rtt min/avg/max/mdev = 0.154/0.198/0.220/0.019 ms
The following user(s) said Thank You: rodw

Please Log in or Create an account to join the conversation.

More
3 years 11 months ago #256113 by scotth
How do I make this stay? It reverts after reboot.

Please Log in or Create an account to join the conversation.

More
3 years 11 months ago #256114 by rodw
The following user(s) said Thank You: scotth

Please Log in or Create an account to join the conversation.

Moderators: PCW, jmelson
Time to create page: 0.199 seconds
Powered by Kunena Forum