From owner-freebsd-net@FreeBSD.ORG Mon Apr 7 06:09:34 2014 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7DDB5341; Mon, 7 Apr 2014 06:09:34 +0000 (UTC) Received: from tampoco.espindola.nl (tampoco.espindola.nl [149.210.133.191]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3DE61D82; Mon, 7 Apr 2014 06:09:33 +0000 (UTC) Received: from [127.0.0.1] (corfu.internal.deze.org [192.168.1.2]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: frank) by tampoco.espindola.nl (Postfix) with ESMTPSA id C22A2371BC6; Mon, 7 Apr 2014 08:09:01 +0200 (CEST) Message-ID: <53424100.7030103@deze.org> Date: Mon, 07 Apr 2014 08:09:04 +0200 From: Frank Volf User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: pyunyh@gmail.com, Rick Macklem Subject: Re: re0: watchdog timeout References: <53418053.5020105@deze.org> <280407068.6916295.1396827428537.JavaMail.root@uoguelph.ca> <20140407012241.GA3543@michelle.cdnetworks.com> In-Reply-To: <20140407012241.GA3543@michelle.cdnetworks.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, marius@freebsd.org, yongari@freebsd.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Apr 2014 06:09:34 -0000 Yonghyeon PYUN schreef op 7-4-2014 3:22: > On Sun, Apr 06, 2014 at 07:37:08PM -0400, Rick Macklem wrote: >> Frank Volf wrote: >>> Hello, >>> >>> I'm experiencing watchdog timeouts with my Realtek interface card. >>> >>> I'm using a fairly new system (Shuttle DS47), running FreeBSD >>> 10-STABLE. >>> For this shuttle a patch has been recently committed to SVN to make >>> this >>> card work at all (revision *262391* >>> ). >>> >>> The timeout is only experienced under heavy network load (the system >>> is >>> running a bacula backup server that backups to NFS connected >>> storage), >>> and typically large full backups trigger this. Normal traffic works >>> fine >>> (this system is e.g. also my firewall to the Internet). >>> >> Since you mention NFS, you could try disabling TSO on the interface >> and see if that helps. (I'm beginning to feel like a parrot saying this, >> but...) If you care about why it might help, read this email thread: >> http://docs.FreeBSD.org/cgi/mid.cgi?1850411724.1687820.1395621539316.JavaMail.root >> >> If it happens to help, please email again, since there are probably >> better ways to fix the problem than disabling TSO. >> > re(4) controllers support TSO but it was disabled long time > ago(r217832). > It's still allowed to enable TSO but users have to explicitly > enable it with ifconfig. If Frank didn't explicitly enable TSO on > the box, TSO may have nothing to do with watchdog timeout, I guess. I haven't explicitly enabled TSO, the only option that has been explicitly set is -vlanhwtag, here is the interface config: re0: flags=8843 metric 0 mtu 1500 options=8208b ether 80:ee:73:77:e9:ab nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active Regards, Frank