From owner-freebsd-net@FreeBSD.ORG  Mon Aug 11 12:10:07 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id C0A3037B401; Mon, 11 Aug 2003 12:10:07 -0700 (PDT)
Received: from kdmail2.netcologne.de (kdmail2.netcologne.de [194.8.194.86])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7197E43FBD; Mon, 11 Aug 2003 12:10:06 -0700 (PDT)
	(envelope-from djanssen@netcologne.de)
Received: from kevelaer (spam2.netcologne.de [194.8.203.34] (may be forged))
	by kdmail2.netcologne.de (Mirapoint Messaging Server MOS 2.9.3.5)
	with SMTP id ACV70136;
	Mon, 11 Aug 2003 21:10:03 +0200 (CEST)
From: Dirk Janssen <djanssen@netcologne.de>
To: <wpaul@FreeBSD.ORG>
X-Mailer: PocoMail 2.64 (1120) - Licensed Version
Date: Mon, 11 Aug 2003 21:10:03 +0200
In-Reply-To: <20030811165617.AA3CD37B425@hub.freebsd.org>
Message-ID: <200381121103.553835@kevelaer>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
cc: freebsd-net@FreeBSD.ORG
Subject: Re: Trouble with 5.1-RELEASE and Broadcom BCM5704C
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Aug 2003 19:10:08 -0000

Hi Bill,

>The BCM5704 has a smaller memory buffer space than earlier NICs,=
 and the
>bge(4) driver up to 5.1-RELEASE failed to take this into=
 account. I
>checked in a fix for this to 5-CURRENT and 4-STABLE yesterday.=
 You can
>apply the following workaround on your 5.1-RELEASE systems to=
 fix this
>(same workaround will work on 4.8-RELEASE as well):
>
>- Bring up /sys/dev/bge/if_bge.c in your favorite editor. -=
 Search for
>the following line of code:
>
>        CSR_WRITE_4(sc, BGE_BMAN_MBUFPOOL_LEN, 0x18000);
>
>It should appear twice in the bge_blockinit() function. - Change=
 0x18000
>to 0x10000 in both places. - Recompile your kernel and/or=
 if_bge.ko
>module.

thanks for the information about this workaround. I will try it=
 out 
tomorrow and give you a feedback.

Regards,

Dirk Janssen