From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 19:37:22 2010 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 CA175106566B for ; Fri, 2 Jul 2010 19:37:22 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 982378FC0A for ; Fri, 2 Jul 2010 19:37:22 +0000 (UTC) Received: by pwj9 with SMTP id 9so841051pwj.13 for ; Fri, 02 Jul 2010 12:37:22 -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=HwRTmrRGirtoS2Vq5Vl0Lhg+s2QGq3V4sVD4cgDQvek=; b=kwhXXEp3mi0WTXJrJL1wVJ9VyOjfB0m3DxqhrmU8MDuQbW9GGGQ/6QcqHgojTahgg2 ctxyIHPqC1SEcA4Ebz2NLnlr990+gQWQ4aNBLiN7fJFI1wRYLvEFqpHsck2QKiMoBVpP Dn6niC+7N3LqLWVib1R0k1rn8VrPWU+k5g8zY= 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=sKatFeDFv7QJMT4azgGnzanFYCdjGZl7IJxilxmMk4UQ73Fjbzi7ztIa/lNsH0gZhB 9CjzGTsbjkWoPK2H/sVh/iTfcHEy/2b266VDtKzAwEBrY2Zm6/xSrZJbjIORBT1oslwu sdBKiwMSRk99hUWS85Qwil02KMqwkvhl9xA28= Received: by 10.142.211.5 with SMTP id j5mr1747056wfg.156.1278099442044; Fri, 02 Jul 2010 12:37:22 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id c15sm1101317rvi.11.2010.07.02.12.37.20 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 02 Jul 2010 12:37:21 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Fri, 2 Jul 2010 12:36:54 -0700 From: Pyun YongHyeon Date: Fri, 2 Jul 2010 12:36:54 -0700 To: Mike Tancsa Message-ID: <20100702193654.GD10862@michelle.cdnetworks.com> References: <201006102031.o5AKVCH2016467@lava.sentex.ca> <201007021739.o62HdMOU092319@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201007021739.o62HdMOU092319@lava.sentex.ca> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, jfvogel@gmail.com Subject: Re: RELENG_7 em problems (and RELENG_8) 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, 02 Jul 2010 19:37:23 -0000 On Fri, Jul 02, 2010 at 01:39:22PM -0400, Mike Tancsa wrote: > Hi Jack, > Just a followup to the email below. I now saw what appears > to be the same problem on RELENG_8, but on a different nic and with > VLANs. So not sure if this is a general em problem, a problem > specific to some em NICs, or a TSO problem in general. The issue > seemed to be triggered when I added a new vlan based on > > em3@pci0:14:0:0: class=0x020000 card=0x109a15d9 > chip=0x109a8086 rev=0x00 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel PRO/1000 PL Network Adaptor (82573L)' > class = network > subclass = ethernet > cap 01[c8] = powerspec 2 supports D0 D3 current D0 > cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message > cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) > > pci14: on pcib5 > em3: port 0x6000-0x601f > mem 0xe8300000-0xe831ffff irq 17 at device 0.0 on pci14 > em3: Using MSI interrupt > em3: [FILTER] > em3: Ethernet address: 00:30:48:9f:eb:81 > > em3: flags=8943 > metric 0 mtu 1500 > options=2098 > ether 00:30:48:9f:eb:81 > inet 10.255.255.254 netmask 0xfffffffc broadcast 10.255.255.255 > media: Ethernet autoselect (1000baseT ) > status: active > > I had to disable tso, rxcsum and txsum in order to see the devices on > the other side of the two vlans trunked off em3. Unfortunately, the > other sides were switches 100km and 500km away so I didnt have any > tcpdump capabilities to diagnose the issue. I had already created > one vlan off this NIC and all was fine. A few weeks later, I added a > new one and I could no longer telnet into the remote switches from > the local machine.... But, I could telnet into the switches from > machines not on the problem box. Hence, it would appear to be a > general TSO issue no ? I disabled tso on the nic (I didnt disable > net.inet.tcp.tso as I forgot about that).. Still nothing. I could > always ping the remote devices, but no tcp services. I then > remembered this issue from before, so I tried disabling tso on the > NIC. Still nothing. Then I disabled rxcsum and txcsum and I could > then telnet into the remote devices. > > This newly observed issue was from a buildworld on Mon Jun 14 > 11:29:12 EDT 2010. > > I will try and recreate the issue locally again to see if I can > trigger the problem on demand. Any thoughts on what it might be ? > Perhaps an issue specific to certain em nics ? > http://www.freebsd.org/cgi/query-pr.cgi?pr=141843 I'm not sure whether you're seeing the same issue though. I didn't have chance to try latest em(4) on stable/7.