kern/104056: VMware ESX 3.0: lnc0: Missed packet -- no receive buffer

Jonas Nagel fireball at zerouptime.ch
Tue Oct 10 10:00:48 PDT 2006


The following reply was made to PR kern/104056; it has been noted by GNATS.

From: Jonas Nagel <fireball at zerouptime.ch>
To: Astrodog <astrodog at gmail.com>
Cc: bug-followup at 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 at zerouptime.ch>
 


More information about the freebsd-bugs mailing list