Mesa hm2/hm2_7i96s.0: error finishing read

More
1 year 8 months ago #322793 by JT
Replied by JT on topic Mesa hm2/hm2_7i96s.0: error finishing read
Code:
nmcli device show GENERAL.DEVICE: enp6s0 GENERAL.TYPE: ethernet GENERAL.HWADDR: F0:2F:74:21:CE:6A GENERAL.MTU: 1500 GENERAL.STATE: 70 (connecting getting IP configuration) GENERAL.CONNECTION: Wired connection 1 GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveConnection/5 WIRED-PROPERTIES.CARRIER: on IP4.GATEWAY: -- IP6.ADDRESS[1]: fe80::9e6b:ff:fe8d:cbd5/64 IP6.GATEWAY: -- IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 1024

JT

Please Log in to join the conversation.

More
1 year 8 months ago #322838 by vre
Replied by vre on topic Mesa hm2/hm2_7i96s.0: error finishing read
For 2khz servo thread what max ping must have?

Please Log in to join the conversation.

More
1 year 8 months ago #322840 by PCW
Replied by PCW on topic Mesa hm2/hm2_7i96s.0: error finishing read
Say 200 uS after 10 minutes or so:

chrt 99 ping -i .0005 -c 600000 -q 10.10.10.10
 

Please Log in to join the conversation.

More
1 year 8 months ago #322841 by rodw
Replied by rodw on topic Mesa hm2/hm2_7i96s.0: error finishing read
The answer is always "it depends". In some kernel traces we did, at 1 kHz, the servo thread was done in around 200 usec and it slept for the remaining 800 usec. On a 2 Khz servo thread, it must be done in 500 usec so in theory, the hardware we had would meet the requirements.

Please Log in to join the conversation.

More
1 year 8 months ago #322868 by tommylight
Replied by tommylight on topic Mesa hm2/hm2_7i96s.0: error finishing read
Some posts just got deleted here????

Please Log in to join the conversation.

More
1 year 8 months ago #322880 by JT
Replied by JT on topic Mesa hm2/hm2_7i96s.0: error finishing read
I deleted my post because I had the nic set to 10.10.10.10 and the ping times were quite wrong.

JT

Please Log in to join the conversation.

More
1 year 8 months ago #322884 by tommylight
Replied by tommylight on topic Mesa hm2/hm2_7i96s.0: error finishing read

I deleted my post because I had the nic set to 10.10.10.10 and the ping times were quite wrong.

JT
That is what i was pointing out when the post disappeared on me! :)

Please Log in to join the conversation.

More
1 year 7 months ago #322920 by JT
Replied by JT on topic Mesa hm2/hm2_7i96s.0: error finishing read
So I've managed to get the PCI NIC working to access the internet and the onboard NIC to communicate with the 7i96S.
Code:
john@cave:~$ sudo lshw -C network   *-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:06:00.0        logical name: enp6s0        version: 06        serial: 68:1c:a2:12:f7:e6        size: 1Gbit/s        capacity: 1Gbit/s        width: 64 bits        clock: 33MHz        capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation        configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.1.0-29-rt-amd64 duplex=full firmware=rtl8168e-3_0.0.4 03/27/12 ip=192.168.1.59 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s        resources: irq:32 ioport:e000(size=256) memory:e0304000-e0304fff memory:e0300000-e0303fff   *-network        description: Ethernet interface        product: RTL8125 2.5GbE Controller        vendor: Realtek Semiconductor Co., Ltd.        physical id: 0        bus info: pci@0000:09:00.0        logical name: enp9s0        version: 04        serial: f0:2f:74:21:ce:6a        size: 100Mbit/s        capacity: 1Gbit/s        width: 64 bits        clock: 33MHz        capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation        configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=6.1.0-29-rt-amd64 duplex=full firmware=rtl8125b-2_0.0.2 07/13/20 ip=10.10.10.12 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s        resources: irq:35 ioport:d000(size=256) memory:fcd00000-fcd0ffff memory:fcd10000-fcd13fff

The first one is the PCI NIC and the second one the onboard NIC. One thing I noticed is the speed of the onboard NIC is 100Mbit/s even though it's a 2.5 GbE card, is that normal?

JT

Please Log in to join the conversation.

More
1 year 7 months ago #322921 by JT
Replied by JT on topic Mesa hm2/hm2_7i96s.0: error finishing read
ping test
Code:
john@cave:~$ sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10 [sudo] password for john: PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data. --- 10.10.10.10 ping statistics --- 60000 packets transmitted, 60000 received, 0% packet loss, time 60095ms rtt min/avg/max/mdev = 0.048/0.051/4.051/0.021 ms

JT

Please Log in to join the conversation.

More
1 year 7 months ago #322924 by JT
Replied by JT on topic Mesa hm2/hm2_7i96s.0: error finishing read
I tried the following grub kernel parameters but the PCI NIC would not work.
Code:
quiet isolcpus=11 idle=poll r8125.EEE=0 pcie_aspm=off quiet isolcpus=11 idle=poll pcie_aspm=off

I changed my grub kernel parameters to
Code:
quiet isolcpus=11 idle=poll

and did a ping test and my PCI NIC started working again as well
Code:
john@cave:~$ sudo chrt 99 ping -i .001 -c 60000 -q 10.10.10.10 [sudo] password for john: PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data. --- 10.10.10.10 ping statistics --- 60000 packets transmitted, 60000 received, 0% packet loss, time 60092ms rtt min/avg/max/mdev = 0.049/0.051/0.123/0.001 ms

JT

Please Log in to join the conversation.

Time to create page: 0.180 seconds
Powered by Kunena Forum