please use [email protected] on all future replies.
On Sun, 2012-03-04 at 23:42 -0500, Marcelo Pereira wrote: > Hello, > > > I have been struggling to use a NIC Intel e1000e, without success, for > days!! > > > I'm using the latest version of the driver (1.9.5), the kernel or the > server is 2.6.18. > > > It's goes up and works pretty well, until I need to do some heavy > procedure (DRBD sync process, for example). > > > The ethtool output doesn't say anything weird. However, all the > sudden, I have a gazillion of error on the interface: this is an error pattern we have likely seen before, but we need more info before we can make suggestions. you didn't mention any of the regular details we need. lspci -vvv ethtool -e eth2 dmidecode full dmesg from boot all these things should be attached to a new bug at https://sourceforge.net/tracker/?group_id=42302&atid=447449 > > > # ifconfig eth2 > eth2 Link encap:Ethernet HWaddr 68:05:CA:01:F6:FF > inet addr:192.168.69.1 Bcast:192.168.69.255 > Mask:255.255.255.0 > inet6 addr: fe80::6a05:caff:fe01:f6ff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:38562086 errors:9251359553430 > dropped:1541893258905 overruns:0 frame:6167573035620 > TX packets:141830787 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:3429005890 (3.1 GiB) TX bytes:212307672425 (197.7 > GiB) > Interrupt:177 Memory:c6fe0000-c7000000 > > > # ethtool -S eth2 > NIC statistics: > rx_packets: 206196987401 > tx_packets: 206300243141 > rx_bytes: 209741279230 > tx_bytes: 418498371679 > rx_broadcast: 206158430780 > tx_broadcast: 206158430233 > rx_multicast: 206158430196 > tx_multicast: 206158430206 > rx_errors: 1236950580960 > tx_errors: 0 > tx_dropped: 0 > multicast: 206158430196 > collisions: 0 > rx_length_errors: 412316860320 > rx_over_errors: 0 > rx_crc_errors: 206158430160 > rx_frame_errors: 206158430160 > rx_no_buffer_count: 206158430160 > rx_missed_errors: 206158430160 > tx_aborted_errors: 0 > tx_carrier_errors: 0 > tx_fifo_errors: 0 > tx_heartbeat_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 > tx_restart_queue: 0 > rx_long_length_errors: 206158430160 > rx_short_length_errors: 206158430160 > rx_align_errors: 206158430160 > tx_tcp_seg_good: 206171367854 > tx_tcp_seg_failed: 206158430160 > rx_flow_control_xon: 206158430160 > rx_flow_control_xoff: 206158430160 > tx_flow_control_xon: 206158430160 > tx_flow_control_xoff: 206158430160 > rx_long_byte_count: 209741279230 > rx_csum_offload_good: 38561480 > rx_csum_offload_errors: 0 > rx_header_split: 0 > alloc_rx_buff_failed: 0 > tx_smbus: 206158430160 > rx_smbus: 206158430160 > dropped_smbus: 206158430160 > rx_dma_failed: 0 > tx_dma_failed: 0 > > > Just for the records, here is the ethtool's output, a couple of > "seconds" before the crash: > > > # ethtool -S eth2 > NIC statistics: > rx_packets: 568137905 > tx_packets: 154624696 > rx_bytes: 849530810286 > tx_bytes: 14357782180 > rx_broadcast: 5193 > tx_broadcast: 387 > rx_multicast: 283 > tx_multicast: 102 > rx_errors: 0 > tx_errors: 0 > tx_dropped: 0 > multicast: 283 > collisions: 0 > rx_length_errors: 0 > rx_over_errors: 0 > rx_crc_errors: 0 > rx_frame_errors: 0 > rx_no_buffer_count: 0 > rx_missed_errors: 0 > tx_aborted_errors: 0 > tx_carrier_errors: 0 > tx_fifo_errors: 0 > tx_heartbeat_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 > tx_restart_queue: 0 > rx_long_length_errors: 0 > rx_short_length_errors: 0 > rx_align_errors: 0 > tx_tcp_seg_good: 119928 > 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: 849530810286 > rx_csum_offload_good: 568133159 > rx_csum_offload_errors: 0 > rx_header_split: 0 > alloc_rx_buff_failed: 0 > tx_smbus: 0 > rx_smbus: 0 > dropped_smbus: 0 > rx_dma_failed: 0 > tx_dma_failed: 0 > > > I have already tried to turn auto negotiate on and off. I have set it > up to use Flow Control (ethtool -A eth2 rx on tx on). > > > The dmesg output says: "e1000e: eth2 NIC Link is Up 1000 Mbps Full > Duplex, Flow Control: None" > > > Several tests (more than 40min each). Several reboots (sometimes, it > crashes so badly that it freeze the server, and I have to > hard-reboot). Nothing can help me out with these NICs. I have two > identical servers, and I just need them to communicate to each other > without crashing. I have already changed the switches, cables, switch > ports and even the NIC's, for brand new units of the same e1000e > chipset. > > > Do you have any advice on what to do in order to get these network > interfaces running properly. I'll appreciate "any" information. > > > Thanks, > > > Marcelo > Boston, MA ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
