From owner-freebsd-stable@FreeBSD.ORG Wed Sep 23 00:04:53 2009 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 3D0C9106568D for ; Wed, 23 Sep 2009 00:04:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.25]) by mx1.freebsd.org (Postfix) with ESMTP id E214E8FC18 for ; Wed, 23 Sep 2009 00:04:52 +0000 (UTC) Received: by qw-out-2122.google.com with SMTP id 3so91270qwe.7 for ; Tue, 22 Sep 2009 17:04:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=4y79BxcXQD6CvKiBj4zR/giQhQyLNJmy3bmFv/sZfOA=; b=Xl/QzOM899UDlH8mw9QVLmGqbOqJ06Zzejq2ZyxJFZZxVu2jWKy25Wn5L7I/y5Qyc2 Q6vOm3Pel6uR2ClixzK5tz3ioWnp2q0T6oXU1hBJZ2TofIYs70rBihQF2/fruVIG0zk5 NVGWz3M8gFDBNGiXi0J6mvixS/MzTXLpbLaUg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=EdRi9ueyUObM1/QL/4sNL10WzqupWPesymJ+GEfLO7WNOfMte7+T4ZV1wODFlAZHpx wyhcA70rCOi3RZ01eHUHf2/iukGxCjfSUybCfng+taNwf4G/FIHYoRX8w+r+I57benwj 4y1XjY5q+p1VovJMR84dWbPaDqYfKfVCK2cuY= Received: by 10.224.109.131 with SMTP id j3mr1374973qap.97.1253664292381; Tue, 22 Sep 2009 17:04:52 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 7sm502158qwf.57.2009.09.22.17.04.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 22 Sep 2009 17:04:51 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Tue, 22 Sep 2009 17:04:05 -0700 From: Pyun YongHyeon Date: Tue, 22 Sep 2009 17:04:05 -0700 To: Cassidy Larson Message-ID: <20090923000405.GC1520@michelle.cdnetworks.com> References: <20090922200053.GA1520@michelle.cdnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org Subject: Re: Random Network Drops on Realtek Interfaces (re) 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: Wed, 23 Sep 2009 00:04:53 -0000 On Tue, Sep 22, 2009 at 05:33:18PM -0600, Cassidy Larson wrote: > Suggestions were: > #1) try "arp -da". This does not fix the issue. I don't see any ARP > for any other IPs other than the local. > #2) speed/duplex settings. I tried forcing 100FD on the box and that > didnt resolve the issue. When I did force 100 full-duplex on the > switch, the box appeared as if it was reporting 100HD. Odd. > Don't do that. It would be normal behavior if link partner's media configuration is autodetect as link partner have to rely on parallel detection. If you have to use forced link, both your NIC and link partner should use the same forced media configuration which is highly discouraged configuration on gigabit links. > > By chace can you find any messages in dmesg reported by re(4)? > > dmesg output related to re(4) would be more helpful as RealTek > > controllers used to show same device ids. > > Here is my dmesg output for the re(4) devices: > re0: PCIe Gigabit Ethernet> port 0xd800-0xd8ff mem > 0xfeaff000-0xfeafffff,0xfdef0000-0xfdefffff irq 16 at device 0.0 on > pci2 > re0: Using 1 MSI messages > re0: Chip rev. 0x3c000000 > re0: MAC rev. 0x00400000 > miibus0: on re0 > re0: Ethernet address: 00:30:48:b0:ec:84 > re0: [FILTER] > re1: PCIe Gigabit Ethernet> port 0xe800-0xe8ff mem > 0xfebff000-0xfebfffff,0xfdff0000-0xfdffffff irq 17 at device 0.0 on > pci3 > re1: Using 1 MSI messages > re1: Chip rev. 0x3c000000 > re1: MAC rev. 0x00400000 > miibus1: on re1 > re1: Ethernet address: 00:30:48:b0:ec:85 > re1: [FILTER] > > Currently, I am not using re1. Only re0 for access. > It looks plain RTL8168C PCIe controller. Is there any odd messages reported by re(4) such as watchdog timeouts? If you disable MSI feature does it make any difference?(Add hw.re.msi_disable="1" to /boot/loader.conf to disable MSI.) > Another side note, I have updated the BIOS to 1.0a from Supermicro as > of yesterday, but that has not fixed this issue. > > Thanks, > > -c