Mesa 7i92 Read Error
Thanks for the suggestion. The /etc/network/interfaces file had:
auto eth0
iface eth0 inet static
address 10.10.10.1
netmask 255.255.255.0I changed it to
auto eth0
iface eth0 inet static
address 10.10.10.12
gateway 10.10.10.1
dns-nameservers 10.10.10.1On the test computer, the program ran for 24 hours without an error! I made the same changes on the computer hooked to the lathe, and it got the read error on the 7i92 after about 15 minutes.
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
- Posts: 19188
- Thank you received: 6432
Also check the other computer if it has an intel ethernet card, there is a line that PCW recomends to use with coalescence set to 0, that should inprove things a lot, i can not recal the exact line but do a search for it, it should be easy to find.
Not the one with irq coalescence, the one with eth.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
To verify that you have the latest firmware you can run this command:
mesaflash --device 7i92 --addr 10.10.10.10 --verbose
Please Log in or Create an account to join the conversation.
hardware-irq-coalesce-rx-usecs 0to the interfaces file.
It almost halved the ping time to the 0.150 to 0.175 range, but it made the read error happen even faster. I had three consecutive tests that all errored in less than 15 minutes.
The computer network chip on the lathe machine is an Intel I217-V
Please Log in or Create an account to join the conversation.
mesaflash --device 7i92 --addr 10.10.10.10 --verboseand got the following output
ETH device 7I92 at ip=10.10.10.10
Communication:
transport layer: ethernet IPv4 UDP
ip address: 10.10.10.10
mac address: 00:60:1B:11:00:72
protocol: LBP16 version 3
Board info:
Flash size: 16Mb (id: 0x14)
Connectors count: 2
Pins per connector: 17
Connectors names: P2 P1
FPGA type: 6slx9tqg144
Number of leds: 4
Board firmware info:
memory spaces:
0: HostMot2 (registers, RW, 32-bit) [size=64K]
1: KSZ8851 (registers, RW, 16-bit)
2: EtherEEP (EEPROM, RW, 16-bit) , page size: 1, erase size: 1
3: FPGAFlsh (flash, RW, 32-bit) [size=16M], page size: 256, erase size: 65536
4: Timers (memory, RW, 16-bit)
6: LBP16RW (memory, RW, 16-bit)
7: LBP16RO (memory, RO, 16-bit)
[space 0] HostMot2
[space 2] Ethernet eeprom:
mac address: 00:60:1B:11:00:72
ip address: 10.10.10.10
board name: 7I92
user leds: eth debug
[space 3] FPGA flash eeprom:
flash size: 16Mb (id: 0x14)
[space 4] timers:
uSTimeStampReg: 0x4C22
WaituSReg: 0x0000
HM2Timeout: 0x0000
[space 6] LBP16 control/status:
packets received: all 97, UDP 19, bad 0
packets sended: all 20, UDP 19, bad 0
parse errors: 0, mem errors 0, write errors 0
error flags: 0x0000
debug LED ptr: 0x0008
scratch: 0x0000
[space 7] LBP16 info:
board name: 7I92
LBP16 protocol version 3
board firmware version 17
IP address jumpers at boot: fixed from EEPROM
I ran another test, and noticed with the new code that the INT light was on after the failure. According to your earlier post, this means that it failed on communication, not a power interruption.
I got the 7i92M that you sent for testing. Thanks! I've only run one test with it, and it ran for about 3 hours before getting the read error. This mostly confirms that it's not the board. Since I was getting such long runs on my test machine (the last one was 26 hours without a failure), I've reinstalled LinuxCNC + Debian Jessie from the .ISO image on the website. I'm currently running some tests. It might be a while before I have the results, since I won't be able to work on it for several weeks...
Please Log in or Create an account to join the conversation.
Dumping the tmax values before and after a read error might provide a bit more insight
as would looking at the kernel log to see if the Ethernet link status changed
To dump the tmax parameters:
halcmd show param *.tmax
to look at the last few kernel log entries
dmesg | tail -n 10
Please Log in or Create an account to join the conversation.
- tommylight
-
- Away
- Moderator
-
- Posts: 19188
- Thank you received: 6432
I tried adding
hardware-irq-coalesce-rx-usecs 0
I do not recal ever PCW mentioning " IRQ coalescence ", Pl7i92 mentions it all the time.
PCW always writes " something ETH coalescence set to 0 ", not IRQ!
Again, i do not know if it makes any diference ( it should ), but could you please try that and report back.
I did try it on a Dell E6510 that has terrible latency and i use it to do tests with it and a 7i92, it went from erroring after 1 to 4 minutes to over 25 minutes.
Just a sec....
forum.linuxcnc.org/27-driver-boards/3559...ethernet-mesa-boards
Give it a try, see if it helps.
Please Log in or Create an account to join the conversation.
etc/network/interfaces file
auto eth0
iface eth0 inet static
address 10.10.10.12
netmask 255.255.255.0Ethernet connection 1 - IPv4 Settings
Address 10.10.10.12
Netmask 8
Gateway 10.10.10.1
DNS servers 10.10.10.1I installed ethtool
sudo apt-get install ethtoolI ran
ping 10.10.10.10before and after I issued this command
sudo ethtool -C eth0 rx-usecs 0The results of the ping are shown in the attachment
The average ping dropped from 0.406 to 0.257, a 37% decrease. I saw something I saw before and discounted - the initial ping time was much longer than the remaining pings. I'm not sure if anything can be done about this.
I ran a test on the lathe computer, again using only the 7i92M and an external 5V power supply. The test ran for 18 hours without an error. I had to stop it at that point because I was going to be away from it for several weeks.
So, very promising results so far. When I get back to it, I want to test it with the 7i92 in the electronics enclosure. I want to see if it's just the ethtool command that's giving better results, or the other changes I made to network settings.
I see that I can make the ethtool changes persistent by adding the following to the /etc/network/interfaces file
pre-up /sbin/ethtool -C eth0 rx-usecs 0I also would like to be able to put the computer back on my local ethernet, so that's another thing to test. For this i'll have to change the settings made to Ethernet connection1, since they disable all other ethernet connections.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.