From: "L F" <lfabio.linux@gmail.com>
To: "Florian Weimer" <fweimer@bfk.de>
Cc: "Urs Thuermann" <urs@isnogud.escape.de>,
"Bill Fink" <billfink@mindspring.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"Kok, Auke-jan H" <auke-jan.h.kok@intel.com>,
"James Chapman" <jchapman@katalix.com>,
netdev@vger.kernel.org
Subject: Re: e1000 driver and samba
Date: Tue, 18 Sep 2007 12:32:09 -0400 [thread overview]
Message-ID: <780b6f780709180932j5944b927p44ace42833e0230b@mail.gmail.com> (raw)
In-Reply-To: <82k5qoxfbk.fsf@mid.bfk.de>
This is the latest ethtool -S :
beehive:~# ethtool -S eth4
NIC statistics:
rx_packets: 33491526
tx_packets: 41410384
rx_bytes: 28384277429
tx_bytes: 46178788616
rx_broadcast: 3144
tx_broadcast: 2068
rx_multicast: 79
tx_multicast: 0
rx_errors: 0
tx_errors: 0
tx_dropped: 0
multicast: 79
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: 36256
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: 0
tx_tcp_seg_failed: 0
rx_flow_control_xon: 37420
rx_flow_control_xoff: 37420
tx_flow_control_xon: 0
tx_flow_control_xoff: 0
rx_long_byte_count: 28384277429
rx_csum_offload_good: 33478553
rx_csum_offload_errors: 0
rx_header_split: 0
alloc_rx_buff_failed: 0
tx_smbus: 0
rx_smbus: 0
dropped_smbus: 0
There have been no further deferred frames, in accordance to what was
posted above. However, as Urs very correctly points out, the problem
is still very much there. I am waiting for new and improved cables
(third batch) to see if that makes a difference.
I am also wondering if, perhaps, a layer3 managed switch with port
statistics may prove helpful.
To answer Bill's questions, memtest+ 1.70 was run overnight, it
totalled some fifty passes with no errors. I know that some maintain
that memtest is not a definitive RAM test, but it certainly catches
most problems.
As to the disk side of the equation, that is of course a possible
concern and I will be running a second, more intensive batch of tests.
However, the fact that virtualbox (running on the server) reports no
errors despite running through significant amounts of data (10GB+,
passing through samba via the tap device that is bridged to the
problematic ethernet) every day makes me fairly confident that the
disk side of the equation is not where the problem lies.
LF
next prev parent reply other threads:[~2007-09-18 16:32 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 2:04 e1000 driver and samba L F
2007-09-14 17:18 ` Kok, Auke
2007-09-14 18:40 ` L F
2007-09-14 20:59 ` Kok, Auke
2007-09-15 0:37 ` L F
2007-09-15 5:09 ` Bill Fink
2007-09-15 12:27 ` L F
2007-09-15 12:44 ` L F
2007-09-15 17:44 ` James Chapman
2007-09-15 19:07 ` Kok, Auke
2007-09-16 4:06 ` L F
2007-09-16 5:04 ` Kok, Auke
2007-09-17 16:42 ` L F
2007-09-17 17:02 ` Kok, Auke
2007-09-17 18:58 ` L F
2007-09-17 21:01 ` Brandeburg, Jesse
2007-09-18 6:03 ` Bill Fink
2007-09-18 7:45 ` Urs Thuermann
2007-09-18 8:47 ` Bill Fink
2007-09-18 13:39 ` Florian Weimer
2007-09-18 16:32 ` L F [this message]
2007-09-18 17:04 ` Tantilov, Emil S
2007-09-19 14:53 ` L F
2007-09-20 2:51 ` Bill Fink
2007-09-21 14:08 ` L F
2007-09-20 4:53 ` Bill Fink
2007-09-18 16:44 ` Bill Fink
2007-09-17 18:02 ` Rick Jones
2007-09-17 18:51 ` Kok, Auke
2007-09-16 16:24 ` James Chapman
2007-09-16 20:03 ` Kok, Auke
2007-09-16 4:07 ` L F
2007-09-14 18:26 ` Francois Romieu
2007-09-14 18:41 ` L F
-- strict thread matches above, loose matches on Subject: below --
2007-09-20 23:30 Bruce Cole
2007-09-21 14:13 ` L F
2007-09-21 18:21 ` Bruce Cole
2007-09-21 21:49 ` Francois Romieu
2007-09-21 22:01 ` Bruce Cole
2007-09-21 22:41 ` Francois Romieu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=780b6f780709180932j5944b927p44ace42833e0230b@mail.gmail.com \
--to=lfabio.linux@gmail.com \
--cc=auke-jan.h.kok@intel.com \
--cc=billfink@mindspring.com \
--cc=fweimer@bfk.de \
--cc=jchapman@katalix.com \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=urs@isnogud.escape.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).