From nobody@FreeBSD.org  Fri Oct  6 12:36:33 2006
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5C43B16A40F
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  6 Oct 2006 12:36:33 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9B2A443D77
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  6 Oct 2006 12:36:27 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k96CaQRj053721
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 6 Oct 2006 12:36:26 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id k96CaQOY053720;
	Fri, 6 Oct 2006 12:36:26 GMT
	(envelope-from nobody)
Message-Id: <200610061236.k96CaQOY053720@www.freebsd.org>
Date: Fri, 6 Oct 2006 12:36:26 GMT
From: Jonas Nagel <fireball@zerouptime.ch>
To: freebsd-gnats-submit@FreeBSD.org
Subject: VMware ESX 3.0: lnc0: Missed packet -- no receive buffer
X-Send-Pr-Version: www-2.3

>Number:         104056
>Category:       kern
>Synopsis:       VMware ESX 3.0: lnc0: Missed packet -- no receive buffer
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    remko
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 06 12:40:21 GMT 2006
>Closed-Date:    Fri Jun 15 10:08:07 GMT 2007
>Last-Modified:  Fri Jun 15 10:08:07 GMT 2007
>Originator:     Jonas Nagel
>Release:        FreeBSD 6.2-BETA2  Mon Oct  2 03:22:01 UTC 2006
>Organization:
-
>Environment:
FreeBSD dns1.hirt.ch 6.2-BETA2 FreeBSD 6.2-BETA2 #0: Mon Oct  2 03:22:01 UTC 2006     root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
FreeBSD 6.2-BETA2 running on VMware ESX Server 3.0 uses driver 'lnc' for the emulated AMD PCNet NIC.

Error messages (repeating):

lnc0: Missed packet -- no receive buffer
lnc0: Missed packet -- no receive buffer
lnc0: Missed packet -- no receive buffer

Also, while pinging the host from outside there is an average packet loss of 1% of the packets, while pinging out from the virtual FreeBSD host yields no packet losses.

Apparently there seems to be a problem with the driver or the virtual hardware; now I am not sure where to look - on the VMware side or on the FreeBSD side.

Since it is a compatibility NIC, which would be improved by the VMware Tools, its probable but not obvious, that the problem could be caused by the fact that there is not the proper driver from VMware installed (no VMware Tools available for FreeBSD).

I just thought I'd post a PR, to see if somebody had an idea how to further troubleshoot the issue.

dmesg as follows:

Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-BETA2 #0: Mon Oct  2 03:22:01 UTC 2006
    root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
ACPI APIC Table: <PTLTD          APIC  >
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 3.40GHz (3397.96-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf48  Stepping = 8
  Features=0xfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS>
  Features2=0x11<SSE3,DS_CPL>
  AMD Features=0x100000<NX>
real memory  = 536870912 (512 MB)
avail memory = 511696896 (487 MB)
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <PTLTD   RSDT> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
isab0: <PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 UDMA33 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1050-0x105f at device 7.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pci0: <bridge> at device 7.3 (no driver attached)
pci0: <display, VGA> at device 15.0 (no driver attached)
mpt0: <LSILogic 1030 Ultra4 Adapter> port 0x1080-0x10ff mem 0xf4800000-0xf4800fff irq 17 at device 16.0 on pci0
mpt0: [GIANT-LOCKED]
mpt0: MPI Version=1.2.0.0
lnc0: <PCNet/PCI Ethernet adapter> port 0x1400-0x147f irq 18 at device 17.0 on pci0
lnc0: Attaching PCNet/PCI Ethernet adapter
lnc0: [GIANT-LOCKED]
lnc0: Ethernet address: 00:50:56:9b:42:71
lnc0: if_start running deferred for Giant
lnc0: PCnet-PCI
acpi_acad0: <AC Adapter> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse, device ID 3
ppc0: <Standard parallel printer port> port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xca000-0xcafff,0xdc000-0xdffff,0xe0000-0xe3fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 3397964408 Hz quality 800
Timecounters tick every 1.000 msec
md0: Preloaded image </boot/mfsroot> 4423680 bytes at 0xc0af0e44
acd0: CDROM <VMware Virtual IDE CDROM Drive/00000001> at ata0-master UDMA33
Waiting 5 seconds for SCSI devices to settle
da0 at mpt0 bus 0 target 0 lun 0
da0: <VMware Virtual disk 1.0> Fixed Direct Access SCSI-2 device 
da0: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing Enabled
da0: 15360MB (31457280 512 byte sectors: 255H 63S/T 1958C)
Trying to mount root from ufs:/dev/md0
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...3 1 0 0 0 done
All buffers synced.
Uptime: 16m32s
Rebooting...
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-BETA2 #0: Mon Oct  2 03:22:01 UTC 2006
    root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
ACPI APIC Table: <PTLTD          APIC  >
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 3.40GHz (3397.98-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf48  Stepping = 8
  Features=0xfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS>
  Features2=0x11<SSE3,DS_CPL>
  AMD Features=0x100000<NX>
real memory  = 536870912 (512 MB)
avail memory = 515883008 (491 MB)
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 <Version 1.1> irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: <PTLTD   RSDT> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
isab0: <PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 UDMA33 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1050-0x105f at device 7.1 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
pci0: <bridge> at device 7.3 (no driver attached)
pci0: <display, VGA> at device 15.0 (no driver attached)
mpt0: <LSILogic 1030 Ultra4 Adapter> port 0x1080-0x10ff mem 0xf4800000-0xf4800fff irq 17 at device 16.0 on pci0
mpt0: [GIANT-LOCKED]
mpt0: MPI Version=1.2.0.0
lnc0: <PCNet/PCI Ethernet adapter> port 0x1400-0x147f irq 18 at device 17.0 on pci0
lnc0: Attaching PCNet/PCI Ethernet adapter
lnc0: [GIANT-LOCKED]
lnc0: Ethernet address: 00:50:56:9b:42:71
lnc0: if_start running deferred for Giant
lnc0: PCnet-PCI
acpi_acad0: <AC Adapter> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse, device ID 3
ppc0: <Standard parallel printer port> port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
pmtimer0 on isa0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xca000-0xcafff,0xdc000-0xdffff,0xe0000-0xe3fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC" frequency 3397982732 Hz quality 800
Timecounters tick every 1.000 msec
acd0: CDROM <VMware Virtual IDE CDROM Drive/00000001> at ata0-master UDMA33
Waiting 5 seconds for SCSI devices to settle
da0 at mpt0 bus 0 target 0 lun 0
da0: <VMware Virtual disk 1.0> Fixed Direct Access SCSI-2 device 
da0: 80.000MB/s transfers (40.000MHz, offset 127, 16bit), Tagged Queueing Enabled
da0: 15360MB (31457280 512 byte sectors: 255H 63S/T 1958C)
Trying to mount root from ufs:/dev/da0s1a
>How-To-Repeat:
Simply wait a few minutes for the error message to appear on the console or help it a bit by pinging the host for a few minutes.
>Fix:

>Release-Note:
>Audit-Trail:

From: Astrodog <astrodog@gmail.com>
To: bug-followup@FreeBSD.org, fireball@zerouptime.ch
Cc:  
Subject: Re: kern/104056: VMware ESX 3.0: lnc0: Missed packet -- no receive buffer
Date: Sun, 8 Oct 2006 07:18:06 -0500

 Check /usr/ports/emulators. vmware-tools exist for FreeBSD, it should
 be possible to get that to install. See if you can reproduce the
 error, with those.
State-Changed-From-To: open->feedback 
State-Changed-By: ceri 
State-Changed-When: Sun Oct 8 16:20:48 UTC 2006 
State-Changed-Why:  
Does this issue still occur with vmware-tools installed? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=104056 

From: Jonas Nagel <fireball@zerouptime.ch>
To: FreeBSD-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/104056: VMware ESX 3.0: lnc0: Missed packet -- no receive buffer
Date: Sun, 08 Oct 2006 22:30:29 +0200

 The vmware-tools provided in the ports are meant for VMware Workstation,
 namely 5.x for the latest, which is still much older than the ESX Server
 3.0, which has its own VMware Tools.
 
 I don't think I am supposed to use those, since the virtual NIC changed
 a lot on ESX Server 3.0.
 
 -- 
 Jonas Nagel <fireball@zerouptime.ch>
 "Everything we humans say is either meaningless or meaningful. A lot of people never learn the difference." (El Reg)
 

From: Jonas Nagel <fireball@zerouptime.ch>
To: Astrodog <astrodog@gmail.com>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/104056: VMware ESX 3.0: lnc0: Missed packet -- no receive buffer
Date: Sun, 08 Oct 2006 23:19:14 +0200

 Update on that, while the built-in function of 'Install VMware Tools'
 errors out with "A general systems error ocurred: Internal error", the
 manual CD mount, using the tools ISO (which is also attempted in the
 port vmware-tools5) results in:
 
 dns1# /sbin/mount -t cd9660 /dev/acd0  /mnt
 mount_cd9660: /dev/acd0: Input/output error
 
 on the console I get the following error at the same time:
 
 g_vfs_done():acd0[READ(offset=32768, length=2048)]error = 5
 
 So: no go.
 -- 
 Jonas Nagel <fireball@zerouptime.ch>
 

From: Jonas Nagel <fireball@zerouptime.ch>
To: Astrodog <astrodog@gmail.com>
Cc: bug-followup@FreeBSD.org
Subject: Re: kern/104056: VMware ESX 3.0: lnc0: Missed packet -- no receive buffer
Date: Mon, 09 Oct 2006 00:38:09 +0200

 Never mind my last mail; I was able to install the tools through the
 ports. I used the vmware-guestd5 port, since I don't run X on that VM.
 
 It wouldn't install the vmxnet.ko though by default.
 
 There is also only one precompiled for FreeBSD 5.3 on the ISO; I copied
 it over and it loaded fine.
 
 dns1# ll vmxnet.ko 
 -r-xr-xr-x  1 root  wheel  12837 Oct  8 23:59 vmxnet.ko
 dns1# kldstat 
 Id Refs Address    Size     Name
  1    5 0xc0400000 6f0e44   kernel
  2    1 0xc0af1000 59f00    acpi.ko
  3    1 0xc5f0e000 3000     vmmemctl.ko
  4    1 0xc5f11000 4000     vmxnet.ko
 
 dns1# ps ax |grep vmware
 85086  ??  Ss     0:01.93 /usr/local/sbin/vmware-guestd --background /var/run/vmware_guestd.pid --halt-command 
 
 I even put the said vmxnet.ko into /boot/kernel and loaded it using
 'vmxnet_load="YES"'. But this all didn't have any influence over network
 performance.
 
 Specially the connection to other virtual machines is less than
 acceptable. Also note the interesting pattern:
 
 dns1# ping -s 16000 hirtdco01
 PING hirtdco01.hirtdom.local (10.0.0.90): 16000 data bytes
 16008 bytes from 10.0.0.90: icmp_seq=0 ttl=128 time=2.148 ms
 16008 bytes from 10.0.0.90: icmp_seq=1 ttl=128 time=1.854 ms
 16008 bytes from 10.0.0.90: icmp_seq=2 ttl=128 time=878.200 ms
 16008 bytes from 10.0.0.90: icmp_seq=3 ttl=128 time=1.963 ms
 16008 bytes from 10.0.0.90: icmp_seq=4 ttl=128 time=1007.225 ms
 16008 bytes from 10.0.0.90: icmp_seq=5 ttl=128 time=2.003 ms
 16008 bytes from 10.0.0.90: icmp_seq=6 ttl=128 time=1007.256 ms
 16008 bytes from 10.0.0.90: icmp_seq=7 ttl=128 time=167.444 ms
 16008 bytes from 10.0.0.90: icmp_seq=8 ttl=128 time=2.328 ms
 16008 bytes from 10.0.0.90: icmp_seq=9 ttl=128 time=1.985 ms
 (...)
 --- hirtdco01.hirtdom.local ping statistics ---
 88 packets transmitted, 81 packets received, 7% packet loss
 round-trip min/avg/max/stddev = 1.581/298.857/1010.492/417.300 ms
 
 It goes from 1-2 ms up to 1 second and down again or, well, results into
 timeouts.
 
 Any other idea (besides blaming it to VMware)?
 
 -- 
 Jonas Nagel <fireball@zerouptime.ch>
 
 

From: Astrodog <astrodog@gmail.com>
To: "Jonas Nagel" <fireball@zerouptime.ch>
Cc: bug-followup@freebsd.org
Subject: Re: kern/104056: VMware ESX 3.0: lnc0: Missed packet -- no receive buffer
Date: Mon, 9 Oct 2006 00:44:07 -0500

 On 10/8/06, Jonas Nagel <fireball@zerouptime.ch> wrote:
 > Never mind my last mail; I was able to install the tools through the
 > ports. I used the vmware-guestd5 port, since I don't run X on that VM.
 >
 > It wouldn't install the vmxnet.ko though by default.
 >
 > There is also only one precompiled for FreeBSD 5.3 on the ISO; I copied
 > it over and it loaded fine.
 >
 > dns1# ll vmxnet.ko
 > -r-xr-xr-x  1 root  wheel  12837 Oct  8 23:59 vmxnet.ko
 > dns1# kldstat
 > Id Refs Address    Size     Name
 >  1    5 0xc0400000 6f0e44   kernel
 >  2    1 0xc0af1000 59f00    acpi.ko
 >  3    1 0xc5f0e000 3000     vmmemctl.ko
 >  4    1 0xc5f11000 4000     vmxnet.ko
 >
 > dns1# ps ax |grep vmware
 > 85086  ??  Ss     0:01.93 /usr/local/sbin/vmware-guestd --background /var/run/vmware_guestd.pid --halt-command
 >
 > I even put the said vmxnet.ko into /boot/kernel and loaded it using
 > 'vmxnet_load="YES"'. But this all didn't have any influence over network
 > performance.
 >
 > Specially the connection to other virtual machines is less than
 > acceptable. Also note the interesting pattern:
 >
 > dns1# ping -s 16000 hirtdco01
 > PING hirtdco01.hirtdom.local (10.0.0.90): 16000 data bytes
 > 16008 bytes from 10.0.0.90: icmp_seq=0 ttl=128 time=2.148 ms
 > 16008 bytes from 10.0.0.90: icmp_seq=1 ttl=128 time=1.854 ms
 > 16008 bytes from 10.0.0.90: icmp_seq=2 ttl=128 time=878.200 ms
 > 16008 bytes from 10.0.0.90: icmp_seq=3 ttl=128 time=1.963 ms
 > 16008 bytes from 10.0.0.90: icmp_seq=4 ttl=128 time=1007.225 ms
 > 16008 bytes from 10.0.0.90: icmp_seq=5 ttl=128 time=2.003 ms
 > 16008 bytes from 10.0.0.90: icmp_seq=6 ttl=128 time=1007.256 ms
 > 16008 bytes from 10.0.0.90: icmp_seq=7 ttl=128 time=167.444 ms
 > 16008 bytes from 10.0.0.90: icmp_seq=8 ttl=128 time=2.328 ms
 > 16008 bytes from 10.0.0.90: icmp_seq=9 ttl=128 time=1.985 ms
 > (...)
 > --- hirtdco01.hirtdom.local ping statistics ---
 > 88 packets transmitted, 81 packets received, 7% packet loss
 > round-trip min/avg/max/stddev = 1.581/298.857/1010.492/417.300 ms
 >
 > It goes from 1-2 ms up to 1 second and down again or, well, results into
 > timeouts.
 >
 > Any other idea (besides blaming it to VMware)?
 >
 
 What kind of system load is there on that? I've seen FreeBSD under
 VMWare get kinda messed up if the other VMs are heavily loaded.

From: Jonas Nagel <fireball@zerouptime.ch>
To: Astrodog <astrodog@gmail.com>
Cc: bug-followup@freebsd.org
Subject: Re: kern/104056: VMware ESX 3.0: lnc0: Missed packet -- no receive buffer
Date: Mon, 09 Oct 2006 08:16:52 +0200

 Well maybe you shouldn't quote on reply to bug-followup@.
 
 Average CPU usage of the physical host for the past day (it's 8:15 am
 now) was at 11%, max. 21%.
 
 I wouldn't file a PR if the cause was that obvious. The other VMs on the
 host(s) (there are two in the DRS cluster of that VI3) are not showing
 that behaviour, so it must be a driver issue on the FreeBSD side, pretty
 much.
 
 -- 
 Jonas Nagel <fireball@zerouptime.ch>
 

From: Jonas Nagel <fireball@zerouptime.ch>
To: Astrodog <astrodog@gmail.com>
Cc: bug-followup@freebsd.org
Subject: Re: kern/104056: VMware ESX 3.0: lnc0: Missed packet -- no receive buffer
Date: Tue, 10 Oct 2006 18:55:45 +0200

 I just verified this; the kernel message ain't lying; its a receive-buffer
 overflow, pretty easily provoked by using lots of frags.
 
 While pinging with no packet size modifications I get a good latency
 with no losses.
 
 dns1# ping hirtdco02
 PING hirtdco02.hirtdom.local (10.0.0.91): 56 data bytes
 64 bytes from 10.0.0.91: icmp_seq=0 ttl=128 time=0.478 ms
 64 bytes from 10.0.0.91: icmp_seq=1 ttl=128 time=0.024 ms
 64 bytes from 10.0.0.91: icmp_seq=2 ttl=128 time=0.089 ms
 64 bytes from 10.0.0.91: icmp_seq=3 ttl=128 time=0.004 ms
 64 bytes from 10.0.0.91: icmp_seq=4 ttl=128 time=1.325 ms
 64 bytes from 10.0.0.91: icmp_seq=5 ttl=128 time=0.000 ms
 64 bytes from 10.0.0.91: icmp_seq=6 ttl=128 time=0.019 ms
 64 bytes from 10.0.0.91: icmp_seq=7 ttl=128 time=0.301 ms
 64 bytes from 10.0.0.91: icmp_seq=8 ttl=128 time=0.431 ms
 (...)
 ^C
 --- hirtdco02.hirtdom.local ping statistics ---
 239 packets transmitted, 239 packets received, 0% packet loss
 round-trip min/avg/max/stddev = 0.000/0.335/2.464/0.415 ms
 
 But when using a ~ 16k packet size, I have those tremendous problems,
 accompanied by the said kernel messages. When we analyze the below
 tcpdump, we can see that apparently a couple of frags of the echo
 replies, which didn't made it through, are missing. Only sequence 2 and
 8 made it through competely and are thus displayed in ping.
 
 dmesg excerpt during the below test:
 (...)
 lnc0: promiscuous mode enabled
 lnc0: Missed packet -- no receive buffer
 lnc0: Missed packet -- no receive buffer
 lnc0: Missed packet -- no receive buffer
 lnc0: Missed packet -- no receive buffer
 lnc0: Missed packet -- no receive buffer
 lnc0: Missed packet -- no receive buffer
 lnc0: Missed packet -- no receive buffer
 lnc0: Missed packet -- no receive buffer
 lnc0: Missed packet -- no receive buffer
 lnc0: promiscuous mode disabled
 (...few more to follow here...)
 
 dns1# ping -s 16000 hirtdco02
 PING hirtdco02.hirtdom.local (10.0.0.91): 16000 data bytes
 16008 bytes from 10.0.0.91: icmp_seq=2 ttl=128 time=584.180 ms
 16008 bytes from 10.0.0.91: icmp_seq=8 ttl=128 time=1.511 ms
 ^C
 --- hirtdco02.hirtdom.local ping statistics ---
 12 packets transmitted, 2 packets received, 83% packet loss
 round-trip min/avg/max/stddev = 1.511/292.845/584.180/291.334 ms
 
 dns1# tcpdump -i lnc0 icmp
 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
 listening on lnc0, link-type EN10MB (Ethernet), capture size 96 bytes
 18:29:42.881681 IP 10.0.0.106 > hirtdco02.hirtdom.local: ICMP echo request, id 36377, seq 0, length 1480
 18:29:42.882696 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:42.883211 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:42.883736 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:42.884596 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:42.884721 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:42.885235 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:42.885698 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:42.886241 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:42.886727 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:42.887201 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:42.887807 IP hirtdco02.hirtdom.local > 10.0.0.106: ICMP echo reply, id 36377, seq 0, length 1480
 18:29:42.887817 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:42.887825 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:42.887832 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:42.887840 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:42.887846 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:42.887854 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:42.887861 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:43.891630 IP 10.0.0.106 > hirtdco02.hirtdom.local: ICMP echo request, id 36377, seq 1, length 1480
 18:29:43.891766 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:43.891899 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:43.892025 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:43.892146 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:43.892266 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:43.892403 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:43.892525 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:43.892646 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:43.892767 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:43.892896 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:43.893148 IP hirtdco02.hirtdom.local > 10.0.0.106: ICMP echo reply, id 36377, seq 1, length 1480
 18:29:43.893159 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:43.893166 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:43.893173 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:43.893180 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:43.893186 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:43.893193 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:43.893200 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:44.897146 IP 10.0.0.106 > hirtdco02.hirtdom.local: ICMP echo request, id 36377, seq 2, length 1480
 18:29:44.897285 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:44.897409 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:44.897529 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:44.897657 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:44.897777 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:44.897896 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:44.898019 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:44.898145 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:44.898265 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:44.898384 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:44.899271 IP hirtdco02.hirtdom.local > 10.0.0.106: ICMP echo reply, id 36377, seq 2, length 1480
 18:29:44.899283 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:44.899702 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:44.899714 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:44.899722 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:44.899729 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:44.899735 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:44.899749 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:44.899755 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:44.899763 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:45.481081 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:45.900342 IP 10.0.0.106 > hirtdco02.hirtdom.local: ICMP echo request, id 36377, seq 3, length 1480
 18:29:45.900482 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:45.900610 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:45.900768 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:45.900891 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:45.901027 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:45.901152 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:45.901274 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:45.901394 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:45.901523 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:45.901647 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:45.901796 IP hirtdco02.hirtdom.local > 10.0.0.106: ICMP echo reply, id 36377, seq 3, length 1480
 18:29:45.901914 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:45.901933 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:45.901940 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:45.901947 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:45.901954 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:45.901960 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:45.901968 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:45.901975 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:45.901981 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:46.905688 IP 10.0.0.106 > hirtdco02.hirtdom.local: ICMP echo request, id 36377, seq 4, length 1480
 18:29:46.905689 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:46.905689 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:46.905689 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:46.905689 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:46.906044 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:46.906166 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:46.906323 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:46.906444 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:46.906562 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:46.906685 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:46.907118 IP hirtdco02.hirtdom.local > 10.0.0.106: ICMP echo reply, id 36377, seq 4, length 1480
 18:29:46.907134 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:46.907142 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:46.907149 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:46.907155 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:46.907162 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:46.907226 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:46.907234 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:47.047622 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:47.047638 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:47.910965 IP 10.0.0.106 > hirtdco02.hirtdom.local: ICMP echo request, id 36377, seq 5, length 1480
 18:29:47.911286 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:47.911422 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:47.911556 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:47.911679 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:47.911804 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:47.911932 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:47.912059 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:47.912183 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:47.912304 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:47.912429 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:47.912681 IP hirtdco02.hirtdom.local > 10.0.0.106: ICMP echo reply, id 36377, seq 5, length 1480
 18:29:47.912692 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:47.912703 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:47.912711 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:47.912717 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:47.912724 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:47.912731 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:47.912737 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:48.917048 IP 10.0.0.106 > hirtdco02.hirtdom.local: ICMP echo request, id 36377, seq 6, length 1480
 18:29:48.917180 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:48.917315 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:48.917438 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:48.917559 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:48.917684 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:48.917824 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:48.917945 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:48.918064 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:48.918186 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:48.918317 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:48.918585 IP hirtdco02.hirtdom.local > 10.0.0.106: ICMP echo reply, id 36377, seq 6, length 1480
 18:29:48.918596 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:48.918604 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:48.918611 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:48.918617 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:48.918627 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:48.918633 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:48.918642 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:49.922528 IP 10.0.0.106 > hirtdco02.hirtdom.local: ICMP echo request, id 36377, seq 7, length 1480
 18:29:49.922529 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:49.922529 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:49.922837 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:49.922961 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:49.923030 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:49.923393 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:49.923517 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:49.923531 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:49.923532 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:49.923532 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:49.924033 IP hirtdco02.hirtdom.local > 10.0.0.106: ICMP echo reply, id 36377, seq 7, length 1480
 18:29:49.924033 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:49.924033 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:49.924033 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:49.924033 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:49.924033 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:49.924033 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:49.924033 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:50.927807 IP 10.0.0.106 > hirtdco02.hirtdom.local: ICMP echo request, id 36377, seq 8, length 1480
 18:29:50.927808 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:50.927808 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:50.927808 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:50.928071 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:50.928196 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:50.928309 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:50.928623 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:50.928746 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:50.928809 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:50.928811 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:50.929308 IP hirtdco02.hirtdom.local > 10.0.0.106: ICMP echo reply, id 36377, seq 8, length 1480
 18:29:50.929310 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:50.929311 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:50.929312 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:50.929312 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:50.929312 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:50.929312 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:50.929312 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:50.929312 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:50.929312 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:50.929312 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:51.934050 IP 10.0.0.106 > hirtdco02.hirtdom.local: ICMP echo request, id 36377, seq 9, length 1480
 18:29:51.934184 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:51.934310 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:51.934430 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:51.934550 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:51.934679 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:51.934804 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:51.934921 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:51.935041 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:51.935165 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:51.935283 IP 10.0.0.106 > hirtdco02.hirtdom.local: icmp
 18:29:51.935829 IP hirtdco02.hirtdom.local > 10.0.0.106: ICMP echo reply, id 36377, seq 9, length 1480
 18:29:51.935847 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:51.935859 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:51.935872 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:51.935882 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:51.935893 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:51.935904 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 18:29:51.935915 IP hirtdco02.hirtdom.local > 10.0.0.106: icmp
 ^C
 200 packets captured
 276 packets received by filter
 0 packets dropped by kernel
 
 I've also tried pinging different machines and on some, the VM in
 question misses certain packets (replies only) completely.
 
 
 -- 
 Jonas Nagel <fireball@zerouptime.ch>
 

From: Jonas Nagel <fireball@zerouptime.ch>
To: Astrodog <astrodog@gmail.com>
Cc: bug-followup@freebsd.org
Subject: Re: kern/104056: VMware ESX 3.0: lnc0: Missed packet -- no receive buffer
Date: Fri, 17 Nov 2006 07:49:27 +0100

 The VMTN community found a workaround for this:
 
 Edit the .VMX file and replace the type of network which is "vmxnet" by
 default to "e1000". This causes ESX 3.x to present a perfect virtual
 emulation of a Intel E1000 PRO Gigabit Adapter, which apparently seems
 to work very well.
 
 I was unable to verify this myself yet, since I fight now with a
 different problem.
 
 -- 
 Jonas Nagel <fireball@zerouptime.ch>
 "Everything we humans say is either meaningless or meaningful. A lot of people never learn the difference." (El Reg)
 
Responsible-Changed-From-To: freebsd-bugs->remko 
Responsible-Changed-By: remko 
Responsible-Changed-When: Fri Jan 26 21:14:46 UTC 2007 
Responsible-Changed-Why:  
Grab the PR, I think this was resolved with the le driver in HEAD, are you able to test this? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=104056 
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Fri Jun 15 10:06:44 UTC 2007 
State-Changed-Why:  
Feedback timeout (> 4 months). 

http://www.freebsd.org/cgi/query-pr.cgi?pr=104056 
>Unformatted:
