Mesa hm2/hm2_7i96s.0: error finishing read

More
3 years 10 months ago #259029 by PCW
What ping times do you get?

Please Log in to join the conversation.

More
3 years 10 months ago #259042 by JT
Code:
14 packets transmitted, 14 received, 0% packet loss, time 13296ms rtt min/avg/max/mdev = 0.078/0.083/0.116/0.009 ms

I'll run ping for a while and see what I get...

JT

Please Log in to join the conversation.

More
3 years 10 months ago #259049 by JT
A longer run
Code:
8195 packets transmitted, 8195 received, 0% packet loss, time 8390659ms rtt min/avg/max/mdev = 0.061/0.083/0.407/0.015 ms

JT

Please Log in to join the conversation.

More
3 years 10 months ago #259050 by rodw
There must be more at work here than just Ping times. John's are very good.

I've got  a J1900 here with Realtek drivers that has worse ping time yet has not triggered an error finishing read on overnight runs. Matter of fact I'm going to install it back on a machine that is having dramas with a similar PC. Running Bookworm and the   6.0 kernel. Thats bound to cause it to error!

INteresting though This machine generated unusable latency with the internal  wifi card connected back on Mint 17.3 with a compiled RT kernel. Now the Wifi is as good as gold. So there has been som eimprovement  with the kernel...

Please Log in to join the conversation.

More
3 years 10 months ago #259078 by JT
Did you see the max?

JT

Please Log in to join the conversation.

More
3 years 10 months ago #259080 by rodw
Around 800k

Please Log in to join the conversation.

More
3 years 10 months ago #259105 by JT

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 to join the conversation.

More
3 years 10 months ago #259135 by rodw
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!


 

Please Log in to join the conversation.

More
3 years 10 months ago #259136 by tommylight

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

Please Log in to join the conversation.

More
3 years 10 months ago #259137 by tommylight
Cr@p, it broke the formating! :(

Please Log in to join the conversation.

Time to create page: 0.188 seconds
Powered by Kunena Forum