Code:
tx_bytes: 8981223237
tx_zero_rexmt: 52540499
tx_one_rexmt: 0
tx_many_rexmt: 0
tx_late_collision: 0
tx_fifo_errors: 0
tx_carrier_errors: 0
tx_excess_deferral: 0
tx_retry_error: 0
rx_frame_error: 0
rx_extra_byte: 0
rx_late_collision: 0
rx_runt: 0
rx_frame_too_long: 0
rx_over_errors: 45637
rx_crc_errors: 0
rx_frame_align_error: 0
rx_length_error: 0
rx_unicast: 74731071
rx_multicast: 9513
rx_broadcast: 5814
rx_packets: 74746398
rx_errors_total: 45637
tx_errors_total: 0
tx_deferral: 0
tx_packets: 52540499
rx_bytes: 76998702487
tx_pause: 99326
rx_pause: 4
rx_drop_frame: 497
My reasoning for not thinking "rx_over_error" is an overrun because 1) ifconfig says there are no overruns, but thinks it's a frame error:
Code:
eth1 Link encap:Ethernet HWaddr 00:04:4b:11:22:33
inet addr:192.168.1.101 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:74797253 errors:45637 dropped:0 overruns:0 frame:45637
TX packets:52596245 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3000
RX bytes:76658031534 (76.6 GB) TX bytes:9011899364 (9.0 GB)
Interrupt:43 Base address:0x2000
yet as seen in the ethtool stats, there are no frame errors. And 2) tx and rx flow-control is enabled on both the server (linux) and client (os x). That flow control on linux is telling os x to slow it's roll is evident by the ethtool stats output above; rx_pause shows activity.
Is it possible that either ethtool or ifconfig are lying?
Bookmarks