Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 04 Apr 2019 01:52:28 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 236999] vmx driver stops sending network packets and resets connections (TCP) but allows ICMP
Message-ID:  <bug-236999-227@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236999

            Bug ID: 236999
           Summary: vmx driver stops sending network packets and resets
                    connections (TCP) but allows ICMP
           Product: Base System
           Version: CURRENT
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs@FreeBSD.org
          Reporter: mshirk@daemon-security.com

Tested on 13-CURRENT, with a FreeBSD VM running under ESXi (not sure the
versions, I actually do not have console access at this point).

I did an upgrade from 12-ALPHA4 something to 13-CURRENT and after this was
completed, users were unable to download files over 1MB from this server. I
verified that I could SSH into this system and navigate the simple website =
that
was serving files, but whenever I tried to download a 40MB file, the transf=
er
would stop, the connection would reset.

I verified the same thing was happening with SFTP, navigate to the file,
everything worked, but start the transfer, connection reset.

I enabled ICMP to be able to ping this system continuously, and noticed not=
hing
was dropping out, and verified nothing else was going on (that I am aware o=
f)
with any type of security device, packet shaping, etc.

But with ICMP working fine while TCP connections were reset, I went to look=
 at
NIC offloading features, and all of them were turned on.

Running the following to disable all of it with the vmx driver, and all of =
the
problems went away, file transfers started to work:

ifconfig vmx0 -rxcsum -txcsum -tso4 -tso6 -lro -rxcsum6 -txcsum6 -vlanhwcsum
-vlanhwtso

I tried flipping each one off and on trying to see it was one particular
option, and it appears TSO4/TSO6 is where the problems resides



vmx0@pci0:3:0:0:        class=3D0x020000 card=3D0x07b015ad chip=3D0x07b015a=
d rev=3D0x01
hdr=3D0x00
    vendor     =3D 'VMware'
    device     =3D 'VMXNET3 Ethernet Controller'
    class      =3D network
    subclass   =3D ethernet

[1] Hypervisor: Origin =3D "VMwareVMware"
[1] vmx0: <VMware VMXNET3 Ethernet Adapter> port 0x4000-0x400f mem
0xfd5fc000-0xfd5fcfff,0xfd5fd000-0xfd5fdfff,0xfd5fe000-0xfd5fffff irq 18 at
device 0.0 on pci3

[1] vmx0: <VMware VMXNET3 Ethernet Adapter> port 0x4000-0x400f mem
0xfd5fc000-0xfd5fcfff,0xfd5fd000-0xfd5fdfff,0xfd5fe000-0xfd5fffff irq 18 at
device 0.0 on pci3
[1] vmx0: Using 512 tx descriptors and 256 rx descriptors
[1] vmx0: Using 2 rx queues 2 tx queues
[1] vmx0: failed to allocate 3 MSI-X vectors, err: 6 - using MSI
[1] vmx0: Using an MSI interrupt
[1] vmx0: Ethernet address: 00:50:56:8f:25:15
[1] vmx0: netmap queues/slots: TX 1/512, RX 1/512

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236999-227>