From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Stone Subject: Re: skge vs sk98lin Date: Mon, 14 May 2007 10:20:26 -0400 Message-ID: <20070514142024.GF1785@mathom.us> References: <20070508120034.GB1785@mathom.us> <20070508101518.288d202a@freekitty> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Cc: netdev@vger.kernel.org To: Stephen Hemminger Return-path: Received: from vms042pub.verizon.net ([206.46.252.42]:58295 "EHLO vms042pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754113AbXENOUw (ORCPT ); Mon, 14 May 2007 10:20:52 -0400 Received: from osgiliath.mathom.us ([72.66.113.156]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JI100FT6BU9RAB3@vms042.mailsrvcs.net> for netdev@vger.kernel.org; Mon, 14 May 2007 09:20:34 -0500 (CDT) In-reply-to: <20070508101518.288d202a@freekitty> Content-disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Tue, May 08, 2007 at 10:15:18AM -0700, Stephen Hemminger wrote: >On Tue, 08 May 2007 08:00:36 -0400 >Michael Stone 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