Date: Sun, 26 Mar 2006 22:34:22 -0500 From: Stephen Clark <Stephen.Clark@seclark.us> To: stable@freebsd.org Subject: Re: 4.9-4.11 receive network stack lockup Message-ID: <44275D3E.6080808@seclark.us> In-Reply-To: <44275456.7040901@seclark.us> References: <44275456.7040901@seclark.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Stephen Clark wrote: >Hi List, > >I am benchmarking freebsd 4.9, (also tried 4.11), two systems using >nttcp 1.47 from ports >thru a 100mb switch with two realtek 10/100 nics. >I have 50 gre tunnels going thru 50 vpn tunnels between the two machines >as well as >quagga/ospfd with all addresses as neighbors. >Using the following script I occasionally get in a state on the sending >machine where it can send data but not receive it. I have a console that >I run tcpdump on and I see packets go out but none come back, where on >the other machine I see the packets come an a response go back. >Any ideas as to what could be happening? > >for ((i=1;i<51;i++ )); do nttcp -T -w48 -n 32768 10.1.1.$((i*2))& done > >TIA, >Steve >_______________________________________________ >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" > > > Hi List, I am replying to my own message - I've discovered the following if I try to ping localhost I get the following: bash-2.05b# ping localhost PING localhost (127.0.0.1): 56 data bytes ping: sendto: No buffer space available ping: sendto: No buffer space available ^C --- localhost ping statistics --- 2 packets transmitted, 0 packets received, 100% packet loss bash-2.05b# netstat -m 72/1312/5760 mbufs in use (current/peak/max): 72 mbufs allocated to data 0/1214/1440 mbuf clusters in use (current/peak/max) 2756 Kbytes allocated to network (63% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines but if i ping another machine: bash-2.05b# ping 10.254.254.1 PING 10.254.254.1 (10.254.254.1): 56 data bytes ^C --- 10.254.254.1 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss But if I tcpdump on 10.254.254.1 I see: $ sudo tcpdump -nli rl0 tcpdump: listening on rl0 22:30:29.701849 10.254.254.3 > 10.254.254.1: icmp: echo request 22:30:29.701888 10.254.254.1 > 10.254.254.3: icmp: echo reply 22:30:30.702799 10.254.254.3 > 10.254.254.1: icmp: echo request 22:30:30.702833 10.254.254.1 > 10.254.254.3: icmp: echo reply 22:30:31.703541 10.254.254.3 > 10.254.254.1: icmp: echo request 22:30:31.703578 10.254.254.1 > 10.254.254.3: icmp: echo reply 22:30:32.704331 10.254.254.3 > 10.254.254.1: icmp: echo request 22:30:32.704365 10.254.254.1 > 10.254.254.3: icmp: echo reply 22:30:33.183196 10.254.254.2.500 > 10.254.254.1.500: isakmp: phase 1 I ident: [|sa] ^C 11 packets received by filter 0 packets dropped by kernel The packet were going out on the wire - but the system was unable to get the response - I am assuming because it was out of buffer space? Are mbufs getting lost somewhere? Is this a known problem?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44275D3E.6080808>