From owner-freebsd-stable@FreeBSD.ORG Mon Jul 30 05:29:01 2007 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 3E59616A418 for ; Mon, 30 Jul 2007 05:29:01 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id 157F113C45A for ; Mon, 30 Jul 2007 05:29:01 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1550883waf for ; Sun, 29 Jul 2007 22:29:00 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=p6Qfm42EzOqpKrXw/8v2P4rUuZk5qI4djNgjaIJ9Vmbszk7eNhOp3B8CkbwinvygDEE9GEhZa3Yl07pQ2Qg/vbAwFnxo7aNv9K6DWD9SA3CdsCEzwcLJqDbbZWS5RcLz0xR/ptEOtSn+CjDaF4rGPxOGMxKr3aC2e1o1GENzUP0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=ePyNmYIreOjjV4Omo+UnNVqvcS4+/Ljb0shCQ5DUgTqVbzm17jRcCk703DLgod2nL4OrvYwjAs0HiwPzInL83bHUa/qpDOHNE6aJbu65trRRE7AUsnSNjrJCTgESJ+LHIgk2m67cH1CcyZJXuEe18U+cCIcIJ7dWVzzYCpps56U= Received: by 10.114.76.1 with SMTP id y1mr5188186waa.1185771728015; Sun, 29 Jul 2007 22:02:08 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id j7sm3492069wah.2007.07.29.22.02.05 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 29 Jul 2007 22:02:07 -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 l6U520WB089456 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 30 Jul 2007 14:02:00 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id l6U51xvZ089455; Mon, 30 Jul 2007 14:01:59 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 30 Jul 2007 14:01:59 +0900 From: Pyun YongHyeon To: Kent Stewart Message-ID: <20070730050159.GA88265@cdnetworks.co.kr> References: <200707292113.01023.lofi@freebsd.org> <200707291327.36963.kstewart@owt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200707291327.36963.kstewart@owt.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Michael Nottebrock Subject: Re: Various problems with re(4) on a PCIe 8168/8111B onboard NIC 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, 30 Jul 2007 05:29:01 -0000 On Sun, Jul 29, 2007 at 01:27:36PM -0700, Kent Stewart wrote: > On Sunday 29 July 2007, Michael Nottebrock wrote: > > After recently updating the windows drivers (I dual-boot Windows XP > > on the machine the NIC is in), I hit this problem: > > http://gentoo-wiki.com/HARDWARE_RTL8168#Troubleshooting which affects > > re(4) like it does the Linux drivers described in the above link. > > > > I already wrote the Realtek technical support about it since their > > "own" FreeBSD driver (a hacked rl(4) that does not support any of the > > chip's advanced features) does not manage to power up the PHY on its > > own either - neither does the motherboard's BIOS when trying to > > netboot. > > > > The other problem is that I have at least two applications > > misbehaving when rxcsum/txcsum is enabled: > > > > - The Linux Second Life client (yes, yes, I know, but it is nice for > > showing off GLX and it is really really good at generating network > > traffic) will cease to receive data after about a minute or so - > > turning off rcxsum/txcsum will mend it on the spot. > > > > - A Fedora Core 4 running in Qemu, networked with bridge(4) and > > tap(4), cannot receive an ip address via DHCP. Interestingly, this > > even occurs if rxcsum/txcsum was already turned off before launching > > Qemu - to make it work, I have to cycle rxcsum/txcsum once. Might be > > related to promiscuous mode. > > > > I realise that both of these make awful test cases, but so far they > > are the only applications I found to expose those problems. > > > > This is on FreeBSD kiste 6.2-STABLE FreeBSD 6.2-STABLE #4: Sat Jul 28 > > 14:11:23 CEST 2007 root@:/usr/obj/usr/src/sys/KISTE-SMP i386. > > The kernel sources are up to date as of 2007-07-27. > > > > The NIC is re0: port > > 0xd800-0xd8ff mem 0xfbfff000-0xfbffffff irq 36 at device 0.0 on pci3 > > / re0@pci3:0:0: class=0x020000 card=0x81681849 chip=0x816810ec > > rev=0x01 hdr=0x00. > > Have you looked at /var/log/messages? I would be surprised if you have > not had a number of > > Jul 27 00:55:32 ruby kernel: re0: watchdog timeout > Jul 27 00:55:32 ruby kernel: re0: link state changed to DOWN > Jul 27 00:55:35 ruby kernel: re0: link state changed to UP > > People have complained a long time ago and basically given up on getting > it fixed. > You should not see the watdog errors on re(4). If you still see the watchdog timeout errors, please let me know. -- Regards, Pyun YongHyeon