From owner-freebsd-current@FreeBSD.ORG Mon Jun 15 12:16:33 2009 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A2E031065670; Mon, 15 Jun 2009 12:16:33 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from acme.spoerlein.net (cl-43.dus-01.de.sixxs.net [IPv6:2a01:198:200:2a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 19BB38FC26; Mon, 15 Jun 2009 12:16:32 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from roadrunner.spoerlein.net (e180144010.adsl.alicedsl.de [85.180.144.10]) by acme.spoerlein.net (8.14.3/8.14.3) with ESMTP id n5FCGVNA021524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 15 Jun 2009 14:16:31 +0200 (CEST) (envelope-from uqs@spoerlein.net) Received: from roadrunner.spoerlein.net (localhost [127.0.0.1]) by roadrunner.spoerlein.net (8.14.3/8.14.3) with ESMTP id n5FCGP92006289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 14:16:25 +0200 (CEST) (envelope-from uqs@spoerlein.net) Received: (from uqs@localhost) by roadrunner.spoerlein.net (8.14.3/8.14.3/Submit) id n5FCGPol006288; Mon, 15 Jun 2009 14:16:25 +0200 (CEST) (envelope-from uqs@spoerlein.net) Date: Mon, 15 Jun 2009 14:16:23 +0200 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Pyun YongHyeon Message-ID: <20090615121623.GA1479@roadrunner.spoerlein.net> Mail-Followup-To: Pyun YongHyeon , current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.19 (2009-01-05) Cc: current@FreeBSD.org Subject: ale(4): Problems with tso, rxcsum and/or txcsum X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jun 2009 12:16:33 -0000 Hello Pyun, I have connection problems with the onboard GigE of an Asus P5Q board, using a recent 8-CURRENT ale0: port 0xdc00-0xdc7f mem 0xfe9c0000-0xfe9fffff irq 17 at device 0.0 on pci2 ale0: 960 Tx FIFO, 1024 Rx FIFO ale0: Using 1 MSI messages. ale0: 4GB boundary crossed, switching to 32bit DMA addressing mode. miibus0: on ale0 ale0: Ethernet address: 00:24:8c:36:3e:10 ale0: [FILTER] ale0: link state changed to UP ale0@pci0:2:0:0: class=0x020000 card=0x82261043 chip=0x10261969 rev=0xb0 hdr=0x00 vendor = 'Attansic (Now owned by Atheros)' device = 'PCI-E ETHERNET CONTROLLER (AR8121/AR8113 )' class = network subclass = ethernet ale0: flags=8843 metric 0 mtu 1500 options=311b ether 00:24:8c:36:3e:10 inet 192.168.0.146 netmask 0xffffff00 broadcast 192.168.0.255 media: Ethernet autoselect (100baseTX ) status: active When transferring data to the machine at ~10MB/s (100Mbit network only) the ssh connection will die after a couple of minutes with Disconnecting: Bad packet length 1592360521. After disabling tso, txcsum and rxcsum the connection seems to be stable, though. I fail to figure out a pattern, though. Do I need to down/up the interface for changes to tso or {tr}xcsum to have any effect? Right now I'm rsyncing several GB to the machine and the connection seems stable even though I re-activated tso, rxcum and txcsum. This is rather weird ... Are problems with this chip revision known? Cheers, Ulrich Spörlein -- http://www.dubistterrorist.de/