From: Michael Stone <mstone@mathom.us>
To: Stephen Hemminger <shemminger@linux-foundation.org>
Cc: netdev@vger.kernel.org
Subject: Re: skge vs sk98lin
Date: Mon, 14 May 2007 10:20:26 -0400 [thread overview]
Message-ID: <20070514142024.GF1785@mathom.us> (raw)
In-Reply-To: <20070508101518.288d202a@freekitty>
On Tue, May 08, 2007 at 10:15:18AM -0700, Stephen Hemminger wrote:
>On Tue, 08 May 2007 08:00:36 -0400
>Michael Stone <mstone@mathom.us> wrote:
>> 2.6.21 seems to have fixed the stability issues I was seeing when using
>> the skge driver with the older sk98xx dual port fiber cards. There is
>> still one more lingering oddness: if I have *two* dual port cards in a
>> system, say eth2-5, I see traffic on eth2, eth3, and eth5, but nothing
>> on eth4. This seems to be consistent accross a couple of systems I've
>> tested; only the first card's second interface sees packets (e.g., with
>> tcpdump). If I reboot with the sk98lin driver on the same kernel I see
>> all traffic, as expected.
>
>Are the statistics changing? ie. ethtool -S eth4 and ifconfig eth4
Ok, I ran this for a lot longer and it seems less consistent than it did
at first. It now appears that there is no correlation between a NIC not
working and its order. In some cases the NICs both come up ok, and see
traffic for a while. I left one example running over the weekend, and
neither interface on one card was seeing traffic, and the interface
counters weren't increasing. In another case, one interface on one NIC
worked for a short period of time, then stopped. The interface counters
would increase by a few packets every 30 seconds or so. Any kind of
ethtool operation (e.g., ethtool -A eth4 autoneg off rx off tx off)
would cause the interface to start seeing traffic again, then eventually
go back to seeing only a few packets every few seconds.
Mike Stone
next prev parent reply other threads:[~2007-05-14 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 12:00 skge vs sk98lin Michael Stone
2007-05-08 17:15 ` Stephen Hemminger
2007-05-14 14:20 ` Michael Stone [this message]
2007-05-14 16:01 ` Stephen Hemminger
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=20070514142024.GF1785@mathom.us \
--to=mstone@mathom.us \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/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).