> > eth3 Link encap:Ethernet HWaddr 00:23:7d:30:9c:e6
> > inet addr:10.10.50.243 Bcast:10.255.255.255 Mask:255.255.255.0
> > inet6 addr: fe80::223:7dff:fe30:9ce6/64 Scope:Link
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:36857 errors:804 dropped:0 overruns:0 frame:804
> > TX packets:14702 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:53602773 (51.1 MiB) TX bytes:1056006 (1.0 MiB)
> > Interrupt:17 Memory:fa000000-fa012800
> [...]
>
> This is on the bnx2 interface?
Yes. However I did some more tests today and saw that this particular port
had trouble getting the link from several switches (Enterasys, HP, 3Com,
...) and with different cables (it had a 2 meter CAT6 certified cable, so it
should be ok, but I also tested shorter cables), the other port of that NIC
didn't have that kind of problem, so I'm wondering if there is a problem
with this port or this position of the passthrough or similar (I have spoken
to local HP staff and they say that the passthrough shouldn't be the problem
here, but I can't find any other explanation).
> Please use 'ethtool -S eth3' to get more detailed statistics, and
> 'ethtool -t eth3' to run a self-test (note this will break the link
> temporarily), and send the output of these.
After finding the problem with the link I have configured the other port of
the bnx2 nic, eth2, which is getting the link ok this port seems to transfer
much better (lower errors and thus greater speed) I got like 40MB/s compared
to the 4 MB/s that I was getting out of the other one.
I'm sending current data for eth2 then:
eth2 Link encap:Ethernet HWaddr 00:23:7d:30:9c:e2
inet addr:10.10.50.243 Bcast:10.10.50.243 Mask:255.255.255.255
inet6 addr: fe80::223:7dff:fe30:9ce2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1411482 errors:1244 dropped:0 overruns:0 frame:1244
TX packets:396964 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2111018119 (1.9 GiB) TX bytes:28042522 (26.7 MiB)
Interrupt:16 Memory:f8000000-f8012800
NIC statistics:
rx_bytes: 2111017191
rx_error_bytes: 0
tx_bytes: 28042522
tx_error_bytes: 0
rx_ucast_packets: 1389861
rx_mcast_packets: 0
rx_bcast_packets: 21607
tx_ucast_packets: 396955
tx_mcast_packets: 6
tx_bcast_packets: 3
tx_mac_errors: 0
tx_carrier_errors: 0
rx_crc_errors: 1244
rx_align_errors: 0
tx_single_collisions: 0
tx_multi_collisions: 0
tx_deferred: 0
tx_excess_collisions: 0
tx_late_collisions: 0
tx_total_collisions: 0
rx_fragments: 6
rx_jabbers: 9
rx_undersize_packets: 0
rx_oversize_packets: 0
rx_64_byte_packets: 19844
rx_65_to_127_byte_packets: 1393
rx_128_to_255_byte_packets: 548
rx_256_to_511_byte_packets: 42
rx_512_to_1023_byte_packets: 0
rx_1024_to_1522_byte_packets: 1389641
rx_1523_to_9022_byte_packets: 0
tx_64_byte_packets: 4
tx_65_to_127_byte_packets: 396959
tx_128_to_255_byte_packets: 1
tx_256_to_511_byte_packets: 0
tx_512_to_1023_byte_packets: 0
tx_1024_to_1522_byte_packets: 0
tx_1523_to_9022_byte_packets: 0
rx_xon_frames: 0
rx_xoff_frames: 0
tx_xon_frames: 0
tx_xoff_frames: 0
rx_mac_ctrl_frames: 0
rx_filtered_packets: 2193
rx_ftq_discards: 0
rx_discards: 0
rx_fw_discards: 0
The test result is PASS
The test extra info:
register_test (offline) 0
memory_test (offline) 0
loopback_test (offline) 0
nvram_test (online) 0
interrupt_test (online) 0
link_test (online) 0
Hope this gives us some hints.
Regards.
--
Manty/BestiaTester -> http://manty.net
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140131110618.ga8...@www.manty.net
