From owner-freebsd-stable@FreeBSD.ORG Mon Aug 4 02:38:15 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89DB91065673 for ; Mon, 4 Aug 2008 02:38:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by mx1.freebsd.org (Postfix) with ESMTP id 50CA78FC18 for ; Mon, 4 Aug 2008 02:38:15 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2747992rvf.43 for ; Sun, 03 Aug 2008 19:38:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=GDLyLO2D5mVT5UjzHenOqTf+AGkh7Kfa9x4zcJ5hkAw=; b=RDp/p3NkJ+yPg/cM4wsac92HF8sJlaycNb+23B3MJYqdJNnO6yEW6aO4/RPjjFDN4Z V+8+kWmmNQoXcGd4ua4lkWFQc2ldGNYn8s2PTFU4sdXqXre99fdGudeSjx+d7OSuSVxL rmSKhawy9i8Zo/vwBXfpr0qAqTWeANwbactOw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=r1Hc6BREGypQM45AXU+nMSUYFofYbWoa/+zd4Z9SG0TSyK66EVCoDnYBeWjJYnYOFo VkxZBgnUv0XSQrWBlBSrJzrpc9PQgdbqIfNivgVmom0J9ZT+6Ilq5pJ7O0ljsuy5QhEK 2T3qlaF1O+418Q5fRz4JXzwpuyN06PcWGxa90= Received: by 10.141.153.16 with SMTP id f16mr5209229rvo.17.1217817495054; Sun, 03 Aug 2008 19:38:15 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id f21sm6310611rvb.0.2008.08.03.19.38.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 03 Aug 2008 19:38:13 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id m742a126022027 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 4 Aug 2008 11:36:01 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m742a02f022026; Mon, 4 Aug 2008 11:36:00 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 4 Aug 2008 11:36:00 +0900 From: Pyun YongHyeon To: Eugene Butusov Message-ID: <20080804023600.GC21401@cdnetworks.co.kr> References: <489262E5.3010304@gmail.com> <20080801080721.GB9206@cdnetworks.co.kr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080801080721.GB9206@cdnetworks.co.kr> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD-STABLE-LIST Subject: Re: Realtek RTL8110 (SB) watchdog timeout. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Aug 2008 02:38:15 -0000 On Fri, Aug 01, 2008 at 05:07:21PM +0900, To Eugene Butusov wrote: > On Fri, Aug 01, 2008 at 03:12:05AM +0200, Eugene Butusov wrote: > > Hi, > > > > After updating from 7.0-RELEASE to STABLE (around 15/08) my NIC > > refuses to handle large file transfers. > > > > pciconf -lv > > > > re0@pci0:4:0:0: class=0x020000 card=0x001a6409 chip=0x816910ec > > rev=0x10 hdr=0x00 > > vendor = 'Realtek Semiconductor' > > device = 'RTL8110SB Single-Chip Gigabit LOM Ethernet Controller' > > class = network > > subclass = ethernet > > > > Log messages: > > > > re: watchdog timeout > > re: link changed to DOWN > > re: link changed to UP > > > > When someone tried to copy large (i.e. 700MB) file from samba share > > (local gigabit network) or ftp (same LAN), > > the NIC was reseted. For a while host was not accesible from the > > network, and then it came back with log messages shown above. > > I've tried to tune samba socket options (SO_RCVBUF=16384 > > SO_SNDBUF=16384), and this fixed the problem for samba users. One > > interesting thing: copying file to windows XP machine worked fine, > > while Vista (SP1 x64) caused the problem. > > > > What solved the problem definitely was disabling TSO for re0 (ifconfig > > One of developer also reported TSO issue. But his hardware was a > plain 8169S. Given that you're seeing TSO issues on 8110SB I'm > afraid all RealTek 8169/8110 series may suffer from the TSO issues. > Under certain circumtances, the controller generates corrupted > frames for TSO case and this seem to be resulted in watchdog > timeouts. > I'm not sure recent PCIe based 8168/8110 family also suffers from > the issue as no one have complained the issue. > > > re0 -tso). I haven't notice any performance drop and it works fine, > > but I'm just curious what happened to the 'good' driver from 7.0-RELEASE. > > > > I don't think re(4) in 7.0-RELEASE is bug free. If you check commit > logs in RELENG_7 you may see what I mean. At the time of re(4) > overhauling, I added TSO to re(4). Generally TSO shall not increase > Tx performance but TSO significantly saves CPU cycles for TCP bulk > transfers. The saved CPU power could be used for other tasks. > > Anyway, thanks for reporting, I'll disable TSO in next monday. > FYI: I've committed TSO patch to HEAD with svn revision r181271. -- Regards, Pyun YongHyeon