From owner-freebsd-stable Fri Apr 13 7:46:55 2001 Delivered-To: freebsd-stable@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 837C837B446 for ; Fri, 13 Apr 2001 07:46:38 -0700 (PDT) (envelope-from dhw@whistle.com) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id f3DEkbV19907 for ; Fri, 13 Apr 2001 07:46:37 -0700 (PDT) Received: from pau-amma.whistle.com( 207.76.205.64) by whistle.com via smap (V2.0) id xma019902; Fri, 13 Apr 2001 07:46:21 -0700 Received: (from dhw@localhost) by pau-amma.whistle.com (8.11.1/8.11.1) id f3DEkKj89412 for freebsd-stable@FreeBSD.ORG; Fri, 13 Apr 2001 07:46:20 -0700 (PDT) Date: Fri, 13 Apr 2001 07:46:20 -0700 (PDT) From: David Wolfskill Message-Id: <200104131446.f3DEkKj89412@pau-amma.whistle.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD 4.3RC out of buffer space in network operations In-Reply-To: <3AD707D9.9F2CD909@sympatico.ca> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Fri, 13 Apr 2001 10:06:17 -0400 >From: Brad Laue >sendto in send_tcp_raw: sendto(3, packet, 40, 0, 64.228.82.35, 16) => No >buffer space available >Sleeping 15 seconds then retrying >This occurs mainly when nmap -sS is called, and has just started >occuring within the last few cvsups. I have adjusted NMBCLUSTERS >as well as MAXUSERS and several things using sysctl, with no >success. I saw this yesterday (also using nmap, but -sP) on my laptop: FreeBSD m133.whistle.com 4.3-RC FreeBSD 4.3-RC #16: Thu Apr 12 11:29:44 PDT 2001 root@m138.whistle.com:/common/S2/obj/usr/src/sys/LAPTOP_30W i386 I had a couple of local modifications affecting the interface in use (an0), so it wasn't apparent to me that this might be something that others would (necessarily or likely) see (which is one reason I didn't mention it then). >The one peculiarity is that the interface in question is tunneling >PPPoE. It seems generally incapable of communicating with nmap normally, >manifesting many odd behaviours (such as nmap not knowing which >interface on which to route a scan, even though it is the default >route). In my case, there's no PPPoE involved, so I suspect that it's not likely an issue. Also, the machine has 256 MB RAM; maxusers is set to 128. I have ready access to a local repository, and can try things out reasonably quickly. Here's a diff of GENERIC vs. LAPTOP_30W (my kernel config file): --- GENERIC Fri Apr 6 05:10:12 2001 +++ LAPTOP_30W Mon Apr 9 13:59:17 2001 @@ -15,19 +15,15 @@ # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # -# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.23 2001/03/07 08:08:42 imp Exp $ +# $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.20 2000/10/31 23:16:07 n_hibma Exp $ machine i386 -cpu I386_CPU -cpu I486_CPU -cpu I586_CPU cpu I686_CPU -ident GENERIC -maxusers 32 +ident "LAPTOP_30W" +maxusers 128 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols -options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem @@ -75,53 +72,26 @@ device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives -device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering +#options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers -device ahb # EISA AHA1742 family -device ahc # AHA2940 and onboard AIC7xxx devices -device amd # AMD 53C974 (Tekram DC-390(T)) -device isp # Qlogic family -device ncr # NCR/Symbios Logic -device sym # NCR/Symbios Logic (newer chipsets) -options SYM_SETUP_LP_PROBE_MAP=0x40 - # Allow ncr to attach legacy NCR devices when - # both sym and ncr are configured - -device adv0 at isa? -device adw -device bt0 at isa? -device aha0 at isa? -device aic0 at isa? - -device ncv # NCR 53C500 -device nsp # Workbit Ninja SCSI-3 -device stg # TMC 18C30/18C50 # SCSI peripherals -device scbus # SCSI bus (required) -device da # Direct Access (disks) -device sa # Sequential Access (tape etc) -device cd # CD -device pass # Passthrough device (direct SCSI access) # RAID controllers interfaced to the SCSI subsystem -device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID -device dpt # DPT Smartcache - See LINT for options! -device mly # Mylex AcceleRAID/eXtremeRAID # RAID controllers -device aac # Adaptec FSA RAID, Dell PERC2/PERC3 -device ida # Compaq Smart RAID -device amr # AMI MegaRAID -device mlx # Mylex DAC960 family -device twe # 3ware Escalade # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 +# Options for psm: +options PSM_DEBUG=0 # 1 for debugging +options PSM_HOOKRESUME #hook the system resume event, useful + #for some laptops +options PSM_RESETAFTERSUSPEND #reset the device at the resume event device vga0 at isa? @@ -142,12 +112,14 @@ device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) -device apm0 at nexus? disable flags 0x20 # Advanced Power Management +device apm0 at nexus? flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support device card device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable +# You may need to reset all pccards after resuming +options PCIC_RESUME_RESET # reset after resume # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 @@ -187,31 +159,22 @@ # ISA Ethernet NICs. device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 -device ex -device ep -device fe0 at isa? port 0x300 -# Xircom Ethernet -device xe -# PRISM I IEEE 802.11b wireless NIC. -device awi # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attachment needed # and resources will always be dynamically assigned by the pccard code. device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those parameters here. device an +# Xircom Ethernet +device xe # The probe order of these is presently determined by i386/isa/isa_compat.c. -device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 -device lnc0 at isa? port 0x280 irq 10 drq 0 -device cs0 at isa? port 0x300 -device sn0 at isa? port 0x300 irq 10 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP @@ -224,7 +187,7 @@ # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! -pseudo-device bpf #Berkeley packet filter +pseudo-device bpf 3 #Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface @@ -234,10 +197,25 @@ device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer -device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device uscanner # Scanners # USB Ethernet, requires mii device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet + +# For non-pnp sound cards with no bridge drivers only: +# device pcm0 at isa? irq 10 drq 1 flags 0x0 +# +# For PnP/PCI sound cards +device pcm + +# Not controlled by `snd' +device pca0 at isa? port IO_TIMER1 + +# +# Allow user-mode programs to manipulate their local descriptor tables. +# This option is required for the WINE Windows(tm) emulator, and is +# not used by anything else (that we know of). +# +options USER_LDT #allow user-level control of i386 ldt Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator Desk: 650/577-7158 TIE: 8/499-7158 Cell: 650/759-0823 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message