Date: Tue, 20 Feb 1996 14:38:55 -0800 From: Wayne Scott <wscott@ichips.intel.com> To: Bill Fenner <fenner@freefall.freebsd.org> Cc: stable@freebsd.org Subject: Re: "arpresolve: can't allocate llinfo" Message-ID: <199602202239.OAA10245@ichips.intel.com> In-Reply-To: Your message of "Thu, 15 Feb 1996 17:14:22 PST." <199602160114.RAA09932@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Could anyone having trouble with seeing "arpresolve: can't allocate llinfo"
> please apply the following patch, to make the message at least a little
> more useful? The next step is to do a "route get x.x.x.x" on the
> address that gets printed and see what it says.
With -stable from yesterday and your patch I get the following behavior:
# to mount command hangs on any of our fileservers and I get a bunch of messages
# in the log like the one below
pdxlx008 ~ # mount -t nfs pdxfs7:/fs7/a /mnt
^C
arpresolve: can't allocate llinfo for 134.134.50.107
pdxlx008 ~ # route get 134.134.50.107
route to: pdxfs7.intel.com
destination: pdxfs7.intel.com
gateway: pdxfs7.intel.com
interface: de0
flags: <UP,GATEWAY,HOST,DONE>
recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire
16384 16384 0 0 0 0 1500 0
pdxlx008 ~ # ypcat hosts | grep pdxfs7
134.134.124.107 pdxfs7 pdxfs7.intel.com fs7 pdxfs7-f3
134.134.50.107 pdxfs7 pdxfs7.intel.com fs7 pdxfs7-f0
134.134.120.107 pdxfs7 pdxfs7.intel.com fs7 pdxfs7-f2
134.134.57.1 pdxfs7 pdxfs7.intel.com fs7 pdxfs7-ae0
134.134.116.107 pdxfs7 pdxfs7.intel.com fs7 pdxfs7-f1
pdxlx008 ~ # ifconfig -a
de0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 134.134.50.26 netmask 0xffffff00 broadcast 134.134.50.255
ether 00:00:92:91:12:f4
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
pdxlx008 ~ # ping 134.134.50.251
PING 134.134.50.251 (134.134.50.251): 56 data bytes
64 bytes from 134.134.50.251: icmp_seq=0 ttl=255 time=2.870 ms
64 bytes from 134.134.50.251: icmp_seq=1 ttl=255 time=1.673 ms
64 bytes from 134.134.50.251: icmp_seq=2 ttl=255 time=1.326 ms
64 bytes from 134.134.50.251: icmp_seq=3 ttl=255 time=1.553 ms
64 bytes from 134.134.50.251: icmp_seq=4 ttl=255 time=1.361 ms
^C
--- 134.134.50.251 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 1.326/1.756/2.870 ms
pdxlx008 ~ # ping 134.134.50.107
PING 134.134.50.107 (134.134.50.107): 56 data bytes
^C
--- 134.134.50.107 ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss
pdxlx008 ~ # arp -a
pdxgw01-f0.jf.intel.com (134.134.50.1) at 0:0:c:6:a:ac
pdxgw25-f0.jf.intel.com (134.134.50.25) at 0:0:c:12:f8:cc
pdx065.jf.intel.com (134.134.50.48) at 8:0:5a:d:20:46
ichips.intel.com (134.134.50.200) at 0:40:b:40:8c:1
pdxcs149.intel.com (134.134.50.208) at 2:60:8c:2d:41:a5
pdxcs147.intel.com (134.134.50.212) at 2:60:8c:2d:2f:d1
pdxcs156.intel.com (134.134.50.218) at 2:60:8c:2d:3f:43
pdxgw00-f0.jf.intel.com (134.134.50.250) at 0:0:c:5:6d:f9
floodgate-f4.jf.intel.com (134.134.50.251) at 0:0:c:35:87:d0
After I switch back to the 2.1 kernel I get this:
pdxlx008 ~ # mount -t nfs pdxfs7:/fs7/a /mnt
pdxlx008 ~ # route get 134.134.50.107
route to: pdxfs7.intel.com
destination: pdxfs7.intel.com
interface: de0
flags: <UP,HOST,DONE,LLINFO>
recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire
16384 16384 0 0 0 0 1500 1130
pdxlx008 ~ # ifconfig -a
lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
de0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 134.134.50.26 netmask 0xffffff00 broadcast 134.134.50.255
ether 00:00:92:91:12:f4
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
pdxlx008 ~ # arp -a
pdxgw01-f0.jf.intel.com (134.134.50.1) at (incomplete)
pdxgw25-f0.jf.intel.com (134.134.50.25) at (incomplete)
pdx065.jf.intel.com (134.134.50.48) at 8:0:5a:d:20:46
pdxfs1.intel.com (134.134.50.101) at 0:40:b:40:16:5e
pdxfs2.intel.com (134.134.50.102) at 0:40:b:40:da:ce
pdxfs3.intel.com (134.134.50.103) at 0:40:b:40:5e:7
pdxfs4.intel.com (134.134.50.104) at 0:40:b:40:ac:15
pdxfs6.intel.com (134.134.50.106) at (incomplete)
pdxfs7.intel.com (134.134.50.107) at 0:40:b:40:de:e8
pdxfs8.intel.com (134.134.50.108) at (incomplete)
pdxfs10.intel.com (134.134.50.109) at (incomplete)
pdxfs11.intel.com (134.134.50.111) at 0:40:b:40:5e:eb
pdxfs12.intel.com (134.134.50.112) at (incomplete)
pdxfs20.intel.com (134.134.50.120) at 0:40:b:40:8c:c1
ichips.intel.com (134.134.50.200) at 0:40:b:40:8c:1
pdxcs149.intel.com (134.134.50.208) at 2:60:8c:2d:41:a5
pdxcs147.intel.com (134.134.50.212) at 2:60:8c:2d:2f:d1
pdxcs156.intel.com (134.134.50.218) at 2:60:8c:2d:3f:43
pdxgw00-f0.jf.intel.com (134.134.50.250) at 0:0:c:5:6d:f9
floodgate-f4.jf.intel.com (134.134.50.251) at 0:0:c:35:87:d0
pdxlx008 ~ # ping pdxfs7
PING pdxfs7.intel.com (134.134.50.107): 56 data bytes
64 bytes from 134.134.50.107: icmp_seq=0 ttl=255 time=1.097 ms
64 bytes from 134.134.50.107: icmp_seq=1 ttl=255 time=0.879 ms
64 bytes from 134.134.50.107: icmp_seq=2 ttl=255 time=0.911 ms
64 bytes from 134.134.50.107: icmp_seq=3 ttl=255 time=0.936 ms
64 bytes from 134.134.50.107: icmp_seq=4 ttl=255 time=0.834 ms
64 bytes from 134.134.50.107: icmp_seq=5 ttl=255 time=0.853 ms
64 bytes from 134.134.50.107: icmp_seq=6 ttl=255 time=1.356 ms
64 bytes from 134.134.50.107: icmp_seq=7 ttl=255 time=0.821 ms
64 bytes from 134.134.50.107: icmp_seq=8 ttl=255 time=0.886 ms
^C
--- pdxfs7.intel.com ping statistics ---
9 packets transmitted, 9 packets received, 0% packet loss
round-trip min/avg/max = 0.821/0.952/1.356 ms
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199602202239.OAA10245>