From owner-freebsd-net Mon Jun 10 20:28: 2 2002 Delivered-To: freebsd-net@freebsd.org Received: from pacbell.net (adsl-63-199-179-203.dsl.snfc21.pacbell.net [63.199.179.203]) by hub.freebsd.org (Postfix) with ESMTP id 75FA237B404; Mon, 10 Jun 2002 20:27:57 -0700 (PDT) Received: (from paleph@localhost) by pacbell.net (8.11.0/8.9.3) id g5B2x3M01869; Mon, 10 Jun 2002 19:59:03 -0700 From: paleph@pacbell.net Message-Id: <200206110259.g5B2x3M01869@pacbell.net> Subject: bge driver hangs seen with FreeBSD 4.5 To: freebsd-net@FreeBSD.ORG Date: Mon, 10 Jun 2002 19:59:02 -0700 (PDT) Cc: freebsd-question@FreeBSD.ORG X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org We're experiencing problems with the bge gigabit ethernet driver. We have a 100 Mbit ethernet network and are running 4.5 standard install kernels. We have two 4.5 machines A (with a bge gigabit driver) and machine B with ed0 interface. With small packets or low load, there is no problem sending data (via ftp) from B to A. However when we attempt to ftp a large file, about 16 Megabytes, from machine B to machine A, the connection immediately hangs and we start seeing timeout messages from the bge driver on machine A. The interface is completely locked up and machine A no longer responds to pings. If we abort the ftp request, machine A heals after a while (5 - 10 minutes). and things start working again. I grabbed the latest bge sources from FreeBSD.org and rebuilt a 4.5 kernel with them. The problem still occurs. Has anyone seen this hang before with 4.5 and know of any fixes? I've just started to look at it. I looked at the bug list and didn't see anything reported for the bge driver. Machine A is a Dell 4650. Paul Fronberg paleph@pacbell.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message