RELENG_7 em problems (and RELENG_8)
Pyun YongHyeon
pyunyh at gmail.com
Fri Jul 2 19:37:23 UTC 2010
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 at 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: <ACPI PCI bus> on pcib5
> em3: <Intel(R) PRO/1000 Network Connection 7.0.5> 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<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
> metric 0 mtu 1500
> options=2098<VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC>
> ether 00:30:48:9f:eb:81
> inet 10.255.255.254 netmask 0xfffffffc broadcast 10.255.255.255
> media: Ethernet autoselect (1000baseT <full-duplex>)
> 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.
More information about the freebsd-stable
mailing list