From owner-freebsd-stable@FreeBSD.ORG Fri Jul 2 17:44:33 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 EF4CA106566C for ; Fri, 2 Jul 2010 17:44:33 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id A6F808FC15 for ; Fri, 2 Jul 2010 17:44:33 +0000 (UTC) Received: by gwb1 with SMTP id 1so1263940gwb.13 for ; Fri, 02 Jul 2010 10:44:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=PXxDb4N4kce7X0tfH0fatXzLY2GU/Lg5LpVv11RqE2c=; b=vi+4nuPSBNgBIQdOehb7lTN8e24o9JARFKqReQhGXkrS1iehNF0yVHjqyYPKZNFanF MEanO23vvRpzRNZYGVoqjr7D9/TJJVm5O1YsXSK5UJt83YEkE3cKRKY7e2M6H9lYA7C+ +XytQKUp/WyL3m8f9D9dEyxsPGGvrC3XxyDk4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=qfoQjG7MEtIA/od4nI9W1tExBdbTJMFtqnYcZnWGhh4WUyWbMTcH1kG2VNy/0GOGSL A358SNlWR202ot7Xcu6Q+pVm464SXmrpiWUKer18Bwtd8zAvIehUa3mD0Kw+3UKflTb2 O+QkyQB77X8Yf04EJ/ER+AtaEb1jdyxi6D3MY= MIME-Version: 1.0 Received: by 10.229.245.68 with SMTP id lt4mr768966qcb.71.1278092666557; Fri, 02 Jul 2010 10:44:26 -0700 (PDT) Received: by 10.229.250.197 with HTTP; Fri, 2 Jul 2010 10:44:26 -0700 (PDT) In-Reply-To: <201007021739.o62HdMOU092319@lava.sentex.ca> References: <201006102031.o5AKVCH2016467@lava.sentex.ca> <201007021739.o62HdMOU092319@lava.sentex.ca> Date: Fri, 2 Jul 2010 10:44:26 -0700 Message-ID: From: Jack Vogel To: Mike Tancsa Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_7 em problems (and RELENG_8) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list 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 17:44:34 -0000 I got the email, there are server outages around here today and people leaving for a long weekend, so not much getting done. I'll take some time and look into this after the weekend, ok? Jack On Fri, Jul 2, 2010 at 10:39 AM, 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 ? > > ---Mike > > > At 04:31 PM 6/10/2010, Mike Tancsa wrote: > >> Hi Jack, >> I am seeing some issues on RELENG_7 with a specific em nic >> >> em2@pci0:13:0:0: class=0x020000 card=0x108c15d9 chip=0x108c8086 >> rev=0x03 hdr=0x00 >> vendor = 'Intel Corporation' >> device = 'Intel Corporation 82573E Gigabit Ethernet Controller >> (Copper) (82573E)' >> 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) >> >> If I disable tso, I am not able to make a tcp connection into the host >> >> eg >> 0[psbgate1]# ifconfig em2 >> em2: flags=8843 metric 0 mtu 1500 >> >> >> options=219b >> ether 00:30:48:9f:eb:80 >> inet 192.168.128.200 netmask 0xfffffff0 broadcast 192.168.128.207 >> media: Ethernet autoselect (100baseTX ) >> status: active >> 0[psbgate1]# ifconfig em2 -tso >> 0[psbgate1]# >> >> >> Looking at the pcap, the checksum is bad on the syn-ack. If I re-enable >> tso, it seems to be ok >> >> 16:18:01.113297 IP (tos 0x10, ttl 64, id 6339, offset 0, flags [DF], proto >> TCP (6), length 60) 192.168.128.196.54172 > 192.168.128.200.22: S, cksum >> 0x4e79 (correct), 3313156149:3313156149(0) win 65535 > 3,sackOK,timestamp 3376174416 0> >> 16:18:01.123676 IP (tos 0x0, ttl 64, id 3311, offset 0, flags [DF], proto >> TCP (6), length 60) 192.168.128.200.22 > 192.168.128.196.54172: S, cksum >> 0x81c9 (incorrect (-> 0x51f2), 1373042663:1373042663(0) ack 3313156150 win >> 65535 >> >> >> em2: port 0x5000-0x501f mem >> 0xe8200000-0xe821ffff irq 16 at device 0.0 on pci13 >> em2: Using MSI interrupt >> em2: [FILTER] >> em2: Ethernet address: 00:30:48:9f:eb:80 >> pcib5: irq 16 at device 28.5 on pci0 >> 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 >> >> >> Also there is still the issue with >> >> >> http://lists.freebsd.org/pipermail/freebsd-stable/2009-November/052842.html >> >> in RELENG_7 ? >> >> ---Mike >> >> >> -------------------------------------------------------------------- >> Mike Tancsa, tel +1 519 651 3400 >> Sentex Communications, mike@sentex.net >> Providing Internet since 1994 www.sentex.net >> Cambridge, Ontario Canada www.sentex.net/mike >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> > > -------------------------------------------------------------------- > Mike Tancsa, tel +1 519 651 3400 > Sentex Communications, mike@sentex.net > Providing Internet since 1994 www.sentex.net > Cambridge, Ontario Canada www.sentex.net/mike > >