> -----Original Message-----
> From: Kristian Kielhofner [mailto:k...@kriskinc.com]
> Sent: Friday, October 25, 2013 12:01 PM
> To: e1000-devel@lists.sourceforge.net
> Subject: [E1000-devel] Intel I350, igb and
> overruns/rx_fifo_errors/queue drops
> 
> Hello,
> 
>   I have a brand new Dell R620 with four onboard Intel I350 ethernet
> controllers.  Under relatively high (but not that high) load the
> controllers report a significant number of overruns, rx_fifo_errors,
> and queue drops.
> 
>   I've tried disabling turbo, all C states, and setting for "Maximum
> Performance" in the BIOS with and without adding the "idle=poll"
> kernel command line option (with no effect).
> 
> Debian 7.2, Linux debian-test 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1
> x86_64 GNU/Linux
> 
> cpuinfo:
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 62
> model name      : Intel(R) Xeon(R) CPU E5-2690 v2 @ 3.00GHz
> stepping        : 4
> microcode       : 0x415
> cpu MHz         : 2999.520
> cache size      : 25600 KB
> physical id     : 0
> siblings        : 20
> core id         : 0
> cpu cores       : 10
> apicid          : 0
> initial apicid  : 0
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 13
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
> syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts
> rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64
> ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2
> x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm arat
> xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase
> smep erms
> bogomips        : 5999.04
> clflush size    : 64
> cache_alignment : 64
> address sizes   : 46 bits physical, 48 bits virtual
> power management:
> 
> x40 (dual 10 core with hyperthreading enabled)
> 
> Intel igb driver version 5.0.6 compiled from source
> 
> Various ethtool output:
> 
> root@debian-test:~# ethtool eth1
> Settings for eth1:
> Supported ports: [ TP ]
> Supported link modes:   10baseT/Half 10baseT/Full
>                        100baseT/Half 100baseT/Full
>                        1000baseT/Full
> Supported pause frame use: No
> Supports auto-negotiation: Yes
> Advertised link modes:  10baseT/Half 10baseT/Full
>                        100baseT/Half 100baseT/Full
>                        1000baseT/Full
> Advertised pause frame use: No
> Advertised auto-negotiation: Yes
> Speed: 1000Mb/s
> Duplex: Full
> Port: Twisted Pair
> PHYAD: 1
> Transceiver: internal
> Auto-negotiation: on
> MDI-X: Unknown
> Supports Wake-on: d
> Wake-on: d
> Current message level: 0x00000003 (3)
>       drv probe
> Link detected: yes
> root@debian-test:~# ethtool -g eth1
> Ring parameters for eth1:
> Pre-set maximums:
> RX: 4096
> RX Mini: 0
> RX Jumbo: 0
> TX: 4096
> Current hardware settings:
> RX: 256
> RX Mini: 0
> RX Jumbo: 0
> TX: 256
> 
> root@debian-test:~# ethtool -k eth1
> Features for eth1:
> rx-checksumming: on
> tx-checksumming: on
> tx-checksum-ipv4: on
> tx-checksum-unneeded: off [fixed]
> tx-checksum-ip-generic: off [fixed]
> tx-checksum-ipv6: on
> tx-checksum-fcoe-crc: off [fixed]
> tx-checksum-sctp: on
> scatter-gather: on
> tx-scatter-gather: on
> tx-scatter-gather-fraglist: off [fixed]
> tcp-segmentation-offload: on
> tx-tcp-segmentation: on
> tx-tcp-ecn-segmentation: off [fixed]
> tx-tcp6-segmentation: on
> udp-fragmentation-offload: off [fixed]
> generic-segmentation-offload: on
> generic-receive-offload: on
> large-receive-offload: off [fixed]
> rx-vlan-offload: on
> tx-vlan-offload: on
> ntuple-filters: off [fixed]
> receive-hashing: on
> highdma: on [fixed]
> rx-vlan-filter: on [fixed]
> vlan-challenged: off [fixed]
> tx-lockless: off [fixed]
> netns-local: off [fixed]
> tx-gso-robust: off [fixed]
> tx-fcoe-segmentation: off [fixed]
> fcoe-mtu: off [fixed]
> tx-nocache-copy: on
> loopback: off [fixed]
> root@debian-test:~# ethtool -S eth1
> NIC statistics:
>      rx_packets: 98621947
>      tx_packets: 73792461
>      rx_bytes: 8965579110
>      tx_bytes: 6772837894
>      rx_broadcast: 19171
>      tx_broadcast: 6
>      rx_multicast: 0
>      tx_multicast: 6
>      multicast: 0
>      collisions: 0
>      rx_crc_errors: 0
>      rx_no_buffer_count: 0
>      rx_missed_errors: 0
>      tx_aborted_errors: 0
>      tx_carrier_errors: 0
>      tx_window_errors: 0
>      tx_abort_late_coll: 0
>      tx_deferred_ok: 0
>      tx_single_coll_ok: 0
>      tx_multi_coll_ok: 0
>      tx_timeout_count: 0
>      rx_long_length_errors: 0
>      rx_short_length_errors: 0
>      rx_align_errors: 0
>      tx_tcp_seg_good: 5
>      tx_tcp_seg_failed: 0
>      rx_flow_control_xon: 0
>      rx_flow_control_xoff: 0
>      tx_flow_control_xon: 0
>      tx_flow_control_xoff: 0
>      rx_long_byte_count: 8965579110
>      tx_dma_out_of_sync: 0
>      tx_smbus: 0
>      rx_smbus: 0
>      dropped_smbus: 0
>      os2bmc_rx_by_bmc: 0
>      os2bmc_tx_by_bmc: 0
>      os2bmc_tx_by_host: 0
>      os2bmc_rx_by_host: 0
>      rx_errors: 0
>      tx_errors: 0
>      tx_dropped: 0
>      rx_length_errors: 0
>      rx_over_errors: 0
>      rx_frame_errors: 0
>      rx_fifo_errors: 19677204
>      tx_fifo_errors: 0
>      tx_heartbeat_errors: 0
>      tx_queue_0_packets: 9861111
>      tx_queue_0_bytes: 979485426
>      tx_queue_0_restart: 0
>      tx_queue_1_packets: 9461560
>      tx_queue_1_bytes: 813742796
>      tx_queue_1_restart: 0
>      tx_queue_2_packets: 9194491
>      tx_queue_2_bytes: 790726190
>      tx_queue_2_restart: 0
>      tx_queue_3_packets: 9104167
>      tx_queue_3_bytes: 782958362
>      tx_queue_3_restart: 0
>      tx_queue_4_packets: 9423037
>      tx_queue_4_bytes: 810418594
>      tx_queue_4_restart: 0
>      tx_queue_5_packets: 8440884
>      tx_queue_5_bytes: 725916034
>      tx_queue_5_restart: 0
>      tx_queue_6_packets: 8968600
>      tx_queue_6_bytes: 771299652
>      tx_queue_6_restart: 0
>      tx_queue_7_packets: 9338621
>      tx_queue_7_bytes: 803121406
>      tx_queue_7_restart: 0
>      rx_queue_0_packets: 78943683
>      rx_queue_0_bytes: 6874052975
>      rx_queue_0_drops: 19677204
>      rx_queue_0_csum_err: 0
>      rx_queue_0_alloc_failed: 0
>      rx_queue_1_packets: 2
>      rx_queue_1_bytes: 320
>      rx_queue_1_drops: 0
>      rx_queue_1_csum_err: 0
>      rx_queue_1_alloc_failed: 0
>      rx_queue_2_packets: 0
>      rx_queue_2_bytes: 0
>      rx_queue_2_drops: 0
>      rx_queue_2_csum_err: 0
>      rx_queue_2_alloc_failed: 0
>      rx_queue_3_packets: 20
>      rx_queue_3_bytes: 1999
>      rx_queue_3_drops: 0
>      rx_queue_3_csum_err: 0
>      rx_queue_3_alloc_failed: 0
>      rx_queue_4_packets: 0
>      rx_queue_4_bytes: 0
>      rx_queue_4_drops: 0
>      rx_queue_4_csum_err: 0
>      rx_queue_4_alloc_failed: 0
>      rx_queue_5_packets: 0
>      rx_queue_5_bytes: 0
>      rx_queue_5_drops: 0
>      rx_queue_5_csum_err: 0
>      rx_queue_5_alloc_failed: 0
>      rx_queue_6_packets: 1037
>      rx_queue_6_bytes: 83643
>      rx_queue_6_drops: 0
>      rx_queue_6_csum_err: 0
>      rx_queue_6_alloc_failed: 0
>      rx_queue_7_packets: 16
>      rx_queue_7_bytes: 2702
>      rx_queue_7_drops: 0
>      rx_queue_7_csum_err: 0
>      rx_queue_7_alloc_failed: 0
> 
>   Anything else to try here?
> 
> Thanks!
> 
> --
> Kristian Kielhofner
> 
So what does the interrupt configuration look like (cat /proc/interrupts)?  Are 
interrupts being shared?

What are you using as the test for this?  Does it still happen when using a 
different type of test like netperf or iperf?

Cheers,
John



------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
To learn more about Intel® Ethernet, visit 
http://communities.intel.com/community/wired

Reply via email to