From: Michael Stone <mstone@mathom.us>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@vger.kernel.org
Subject: skge vs sk98lin
Date: Tue, 08 May 2007 08:00:36 -0400 [thread overview]
Message-ID: <20070508120034.GB1785@mathom.us> (raw)
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.
Mike Stone
next reply other threads:[~2007-05-08 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 12:00 Michael Stone [this message]
2007-05-08 17:15 ` skge vs sk98lin Stephen Hemminger
2007-05-14 14:20 ` Michael Stone
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=20070508120034.GB1785@mathom.us \
--to=mstone@mathom.us \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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).