From owner-freebsd-stable@FreeBSD.ORG Thu Jun 4 00:46:33 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F034F106564A for ; Thu, 4 Jun 2009 00:46:33 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from MMS3.broadcom.com (mms3.broadcom.com [216.31.210.19]) by mx1.freebsd.org (Postfix) with ESMTP id C9BA68FC13 for ; Thu, 4 Jun 2009 00:46:33 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from [10.9.200.131] by MMS3.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Wed, 03 Jun 2009 16:13:01 -0700 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Wed, 3 Jun 2009 16:13:01 -0700 From: "David Christensen" To: "Pete French" , "d@delphij.net" Date: Wed, 3 Jun 2009 16:13:01 -0700 Thread-Topic: mini-HEADSUP bce owners: please test Thread-Index: Acnkn6Jep8pLF63+TDO6PpuyqecCtgAAIhHQ Message-ID: <5D267A3F22FD854F8F48B3D2B523819339DFEA2BC0@IRVEXCHCCR01.corp.ad.broadcom.com> References: <4A26FF44.3040609@delphij.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-WSS-ID: 6639DCF738O9422936-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: "freebsd-stable@freebsd.org" , "davidch@FreeBSD.ORG" Subject: RE: mini-HEADSUP bce owners: please test X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jun 2009 00:46:34 -0000 > > David and I have committed some fixes to 7-STABLE tree, and I think=20 > > all important bce(4) fixes has been merged now. If you have bce(4)=20 > > interfaces PLEASE help us to test them, the simplest way of=20 > doing this=20 > > is to sync your code with RELENG_7 and rebuild kernel. [1] >=20 > I won't have timer to try this until friday at the earliest,=20 > but one question... is this likely to fix my infamous=20 > lagg/lacp issue ? I notice it isn't in the list of known=20 > issues. I will test anyway, but if you happen to be in that=20 > bit of code.... *does best winning smile* :-) That should be the packet length fix at line 5973 of if_bce.c. I did not test the teaming fix myself but another user provided a similar packet length fix which he claimed did fix the issue so I'm hopeful that this should work for you too. Dave