From owner-freebsd-amd64@FreeBSD.ORG Sun Jan 21 03:20:18 2007 Return-Path: X-Original-To: freebsd-amd64@hub.freebsd.org Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 99EE916A400 for ; Sun, 21 Jan 2007 03:20:18 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id 89BD713C43E for ; Sun, 21 Jan 2007 03:20:18 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l0L3KIle049169 for ; Sun, 21 Jan 2007 03:20:18 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l0L3KHPa049168; Sun, 21 Jan 2007 03:20:17 GMT (envelope-from gnats) Date: Sun, 21 Jan 2007 03:20:17 GMT Message-Id: <200701210320.l0L3KHPa049168@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: "Guy F. Boyd" Cc: Subject: Re: amd64/106918: Asus P5B with internal RealTek PCIe Ethernet X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Guy F. Boyd" List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Jan 2007 03:20:18 -0000 The following reply was made to PR amd64/106918; it has been noted by GNATS. From: "Guy F. Boyd" To: , Cc: Subject: Re: amd64/106918: Asus P5B with internal RealTek PCIe Ethernet Date: Sat, 20 Jan 2007 22:06:46 -0500 Hello! I just experienced something very similar with an Asus P5B/intel with an on-board Realtek PCIe Ethernet, with telnet(1) and ftp(1) on FreeBSD bullwinkle 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #1: Mon Jan 15 16:36:51 EST 2007 root@bullwinkle:/usr/obj/usr/src/sys/GENERIC i386 for me, the symptoms disappeared by removing -rxcsum and -txcsum from the interface. Maybe this is a work-around. For reference, comparison was against a 3com 3c905tx PCI (xl0) in the same machine, configured identically ( same IP number, same local network ) on an alternate boot. The remote system in both cases was an ancient RELENG-3 testbed. Note that connecting to remote RELENG-6 systems did not exhibit the problem hangs with rxcsum/txcsum enabled. All test traffic traversed a RELENG-6 natd/ipfw gateway. No connections to hosts on the same LAN showed hung behavior ( but there are no pre-RELENG-6 boxes to test against on the local LAN at the moment ). Hope this helps.