ping: sendto: No buffer space available

2005-03-10 Thread Mario Sergio Fujikawa Ferreira
Hi,

  I have been experiencing this

$ ping 10.1.1.1
PING 10.1.1.1 (10.1.1.1): 56 data bytes
ping: sendto: No buffer space available
ping: sendto: No buffer space available

  Does anyone have any ideas? Doing

# ifconfig fxp0 down
# ifconfig fxp0 up

fixes it but it won't recover otherwise.

  I am running a matched world-kernel.

$ uname -a
FreeBSD exxodus.fedaykin.here 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #0: Fri Mar 
 4 01:52:24 BRT 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LIOUX  i386


  Please let me if more information is required.

$ ifconfig -a
fxp0: flags=19843UP,BROADCAST,RUNNING,SIMPLEX,LINK0,MULTICAST,POLLING mtu 1500
options=4bRXCSUM,TXCSUM,VLAN_MTU,POLLING
inet 10.1.1.2 netmask 0xff80 broadcast 10.0.0.127
ether 00:00:00:00:00:00
media: Ethernet autoselect (100baseTX full-duplex)
status: active
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet 127.0.0.1 netmask 0xff00 

$ netstat -m
1347 mbufs in use
835/25600 mbuf clusters in use (current/max)
0/38/6656 sfbufs in use (current/peak/max)
2006 KBytes allocated to network
0 requests for sfbufs denied
0 requests for sfbufs delayed
0 requests for I/O initiated by sendfile
2732 calls to protocol drain routines


$ cat /var/run/dmesg.boot

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...9 9 9 8 8 2 2 1 1 1 0 0 0 0 done
No buffers busy after final sync
Copyright (c) 1992-2005 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 5.4-PRERELEASE #0: Fri Mar  4 01:52:24 BRT 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/LIOUX
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) XP 2600+ (1917.81-MHz 686-class CPU)
  Origin = AuthenticAMD  Id = 0x6a0  Stepping = 0
  
Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
  AMD Features=0xc040AMIE,DSP,3DNow!
real memory  = 2146697216 (2047 MB)
avail memory = 2095230976 (1998 MB)
ACPI APIC Table: A M I  OEMAPIC 
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 Version 0.3 irqs 0-23 on motherboard
npx0: math processor on motherboard
npx0: INT 16 interface
acpi0: A M I OEMRSDT on motherboard
acpi0: Power Button (fixed)
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0
cpu0: ACPI CPU on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
agp0: VIA KT880 host to PCI bridge mem 0xe000-0xefff at device 0.0 on 
pci0
pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
drm0: Matrox G400/G450 (AGP) mem 
0xfe00-0xfe7f,0xfeafc000-0xfeaf,0xfa00-0xfbff irq 16 at 
device 0.0 on pci1
info: [drm] AGP at 0xe000 256MB
info: [drm] Initialized mga 3.1.0 20021029 on minor 0
bktr0: BrookTree 878 mem 0xfd9fe000-0xfd9fefff irq 19 at device 7.0 on pci0
smbus0: System Management Bus on bktr0
iicbb0: I2C bit-banging driver on bktr0
iicbus0: Philips I2C bus on iicbb0 master-only
iicsmb0: SMBus over I2C bridge on iicbus0
smbus1: System Management Bus on iicsmb0
bktr0: Hauppauge Model 44001 C110
bktr0: Hauppauge WinCast/TV.
pci0: multimedia at device 7.1 (no driver attached)
fxp0: Intel 82550 Pro/100 Ethernet port 0xb800-0xb83f mem 
0xfebc-0xfebd,0xfebfe000-0xfebfefff irq 18 at device 8.0 on pci0
miibus0: MII bus on fxp0
inphy0: i82555 10/100 media interface on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:02:b3:2d:b2:de
pci0: multimedia, audio at device 10.0 (no driver attached)
pci0: input device at device 10.1 (no driver attached)
pci0: serial bus, FireWire at device 10.2 (no driver attached)
atapci0: VIA 6420 SATA150 controller port 
0xc800-0xc80f,0xcc00-0xcc03,0xd000-0xd007,0xd400-0xd403,0xd800-0xd807 irq 20 at 
device 15.0 on pci0
ata2: channel #0 on atapci0
ata3: channel #1 on atapci0
atapci1: VIA 8237 UDMA133 controller port 
0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0
ata0: channel #0 on atapci1
ata1: channel #1 on atapci1
uhci0: VIA 83C572 USB controller port 0xdc00-0xdc1f irq 21 at device 16.0 on 
pci0
usb0: VIA 83C572 USB controller on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: VIA 83C572 USB controller port 0xe000-0xe01f irq 21 at device 16.1 on 
pci0
usb1: VIA 83C572 USB controller on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: VIA 83C572 USB controller port 0xe400-0xe41f irq 21 at device 16.2 on 
pci0
usb2: VIA

Re: ping: sendto: No buffer space available

2005-03-10 Thread Daniel Eischen
On Thu, 10 Mar 2005, Mario Sergio Fujikawa Ferreira wrote:

 Hi,

   I have been experiencing this

 $ ping 10.1.1.1
 PING 10.1.1.1 (10.1.1.1): 56 data bytes
 ping: sendto: No buffer space available
 ping: sendto: No buffer space available

   Does anyone have any ideas? Doing

 # ifconfig fxp0 down
 # ifconfig fxp0 up

 fixes it but it won't recover otherwise.

Yeah, I've gotten it also and on 4.x as well.  It occurred on
both de and fxp devices as well.  The box is a router with 4
or 5 interfaces which are nowhere near fully loaded.  We only
get this problem on the interface that is connected to a hub;
all other interfaces are on switches.

It is annoying because it happens once every week or two.

-- 
DE

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


ping: sendto: No buffer space available

2004-01-14 Thread Pavel S. Shirshov
Hello.

OS:
# uname -a
FreeBSD devel.ucsnet.ru 4.8-RELEASE-p13 FreeBSD 4.8-RELEASE-p13 #9: Wed Nov 26 
12:38:10 YEKT 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/PAVELSH_DEVEL  i386

Problem - error message No buffer space available.
But,
# netstat -m
145/18656/32768 mbufs in use (current/peak/max):
144 mbufs allocated to data
1 mbufs allocated to packet headers
142/628/8192 mbuf clusters in use (current/peak/max)
5920 Kbytes allocated to network (24% of mb_map in use)
25 requests for memory denied
1 requests for memory delayed
0 calls to protocol drain routines

Peak was 18656, max 32768. Why i'm got message No buffer space
available?

P.S.:
# sysctl -a net.inet
net.inet.ip.portrange.lowfirst: 1023
net.inet.ip.portrange.lowlast: 600
net.inet.ip.portrange.first: 1024
net.inet.ip.portrange.last: 5000
net.inet.ip.portrange.hifirst: 49152
net.inet.ip.portrange.hilast: 65535
net.inet.ip.forwarding: 1
net.inet.ip.redirect: 1
net.inet.ip.ttl: 64
net.inet.ip.rtexpire: 315
net.inet.ip.rtminexpire: 10
net.inet.ip.rtmaxcache: 128
net.inet.ip.sourceroute: 0
net.inet.ip.intr_queue_maxlen: 100
net.inet.ip.intr_queue_drops: 0
net.inet.ip.accept_sourceroute: 0
net.inet.ip.fastforwarding: 0
net.inet.ip.keepfaith: 0
net.inet.ip.subnets_are_local: 0
net.inet.ip.dummynet.hash_size: 64
net.inet.ip.dummynet.curr_time: 60478441
net.inet.ip.dummynet.ready_heap: 0
net.inet.ip.dummynet.extract_heap: 0
net.inet.ip.dummynet.searches: 0
net.inet.ip.dummynet.search_steps: 0
net.inet.ip.dummynet.expire: 1
net.inet.ip.dummynet.max_chain_len: 16
net.inet.ip.dummynet.red_lookup_depth: 256
net.inet.ip.dummynet.red_avg_pkt_size: 512
net.inet.ip.dummynet.red_max_pkt_size: 1500
net.inet.ip.fw.enable: 1
net.inet.ip.fw.one_pass: 1
net.inet.ip.fw.debug: 1
net.inet.ip.fw.verbose: 1
net.inet.ip.fw.verbose_limit: 0
net.inet.ip.fw.dyn_buckets: 256
net.inet.ip.fw.curr_dyn_buckets: 256
net.inet.ip.fw.dyn_count: 0
net.inet.ip.fw.dyn_max: 1000
net.inet.ip.fw.static_count: 33
net.inet.ip.fw.dyn_ack_lifetime: 300
net.inet.ip.fw.dyn_syn_lifetime: 20
net.inet.ip.fw.dyn_fin_lifetime: 1
net.inet.ip.fw.dyn_rst_lifetime: 1
net.inet.ip.fw.dyn_udp_lifetime: 10
net.inet.ip.fw.dyn_short_lifetime: 5
net.inet.ip.fw.dyn_grace_time: 10
net.inet.ip.maxfragpackets: 256
net.inet.ip.maxfragsperpacket: 16
net.inet.ip.sendsourcequench: 0
net.inet.ip.check_interface: 0
net.inet.ip.stealth: 0
net.inet.icmp.maskrepl: 0
net.inet.icmp.icmplim: 200
net.inet.icmp.drop_redirect: 0
net.inet.icmp.log_redirect: 0
net.inet.icmp.icmplim_output: 1
net.inet.icmp.bmcastecho: 0
net.inet.tcp.rfc1323: 1
net.inet.tcp.rfc1644: 0
net.inet.tcp.mssdflt: 512
net.inet.tcp.keepidle: 720
net.inet.tcp.keepintvl: 75000
net.inet.tcp.sendspace: 32768
net.inet.tcp.recvspace: 57344
net.inet.tcp.keepinit: 75000
net.inet.tcp.delacktime: 100
net.inet.tcp.log_in_vain: 0
net.inet.tcp.blackhole: 0
net.inet.tcp.delayed_ack: 1
net.inet.tcp.drop_synfin: 0
net.inet.tcp.path_mtu_discovery: 1
net.inet.tcp.slowstart_flightsize: 1
net.inet.tcp.local_slowstart_flightsize: 4
net.inet.tcp.newreno: 1
net.inet.tcp.tcbhashsize: 512
net.inet.tcp.do_tcpdrain: 1
net.inet.tcp.pcbcount: 66
net.inet.tcp.icmp_may_rst: 1
net.inet.tcp.isn_reseed_interval: 0
net.inet.tcp.inflight_enable: 0
net.inet.tcp.inflight_debug: 0
net.inet.tcp.inflight_min: 6144
net.inet.tcp.inflight_max: 1073725440
net.inet.tcp.inflight_stab: 20
net.inet.tcp.syncookies: 1
net.inet.tcp.syncache.bucketlimit: 30
net.inet.tcp.syncache.cachelimit: 15359
net.inet.tcp.syncache.count: 0
net.inet.tcp.syncache.hashsize: 512
net.inet.tcp.syncache.rexmtlimit: 3
net.inet.tcp.msl: 3
net.inet.tcp.rexmit_min: 1000
net.inet.tcp.rexmit_slop: 200
net.inet.tcp.always_keepalive: 1
net.inet.udp.checksum: 1
net.inet.udp.maxdgram: 9216
net.inet.udp.recvspace: 41600
net.inet.udp.log_in_vain: 0
net.inet.udp.blackhole: 0
net.inet.accf.unloadable: 0
net.inet.raw.maxdgram: 16384
net.inet.raw.recvspace: 16384

P.P.S. Sorry for bad English.

-- 
 ,
 Pavel  mailto:[EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: ping: sendto: No buffer space available

2003-02-04 Thread Michael Sierchio
Dag-Erling Smorgrav wrote:


Interference is preventing the card from transmitting, causing packets
to accumulate in the outgoing queue.



Dummynet queues with RED might help -- changing the behavior from tail
dropping to early detection may improve performance.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message