Mesa hm2/hm2_7i96s.0: error finishing read

JT
Topic Author
Away
Administrator

3 years 10 months ago #259105 by JT

Replied by JT on topic Mesa hm2/hm2_7i96s.0: error finishing read

rodw wrote:
There must be more at work here than just Ping times. John's are very good.

Did you see my max time?0.407

JT

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

rodw
Offline
Platinum Member

3 years 10 months ago #259135 by rodw

Replied by rodw on topic Mesa hm2/hm2_7i96s.0: error finishing read

overnight no errors . Since your longer run anyway

Code:

packing@packing:~$ halcmd show param hm2*tmax*
Parameters:
Owner   Type  Dir         Value  Name
    93  s32   RW              0  hm2_7i76e.0.read-request.tmax
    93  bit   RO          FALSE  hm2_7i76e.0.read-request.tmax-increased
    93  s32   RW         909760  hm2_7i76e.0.read.tmax
    93  bit   RO          FALSE  hm2_7i76e.0.read.tmax-increased
    93  s32   RW         489900  hm2_7i76e.0.write.tmax
    93  bit   RO          FALSE  hm2_7i76e.0.write.tmax-increased

Ping times

Code:

64 bytes from 10.10.10.10: icmp_seq=19 ttl=64 time=0.455 ms
64 bytes from 10.10.10.10: icmp_seq=20 ttl=64 time=0.425 ms
64 bytes from 10.10.10.10: icmp_seq=21 ttl=64 time=0.434 ms
64 bytes from 10.10.10.10: icmp_seq=22 ttl=64 time=0.498 ms
64 bytes from 10.10.10.10: icmp_seq=23 ttl=64 time=0.500 ms
64 bytes from 10.10.10.10: icmp_seq=24 ttl=64 time=0.510 ms
64 bytes from 10.10.10.10: icmp_seq=25 ttl=64 time=0.465 ms
^C
--- 10.10.10.10 ping statistics ---
25 packets transmitted, 25 received, 0% packet loss, time 24366ms
rtt min/avg/max/mdev = 0.245/0.465/0.698/0.074 ms
packing@packing:~$ 

max ping time = 0.510

Code:

  *-network
       description: Ethernet interface
       product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: enp3s0

Ahh, on this PC, the change to the driver actually stuck

Code:

packing@packing:~$ sudo ethtool -i enp3s0
driver: r8168
version: 8.050.03-NAPI

Something odd happened as the driver was rebuilt when I changes linux-headers, not when I installed the driver.
Then it worked...

PS. not playing with this one anymore!

RodW
MrRodW.au
Youtube

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

tommylight
Offline
Moderator

3 years 10 months ago #259136 by tommylight

Replied by tommylight on topic Mesa hm2/hm2_7i96s.0: error finishing read

rodw wrote:
rtt min/avg/max/mdev = 0.245/0.465/0.698/0.074 ms

max ping time = 0.510

Nope, max ping time 0.698.
Usually the first one or two replies are longer, then settle.
min/ avg/ max/ mdev
0.245/0.465/0.698/0.074 ms

www.youtube.com/@toma.cnc1
www.youtube.com/@toma.3d
www.youtube.com/@tomapc

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

tommylight
Offline
Moderator

3 years 10 months ago #259137 by tommylight

Replied by tommylight on topic Mesa hm2/hm2_7i96s.0: error finishing read

Cr@p, it broke the formating!

www.youtube.com/@toma.cnc1
www.youtube.com/@toma.3d
www.youtube.com/@tomapc

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

rodw
Offline
Platinum Member

3 years 10 months ago #259140 by rodw

Replied by rodw on topic Mesa hm2/hm2_7i96s.0: error finishing read

tommylight wrote:

rodw wrote:
rtt min/avg/max/mdev = 0.245/0.465/0.698/0.074 ms

max ping time = 0.510

Nope, max ping time 0.698.
Usually the first one or two replies are longer, then settle.
min/ avg/ max/ mdev
0.245/0.465/0.698/0.074 ms

Tommy, yses .510 is after the first slower ping.
But the point is pings are worse than Johns and does not get an error finishing read and TMAX values are way lower...
The queston is why?

RodW
MrRodW.au
Youtube

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

tommylight
Offline
Moderator

3 years 10 months ago #259144 by tommylight

Replied by tommylight on topic Mesa hm2/hm2_7i96s.0: error finishing read

I would venture a guess at the way the driver requests interrupts to hardware, but i am not willing to go deep into that, especially since you already did a lot of work in figuring out solutions and what drivers work, so thank you for the time and effort you put into it.
Did anyone try ping with bigger frames/packets?
Pretty sure the size will mess response times quickly on the kernels with issues.
Or maybe, just maybe there is something wrong in those kernels in the way they handle UDP transport?
Ping is TCP/IP/ICMP, Mesa uses UDP if i am not mistaken, and so did Quake 3, the game. Quake had a way to switch to TCP/IP but that was laggy as hell with the limited bandwidth we had.

www.youtube.com/@toma.cnc1
www.youtube.com/@toma.3d
www.youtube.com/@tomapc

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

Moderators: PCW, jmelson

Time to create page: 0.094 seconds