From owner-freebsd-current@FreeBSD.ORG Mon Jun 15 12:48:29 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 507E4106564A; Mon, 15 Jun 2009 12:48:29 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id 190C58FC0C; Mon, 15 Jun 2009 12:48:28 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id m38so1240113waf.27 for ; Mon, 15 Jun 2009 05:48:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:subject :message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=ionKhtvqS2JwgS60U6gv95mZk/HReEPfTgtBRoYDUGA=; b=JLOyqGslqmNGlKZYOoryfBjbA3Oq+vMNYoX8gw0G2xysY0Ej2JIuhgpo0kRhnSDxkb dKWVdQptbdVdiGojVuS1N987fhAH6AedA6A2Y/AqMhuiWHi8Vpx5lECJEcOFotfUtuBE xmuLyXbew/Ne8HwcF0yNg4jdwuFBWQZDj8YB0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=U+gv4m5m3KD+b+trXsLnlds2zwCkCbYJdG0IIJPJFRnpSchB0fk5WWHCAE4ygVblb5 kfEB7o2umYS7jmxF/PYVgHRwOSZBN0X4n0TBfT0td+fx18MKAePuv9HCAsi17ROpWw8j RDsD3dAA0+pmPkzp9rIEMH0lmDOSF0I00GDFw= Received: by 10.114.92.18 with SMTP id p18mr11762951wab.45.1245070108663; Mon, 15 Jun 2009 05:48:28 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ([114.111.62.249]) by mx.google.com with ESMTPS id n30sm6275955wag.6.2009.06.15.05.48.26 (version=SSLv3 cipher=RC4-MD5); Mon, 15 Jun 2009 05:48:27 -0700 (PDT) Received: by michelle.cdnetworks.co.kr (sSMTP sendmail emulation); Mon, 15 Jun 2009 21:51:54 +0900 From: Pyun YongHyeon Date: Mon, 15 Jun 2009 21:51:54 +0900 To: Pyun YongHyeon , current@freebsd.org Message-ID: <20090615125154.GG78415@michelle.cdnetworks.co.kr> References: <20090615121623.GA1479@roadrunner.spoerlein.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090615121623.GA1479@roadrunner.spoerlein.net> User-Agent: Mutt/1.4.2.3i Cc: Subject: Re: ale(4): Problems with tso, rxcsum and/or txcsum X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com 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:48:29 -0000 On Mon, Jun 15, 2009 at 02:16:23PM +0200, Ulrich Sp??rlein wrote: > 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 Hmm, I think this is the second report that could be related with Rx checksum offloading. If disabling Rx checksum fix the issue, I have to disable it by default until I understand what's going on. > down/up the interface for changes to tso or {tr}xcsum to have any > effect? > No, ale(4) does not require interface reinitialization. Instead of turning off all checksum offloading try disabling Rx checksum offload first. > 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? > No, I'm not aware of it but as I said it's second report so I guess it's real.