netdev - Re: sky2 bonding problem, 802.3ad

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070215213135.GC30353@gospo.rdu.redhat.com>
Date:	Thu, 15 Feb 2007 16:31:36 -0500
From:	Andy Gospodarek <andy@...yhouse.net>
To:	Holger Eitzenberger <holger@...eitzenberger.de>
Cc:	shemminger@...ux-foundation.org,
	sk-drivers@...ts.linux-foundation.org, netdev@...r.kernel.org
Subject: Re: sky2 bonding problem, 802.3ad

On Thu, Feb 15, 2007 at 07:55:42PM +0100, Holger Eitzenberger wrote:
> Hi Steven,
> 
> I have problems using sky2 v1.10 with with bonding driver (802.3ad),
> on 'Marvell 88E8053 PCI-E Gigabit Ethernet Controller'.  I have attached
> the full lspci output.
> 
> My test was to setup a bond of two physical links (both links same
> hardware) and ping 192.168.11.10, which is the address of the switch
> itself.
> 
> I have tested v1.10 with kernel 2.6.19 and 2.6.16.36 (own backport),
> which despite the bonding problem runs fine.  Both, kernel 2.6.19 and
> 2.6.16.36 show the same behaviour.  The 802.3ad aware switch is a Dell
> PowerConnect 5324.  VLAN is not configured on all switch ports.  Another
> test on a host running kernel 2.6.18.2 with two e1000's bonded runs
> fine.  Using sk98lin (v8.41 & v10.0.4) worked also.


I get the impression that sky2 has never worked for you.  Is that
correct?  There was an skge problem I noticed a while ago where on reset
the multicast membership list was cleared.  

commit 758140900a82e3ed3bb2be1d4705dd352fe44825
Author: Stephen Hemminger <shemminger@...l.org>
Date:   Fri Dec 1 11:41:08 2006 -0800

    [PATCH] skge: don't clear MC state on link down

    I would rather fix Andy's problem by not clearing
    multicast information on link down.

    Also, add code to restore multicast state after ethtool phy reset.

    Signed-off-by: Stephen Hemminger <shemminger@...l.org>
    Signed-off-by: Jeff Garzik <jeff@...zik.org>



A patch Having this list cleared could stop you from receiving 802.3ad
PDUs.  I'll check skge and see if it has the same problem (I'm betting
on it).





-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html