From owner-freebsd-current@FreeBSD.ORG Thu Jul 17 01:50:35 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A08A106564A for ; Thu, 17 Jul 2008 01:50:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id D46CF8FC20 for ; Thu, 17 Jul 2008 01:50:34 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so3533656pyb.10 for ; Wed, 16 Jul 2008 18:50:34 -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=MTXdBdR4wV/oxOIbHbc5CxhSquXb673LevyrDB0VOHc=; b=hOwzZdX4qEc0edo0zmhgitFGVvzifQ6CXAPAm17dnarxoUz+uxzuNDwzO4nizGtVlG rKuiSrbP24zi6dgPmC0E92YnlZ1JE6eXAAHAqMyG5E+ZgPjlcVAtV+wwrri312wmvA/u SNY1iW0e7229iKNdiJ08I7+dhN270OmLOhWxc= 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=D1VrLo7paEsFZ6TVxYAsyFHyBckzhrbz8B0v8/uTvJ8VpC+47hTlNi8fZJbh0XHl/m vOqM3yRWxAAm5TvAlENVw4mMmiqdDebCZhXla+5tn/wjbY6uqMsDHypbzLkflQRAWpII hbdwVsmcpAfuROu0FzRFl8AeSUZymn0Ljj/2Y= Received: by 10.141.152.8 with SMTP id e8mr848965rvo.19.1216259433781; Wed, 16 Jul 2008 18:50:33 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id b8sm5485899rvf.8.2008.07.16.18.50.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 16 Jul 2008 18:50: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 m6H1mMU2049167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Jul 2008 10:48: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 m6H1mJuj049166; Thu, 17 Jul 2008 10:48:19 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 17 Jul 2008 10:48:18 +0900 From: Pyun YongHyeon To: Johan Hendriks Message-ID: <20080717014818.GC48743@cdnetworks.co.kr> References: <487DA2E5.3080201@andric.com> <57200BF94E69E54880C9BB1AF714BBCB5DDFA7@w2003s01.double-l.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57200BF94E69E54880C9BB1AF714BBCB5DDFA7@w2003s01.double-l.local> User-Agent: Mutt/1.4.2.1i Cc: Dimitry Andric , freebsd-current@freebsd.org Subject: Re: Call for testers: re(4) andRTL8168C/RTL8168CP/RTL8111C/RTL8111CP 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: Thu, 17 Jul 2008 01:50:35 -0000 On Wed, Jul 16, 2008 at 09:45:33AM +0200, Johan Hendriks wrote: > > > >Aan: pyunyh@gmail.com > >CC: freebsd-current@FreeBSD.org > >Onderwerp: Re: Call for testers: re(4) >andRTL8168C/RTL8168CP/RTL8111C/RTL8111CP > > >On 2008-07-14 03:35, Pyun YongHyeon wrote: > >> Here is patch for re(4) link handling. > >> Copy if_re.c and if_rlreg.h from HEAD to RELENG_7 and apply > >> attached one. If you still see watchdog timeouts, please turn off > >> TSO and let me know how it goes. > > >I've tested this trough several reboots, and I haven't been bitten by > >any watchdogs yet. :) I'll run some stress tests today, to see if it > >handles that too. > > > >> One user reported TSO issues on 8169 family controllers but I > >> can't reproduce this on my 8169 hardware so it could be related > >> with silicon bug of sepecific revision of the hardware. > > >I'm using re's default settings, which seem to be: > > >re0: flags=8843 metric 0 mtu 1500 > >options=399bST,WOL_MCAST,WOL_MAGIC> > > >So TSO for IPv4 but not IPv6, right? I haven't yet seen any problems > >because of it. What would be a good way to "exercise" TSO? > > > I had a re(4) card that did crash 7-stable now i cvsuped to 15-07-2008 and did a rebuild > > The system is now in "production" and I see the following in /var/log/messages. > > Jul 15 18:24:40 intranet kernel: re0: watchdog timeout > Jul 15 18:24:40 intranet kernel: re0: link state changed to DOWN > Jul 15 18:24:43 intranet kernel: re0: link state changed to UP > Jul 15 19:28:03 intranet ntpd[883]: kernel time sync enabled 6001 > Jul 15 19:45:08 intranet ntpd[883]: kernel time sync enabled 2001 > Jul 15 20:04:41 intranet kernel: re0: watchdog timeout > Jul 15 20:04:41 intranet kernel: re0: link state changed to DOWN > Jul 15 20:04:43 intranet kernel: re0: link state changed to UP > Jul 15 21:14:40 intranet kernel: re0: watchdog timeout > Jul 15 21:14:40 intranet kernel: re0: link state changed to DOWN > Jul 15 21:14:43 intranet kernel: re0: link state changed to UP > Jul 15 21:19:41 intranet kernel: re0: watchdog timeout > Jul 15 21:19:41 intranet kernel: re0: link state changed to DOWN > Jul 15 21:19:43 intranet kernel: re0: link state changed to UP > Jul 15 21:24:40 intranet kernel: re0: watchdog timeout > Jul 15 21:24:40 intranet kernel: re0: link state changed to DOWN > Jul 15 21:24:43 intranet kernel: re0: link state changed to UP > Jul 15 22:14:40 intranet kernel: re0: watchdog timeout > Jul 15 22:14:40 intranet kernel: re0: link state changed to DOWN > Jul 15 22:14:43 intranet kernel: re0: link state changed to UP > Jul 16 03:20:53 intranet kernel: re0: watchdog timeout > Jul 16 03:20:53 intranet kernel: re0: link state changed to DOWN > Jul 16 03:20:56 intranet kernel: re0: link state changed to UP > Jul 16 03:24:41 intranet kernel: re0: watchdog timeout > Jul 16 03:24:41 intranet kernel: re0: link state changed to DOWN > Jul 16 03:24:43 intranet kernel: re0: link state changed to UP > Jul 16 03:25:53 intranet kernel: re0: watchdog timeout > Jul 16 03:25:53 intranet kernel: re0: link state changed to DOWN > Jul 16 03:25:56 intranet kernel: re0: link state changed to UP > Jul 16 03:44:40 intranet kernel: re0: watchdog timeout > Jul 16 03:44:40 intranet kernel: re0: link state changed to DOWN > Jul 16 03:44:43 intranet kernel: re0: link state changed to UP > Jul 16 04:23:32 intranet ntpd[883]: kernel time sync enabled 6001 > Jul 16 04:40:38 intranet ntpd[883]: kernel time sync enabled 2001 > Jul 16 05:19:41 intranet kernel: re0: watchdog timeout > Jul 16 05:19:41 intranet kernel: re0: link state changed to DOWN > Jul 16 05:19:44 intranet kernel: re0: link state changed to UP > Jul 16 06:19:40 intranet kernel: re0: watchdog timeout > Jul 16 06:19:40 intranet kernel: re0: link state changed to DOWN > Jul 16 06:19:43 intranet kernel: re0: link state changed to UP > Jul 16 08:14:40 intranet kernel: re0: watchdog timeout > Jul 16 08:14:40 intranet kernel: re0: link state changed to DOWN > Jul 16 08:14:43 intranet kernel: re0: link state changed to UP > Jul 16 08:44:41 intranet kernel: re0: watchdog timeout > Jul 16 08:44:41 intranet kernel: re0: link state changed to DOWN > Jul 16 08:44:44 intranet kernel: re0: link state changed to UP > > It is a small intranet webserver and does cacti and nagios things and mirror cvs for the other machines. > > #pciconf -lv > re0@pci0:2:0:0: class=0x020000 card=0x2a73103c chip=0x816810ec rev=0x02 hdr=0x00 > vendor = 'Realtek Semiconductor' > device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' > class = network > subclass = Ethernet > > # dmesg > re0: port 0xe800-0xe8ff mem 0xfebff000-0xfebfffff,0xfdff0000-0xfdffffff irq 18 at device 0.0 on pci2 > re0: Chip rev. 0x3c000000 It's RealTek 8139C controller. > re0: MAC rev. 0x00200000 > miibus0: on re0 > rgephy0: PHY 1 on miibus0 > rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto > re0: Ethernet address: 00:1e:0b:a7:cc:38 > re0: [FILTER] > > It also not always load ok on a reboot ! > Sometimes it complains about something with PHY I know this issue on second generation of PCIe controllers but have no clue yet. I vaguely guess it's related with power-saving or initial hardware reset related stuff. > A reboot than fix this and loads the re0 driver. > It would be even better if you can try patch I posted earlier in this thread. -- Regards, Pyun YongHyeon