lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <E22A6C23-AC23-4E24-B25D-7300CCF8D0FA@plansource.com>
Date:	Tue, 4 Aug 2015 16:11:29 +0000
From:	Dan Finn <Dan.Finn@...nsource.com>
To:	Yuval Mintz <Yuval.Mintz@...gic.com>,
	Dan Finn <Dan.Finn@...nsource.com>,
	netdev <netdev@...r.kernel.org>
Subject: Re: RX overrun errors building on several of our hosts

On 8/4/15, 5:39 AM, "Yuval Mintz" <Yuval.Mintz@...gic.com> wrote:


>> After implementing a new monitoring tool I've noticed that several of 
>>our
>> physical servers have increasing RX errors, all seem to be classified 
>>as overruns.
>
>Just to be sure we're looking at the same thing - are you referring to 
>the errors
>appearing on the bonding interfaces? I.e., ~10^(-6) of Rx packets are 
>errors?
>Also, how exactly do you classify such errors as overruns?
>
>If you can, please provide `ethtool -S' and `ethtool -I' outputs for
>base interfaces. Also, for good measures, please provide an `ethtool -d'
>output as well.
>
>Thanks,
>Yuval


Originally I had noticed the errors on the bond interface but if you look, 
the error count on the bonded interface is just a total of the errors on 
all of the slaves that are part of that bond (3 out of 4 slaves have 
overruns).  I’m classifying these as overruns simply because that is how 
they show up in the output from ifconfig.  

RX packets:100971364 errors:142 dropped:0 overruns:142 frame:0

That is a pretty small amount of errors compared to the total but it has 
me concerned that they are building on several of our servers.  If you’re 
saying this is something that doesn’t need to be worried about then I can 
live with that but it seems like ideally there should be 0 errors.

Here’s the output you asked for on one of the interfaces building errors:

ethtool -S em1
NIC statistics:
     [0]: rx_bytes: 4815733851
     [0]: rx_ucast_packets: 5582251
     [0]: rx_mcast_packets: 28173
     [0]: rx_bcast_packets: 1119087
     [0]: rx_discards: 0
     [0]: rx_phy_ip_err_discards: 0
     [0]: rx_skb_alloc_discard: 0
     [0]: rx_csum_offload_errors: 0
     [0]: tx_bytes: 3502081710
     [0]: tx_ucast_packets: 10437336
     [0]: tx_mcast_packets: 0
     [0]: tx_bcast_packets: 0
     [0]: tpa_aggregations: 193215
     [0]: tpa_aggregated_frames: 2709588
     [0]: tpa_bytes: 4055391762
     [0]: driver_filtered_tx_pkt: 0
     [1]: rx_bytes: 2167357708
     [1]: rx_ucast_packets: 2646259
     [1]: rx_mcast_packets: 0
     [1]: rx_bcast_packets: 0
     [1]: rx_discards: 0
     [1]: rx_phy_ip_err_discards: 0
     [1]: rx_skb_alloc_discard: 0
     [1]: rx_csum_offload_errors: 0
     [1]: tx_bytes: 1506529996
     [1]: tx_ucast_packets: 2099117
     [1]: tx_mcast_packets: 4
     [1]: tx_bcast_packets: 0
     [1]: tpa_aggregations: 275115
     [1]: tpa_aggregated_frames: 1289135
     [1]: tpa_bytes: 1851904085
     [1]: driver_filtered_tx_pkt: 0
     [2]: rx_bytes: 24963674569
     [2]: rx_ucast_packets: 19824451
     [2]: rx_mcast_packets: 0
     [2]: rx_bcast_packets: 1083
     [2]: rx_discards: 19
     [2]: rx_phy_ip_err_discards: 0
     [2]: rx_skb_alloc_discard: 0
     [2]: rx_csum_offload_errors: 0
     [2]: tx_bytes: 2019385415
     [2]: tx_ucast_packets: 5426273
     [2]: tx_mcast_packets: 0
     [2]: tx_bcast_packets: 5
     [2]: tpa_aggregations: 3479417
     [2]: tpa_aggregated_frames: 15708790
     [2]: tpa_bytes: 22447927794
     [2]: driver_filtered_tx_pkt: 0
     [3]: rx_bytes: 351708557
     [3]: rx_ucast_packets: 1149661
     [3]: rx_mcast_packets: 0
     [3]: rx_bcast_packets: 0
     [3]: rx_discards: 0
     [3]: rx_phy_ip_err_discards: 0
     [3]: rx_skb_alloc_discard: 0
     [3]: rx_csum_offload_errors: 0
     [3]: tx_bytes: 1703679951
     [3]: tx_ucast_packets: 4137632
     [3]: tx_mcast_packets: 0
     [3]: tx_bcast_packets: 0
     [3]: tpa_aggregations: 45426
     [3]: tpa_aggregated_frames: 181001
     [3]: tpa_bytes: 237385559
     [3]: driver_filtered_tx_pkt: 0
     [4]: rx_bytes: 939209699
     [4]: rx_ucast_packets: 1831789
     [4]: rx_mcast_packets: 0
     [4]: rx_bcast_packets: 0
     [4]: rx_discards: 0
     [4]: rx_phy_ip_err_discards: 0
     [4]: rx_skb_alloc_discard: 0
     [4]: rx_csum_offload_errors: 0
     [4]: tx_bytes: 2270315987
     [4]: tx_ucast_packets: 5025980
     [4]: tx_mcast_packets: 0
     [4]: tx_bcast_packets: 0
     [4]: tpa_aggregations: 77723
     [4]: tpa_aggregated_frames: 552723
     [4]: tpa_bytes: 801969855
     [4]: driver_filtered_tx_pkt: 0
     [5]: rx_bytes: 20134794297
     [5]: rx_ucast_packets: 16260597
     [5]: rx_mcast_packets: 0
     [5]: rx_bcast_packets: 0
     [5]: rx_discards: 0
     [5]: rx_phy_ip_err_discards: 0
     [5]: rx_skb_alloc_discard: 0
     [5]: rx_csum_offload_errors: 0
     [5]: tx_bytes: 1458283654
     [5]: tx_ucast_packets: 3058299
     [5]: tx_mcast_packets: 0
     [5]: tx_bcast_packets: 0
     [5]: tpa_aggregations: 2773813
     [5]: tpa_aggregated_frames: 12861563
     [5]: tpa_bytes: 18316820004
     [5]: driver_filtered_tx_pkt: 0
     [6]: rx_bytes: 305437769
     [6]: rx_ucast_packets: 1220063
     [6]: rx_mcast_packets: 0
     [6]: rx_bcast_packets: 0
     [6]: rx_discards: 0
     [6]: rx_phy_ip_err_discards: 0
     [6]: rx_skb_alloc_discard: 0
     [6]: rx_csum_offload_errors: 0
     [6]: tx_bytes: 2450697942
     [6]: tx_ucast_packets: 5219618
     [6]: tx_mcast_packets: 0
     [6]: tx_bcast_packets: 0
     [6]: tpa_aggregations: 43882
     [6]: tpa_aggregated_frames: 139260
     [6]: tpa_bytes: 177363439
     [6]: driver_filtered_tx_pkt: 0
     [7]: rx_bytes: 6476367230
     [7]: rx_ucast_packets: 6123976
     [7]: rx_mcast_packets: 0
     [7]: rx_bcast_packets: 121603
     [7]: rx_discards: 0
     [7]: rx_phy_ip_err_discards: 0
     [7]: rx_skb_alloc_discard: 0
     [7]: rx_csum_offload_errors: 0
     [7]: tx_bytes: 2715949918
     [7]: tx_ucast_packets: 6497153
     [7]: tx_mcast_packets: 0
     [7]: tx_bcast_packets: 0
     [7]: tpa_aggregations: 794362
     [7]: tpa_aggregated_frames: 4101833
     [7]: tpa_bytes: 5877064130
     [7]: driver_filtered_tx_pkt: 0
     rx_bytes: 60154283680
     rx_error_bytes: 0
     rx_ucast_packets: 54639047
     rx_mcast_packets: 28173
     rx_bcast_packets: 1241773
     rx_crc_errors: 0
     rx_align_errors: 0
     rx_undersize_packets: 0
     rx_oversize_packets: 0
     rx_fragments: 0
     rx_jabbers: 0
     rx_discards: 19
     rx_filtered_packets: 731881
     rx_mf_tag_discard: 0
     pfc_frames_received: 0
     pfc_frames_sent: 0
     rx_brb_discard: 0
     rx_brb_truncate: 0
     rx_pause_frames: 0
     rx_mac_ctrl_frames: 0
     rx_constant_pause_events: 0
     rx_phy_ip_err_discards: 0
     rx_skb_alloc_discard: 0
     rx_csum_offload_errors: 0
     tx_bytes: 17626924573
     tx_error_bytes: 0
     tx_ucast_packets: 41901408
     tx_mcast_packets: 4
     tx_bcast_packets: 5
     tx_mac_errors: 0
     tx_carrier_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
     tx_64_byte_packets: 15611
     tx_65_to_127_byte_packets: 19919087
     tx_128_to_255_byte_packets: 8832392
     tx_256_to_511_byte_packets: 2862303
     tx_512_to_1023_byte_packets: 956891
     tx_1024_to_1522_byte_packets: 9343904
     tx_1523_to_9022_byte_packets: 0
     tx_pause_frames: 0
     tpa_aggregations: 7682953
     tpa_aggregated_frames: 37543893
     tpa_bytes: 53765826628
     recoverable_errors: 0
     unrecoverable_errors: 0
     driver_filtered_tx_pkt: 0
     Tx LPI entry count: 0



ethtool -I em1
ethtool: bad command line argument(s)
For more information run ethtool -h

Maybe you meant lower case I?

ethtool -i em1
driver: bnx2x
version: 1.78.19-0
firmware-version: FFV7.10.17 bc 7.10.11
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes




ethtool -d em1:
https://raw.githubusercontent.com/danfinn/errors/master/ethtool_output.txt




Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ