From owner-freebsd-stable@FreeBSD.ORG Fri Aug 1 08:09:34 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 54DF21065682 for ; Fri, 1 Aug 2008 08:09:34 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by mx1.freebsd.org (Postfix) with ESMTP id 1E6298FC1B for ; Fri, 1 Aug 2008 08:09:34 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so1278449rvf.43 for ; Fri, 01 Aug 2008 01:09:33 -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=yF7FRWbu3C3B6v7P7iYUG20kvy6uHyNjaA8Ag/FwgLs=; b=c1r09h5B2yz+Mpi2B587WO1kI+5eu0TRoaD0UR+qMgIYeR2gwT+0TydUgEO72vbwu2 hXhIcNjoSGqBG/bTaRTnrCnhT6C/nJItHyH2evBs5Yx8eCcTW1ZrhwRmVl03EzHvR0v7 plRRE4nuVPW+lu4XgQH36F8K47ERpkmZV57wM= 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=GmBJz9fVrIwolhjF8tdQq5JdVfwOUvmq0aoN11qQdULi2up6Ri7DXcbvmvBxGq4W1Q 8kNtQOrpdKlKyOL6JkdAM+BpWYNs5Qmu4tkOP7mdevr6B94vBaqEq34716Ria7LulMnu 9ERPIHJ50dWkrH5AI616gUX2Wbe+1hNWLe1O0= Received: by 10.141.49.6 with SMTP id b6mr5798086rvk.89.1217578173785; Fri, 01 Aug 2008 01:09:33 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id k2sm1249193rvb.4.2008.08.01.01.09.31 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 01 Aug 2008 01:09:32 -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 m7187MOw010579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 1 Aug 2008 17:07:22 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m7187LtN010578; Fri, 1 Aug 2008 17:07:21 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Fri, 1 Aug 2008 17:07:21 +0900 From: Pyun YongHyeon To: Eugene Butusov Message-ID: <20080801080721.GB9206@cdnetworks.co.kr> References: <489262E5.3010304@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <489262E5.3010304@gmail.com> 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: Fri, 01 Aug 2008 08:09:34 -0000 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. -- Regards, Pyun YongHyeon