Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    No buffer space available [solved]

    2.0-RC Snapshot Feedback and Problems - RETIRED
    4
    12
    10.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      wallabybob
      last edited by

      Where do you see this error reported? What messages are reported around it? How do you know its the fibre interface? What types of NICs are you using and for what interfaces? (e.g. WAN is em0, OPT1 is rl0, …) Have you tried using another NIC for the fibre interface?

      1 Reply Last reply Reply Quote 0
      • T
        toomeek
        last edited by

        Is this HP or Dell machine?
        Maybe this will helpful..
        http://iscsi-hp-proliant.blogspot.com/2009/05/tcp-offload-does-not-work-in-windows.html
        I heard that some FC/Gigabit chips cannot handle heavy traffic and need driver update.

        1 Reply Last reply Reply Quote 0
        • H
          Hugovsky
          last edited by

          @wallabybob: It's not reported. When internet goes out, I try to ping the fibre nic and it says "No buffer space available". Other interfaces work perfectly. All nics are realtek 8139D chips. I wonder if that's the problem… I'm going to try different chipsets.

          @TooMeeK: No, it's a machine I've mounted to do the job. Gigabyte Motherboard and intel dual core proc.

          I'm not using tcp offloading.

          1 Reply Last reply Reply Quote 0
          • T
            toomeek
            last edited by

            try this:
            http://lists.freebsd.org/pipermail/freebsd-performance/2003-July/000398.html

            1 Reply Last reply Reply Quote 0
            • H
              Hugovsky
              last edited by

              hum… Interesting...

              Changed nics today. Will test to try if it's solved.

              1 Reply Last reply Reply Quote 0
              • D
                dreamslacker
                last edited by

                Your board should have an onboard RTL8111 (either B or C revision).  Try using that for the fibre connection instead.  It's quite a bit more robust than the 8139.

                1 Reply Last reply Reply Quote 0
                • H
                  Hugovsky
                  last edited by

                  thanks, dreamslacker. I'll try that, too.

                  1 Reply Last reply Reply Quote 0
                  • H
                    Hugovsky
                    last edited by

                    Changed fibre optical nic with cheap sis nic. So far, so good. It should have crashed already.

                    Also, another question: what's this(shown on top -S):

                    "  12 root       15 -60    -     0K   120K WAIT    1   8:04 13.57% intr  "

                    Thanks for the answers.

                    Total system specs:

                    Processors   2
                    Model Intel(R) Core(TM)2 CPU 6420 @ 2.13GHz
                    CPU Speed 2.13 GHz
                    PCI Devices

                    • atapci0: VIA 8237A SATA150 controller
                    • atapci1: VIA 8237A UDMA133 controller
                    • isab0: PCI-ISA bridge
                    • pcib1: PCI-PCI bridge
                    • pcib2: ACPI PCI-PCI bridge
                    • pcib3: ACPI PCI-PCI bridge
                    • re0: RealTek 8169SC/8110SC Single-chip Gigabit Ethernet
                    • rl0: RealTek 8139 10/100BaseTX
                    • sis0: SiS 900 10/100BaseTX
                    • vgapci0: VGA-compatible display
                      IDE Devices
                    • acd0: TSSTcorpCD/DVDW SH-S182D/SB04
                    • ad4: MAXTOR STM3320820AS 3.AAE (Capacity: 312.70 GB)
                    1 Reply Last reply Reply Quote 0
                    • H
                      Hugovsky
                      last edited by

                      update: on console, screen it shows "watch dog time out" in the interface.

                      hardware problem?

                      1 Reply Last reply Reply Quote 0
                      • H
                        Hugovsky
                        last edited by

                        Just for the record, here's my dmesg:

                        Copyright © 1992-2010 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 is a registered trademark of The FreeBSD Foundation.
                        FreeBSD 8.1-RELEASE-p1 #1: Wed Nov  3 02:51:55 EDT 2010
                            sullrich@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj.pfSense/usr/pfSe                                              nsesrc/src/sys/pfSense_SMP.8 i386
                        Timecounter "i8254" frequency 1193182 Hz quality 0
                        CPU: Intel(R) Core(TM)2 CPU          6420  @ 2.13GHz (2128.01-MHz 686-class CPU)
                          Origin = "GenuineIntel"  Id = 0x6f6  Family = 6  Model = f  Stepping = 6
                          Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,c   ="" mov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe="">Features2=0xe3bd <sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm>AMD Features=0x20000000 <lm>AMD Features2=0x1 <lahf>TSC: P-state invariant
                        real memory  = 1610612736 (1536 MB)
                        avail memory = 1558155264 (1485 MB)
                        ACPI APIC Table: <award  asusacpi="">FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
                        FreeBSD/SMP: 1 package(s) x 2 core(s)
                        cpu0 (BSP): APIC ID:  0
                        cpu1 (AP): APIC ID:  1
                        ioapic0: Changing APIC ID to 4
                        ioapic0 <version 0.3="">irqs 0-23 on motherboard
                        ioapic1 <version 0.3="">irqs 24-47 on motherboard
                        ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                        ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /bo                                              ot/loader.conf.
                        module_register_init: MOD_LOAD (ipw_bss_fw, 0xc075a920, 0) error 1
                        ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
                        ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /b                                              oot/loader.conf.
                        module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc075a9e0, 0) error 1
                        wlan: mac acl policy registered
                        ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw                                              /.
                        ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in                                                /boot/loader.conf.
                        module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc075aaa0, 0) error 1
                        wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
                        wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/l                                              oader.conf.
                        module_register_init: MOD_LOAD (wpi_fw, 0xc094f580, 0) error 1
                        kbd1 at kbdmux0
                        cryptosoft0: <software crypto="">on motherboard
                        padlock0: No ACE support.
                        acpi0: <award asusacpi="">on motherboard
                        acpi0: [ITHREAD]
                        acpi0: Power Button (fixed)
                        acpi0: reservation of 100000, 5fde0000 (3) failed
                        acpi0: reservation of 0, a0000 (3) failed
                        Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
                        acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
                        cpu0: <acpi cpu="">on acpi0
                        cpu1: <acpi cpu="">on acpi0
                        acpi_hpet0: <high precision="" event="" timer="">iomem 0xfe800000-0xfe8003ff on acpi0
                        device_attach: acpi_hpet0 attach returned 12
                        acpi_button0: <power button="">on acpi0
                        acpi_button1: <sleep button="">on acpi0
                        pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
                        pci0: <acpi pci="" bus="">on pcib0
                        agp0: <via 3327="" (p4m890)="" host="" to="" pci="" bridge="">on hostb0
                        agp0: aperture size is 128M
                        pcib1: <pci-pci bridge="">at device 1.0 on pci0
                        pci1: <pci bus="">on pcib1
                        pcib2: <acpi pci-pci="" bridge="">irq 27 at device 2.0 on pci0
                        pci2: <acpi pci="" bus="">on pcib2
                        vgapci0: <vga-compatible display="">port 0xcc00-0xcc7f mem 0xdc000000-0xdcffffff,0                                              xc0000000-0xcfffffff,0xda000000-0xdbffffff irq 24 at device 0.0 on pci2
                        atapci0: <via 8237a="" sata150="" controller="">port 0xfc00-0xfc07,0xf800-0xf803,0xf400-                                              0xf407,0xf000-0xf003,0xec00-0xec0f,0xe800-0xe8ff irq 21 at device 15.0 on pci0
                        atapci0: [ITHREAD]
                        ata2: <ata 0="" channel="">on atapci0
                        ata2: [ITHREAD]
                        ata3: <ata 1="" channel="">on atapci0
                        ata3: [ITHREAD]
                        atapci1: <via 8237a="" udma133="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376                                              ,0xe400-0xe40f at device 15.1 on pci0
                        ata0: <ata 0="" channel="">on atapci1
                        ata0: [ITHREAD]
                        ata1: <ata 1="" channel="">on atapci1
                        ata1: [ITHREAD]
                        isab0: <pci-isa bridge="">at device 17.0 on pci0
                        isa0: <isa bus="">on isab0
                        pcib3: <acpi pci-pci="" bridge="">at device 19.1 on pci0
                        pci4: <acpi pci="" bus="">on pcib3
                        rl0: <realtek 10="" 8139="" 100basetx="">port 0xbc00-0xbcff mem 0xdfeff000-0xdfeff0ff ir                                              q 17 at device 3.0 on pci4
                        miibus0: <mii bus="">on rl0
                        rlphy0: <realtek internal="" media="" interface="">PHY 0 on miibus0
                        rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
                        rl0: [ITHREAD]
                        sis0: <sis 10="" 900="" 100basetx="">port 0xb800-0xb8ff mem 0xdfefe000-0xdfefefff irq 19                                                at device 5.0 on pci4
                        miibus1: <mii bus="">on sis0
                        ukphy0: <generic ieee="" 802.3u="" media="" interface="">PHY 0 on miibus1
                        ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
                        sis0: [ITHREAD]
                        re0: <realtek 8169sc="" 8110sc="" single-chip="" gigabit="" ethernet="">port 0xb400-0xb4ff mem                                                0xdfefd000-0xdfefd0ff irq 20 at device 7.0 on pci4
                        re0: Chip rev. 0x18000000
                        re0: MAC rev. 0x00000000
                        miibus2: <mii bus="">on re0
                        rgephy0: <rtl8169s 8110s="" 8211b="" media="" interface="">PHY 1 on miibus2
                        rgephy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-F                                              DX, auto
                        re0: [FILTER]
                        pcib4: <acpi host-pci="" bridge="">on acpi0
                        pci128: <acpi pci="" bus="">on pcib4
                        acpi_tz0: <thermal zone="">on acpi0
                        atrtc0: <at realtime="" clock="">port 0x70-0x73 on acpi0
                        atkbdc0: <keyboard controller="" (i8042)="">port 0x60,0x64 irq 1 on acpi0
                        atkbd0: <at keyboard="">irq 1 on atkbdc0
                        kbd0 at atkbd0
                        atkbd0: [GIANT-LOCKED]
                        atkbd0: [ITHREAD]
                        pmtimer0 on isa0
                        sc0: <system console="">at flags 0x100 on isa0
                        sc0: VGA <16 virtual consoles, flags=0x300>
                        vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
                        ppc0: parallel port not found.
                        est0: <enhanced speedstep="" frequency="" control="">on cpu0
                        p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
                        est1: <enhanced speedstep="" frequency="" control="">on cpu1
                        est: CPU supports Enhanced Speedstep, but is not recognized.
                        est: cpu_vendor GenuineIntel, msr 82a082a0600082a
                        device_attach: est1 attach returned 6
                        p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
                        Timecounters tick every 1.000 msec
                        IPsec: Initialized Security Association Processing.
                        acd0: DVDR <tsstcorpcd dvdw="" sh-s182d="" sb04="">at ata1-master UDMA33
                        ad4: 305245MB <maxtor stm3320820as="" 3.aae="">at ata2-master UDMA100 SATA 1.5Gb/s
                        SMP: AP CPU #1 Launched!
                        Trying to mount root from ufs:/dev/ad4s1a
                        pflog0: promiscuous mode enabled
                        pid 58048 (squid), uid 62: exited on signal 6
                        rl0: promiscuous mode enabled
                        rl0: promiscuous mode disabled
                        rl0: promiscuous mode enabled
                        sis0: promiscuous mode enabled
                        sis0: promiscuous mode disabled
                        sis0: promiscuous mode enabled
                        rl0_vlan2: promiscuous mode enabled
                        rl0_vlan2: promiscuous mode disabled
                        rl0_vlan2: promiscuous mode enabled
                        ng0: changing name to 'pppoe2'
                        arpresolve: can't allocate llinfo for 192.168.1.254
                        arpresolve: can't allocate llinfo for 192.168.1.254
                        arpresolve: can't allocate llinfo for 192.168.1.254
                        arpresolve: can't allocate llinfo for 192.168.1.254
                        arpresolve: can't allocate llinfo for 192.168.1.254
                        arpresolve: can't allocate llinfo for 192.168.1.254
                        arpresolve: can't allocate llinfo for 192.168.1.254</maxtor></tsstcorpcd></cpu></enhanced></cpu></enhanced></generic></system></at></keyboard></at></thermal></acpi></acpi></rtl8169s></mii></realtek></generic></mii></sis></realtek></mii></realtek></acpi></acpi></isa></pci-isa></ata></ata></via></ata></ata></via></vga-compatible></acpi></acpi></pci></pci-pci></via></acpi></acpi></sleep></power></high></acpi></acpi></award></software></version></version></award ></lahf></lm></sse3,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,c >

                        1 Reply Last reply Reply Quote 0
                        • H
                          Hugovsky
                          last edited by

                          Just to let you: this issue seems to be solved. Been running for 3 days without problems. The solution was simple: just check "Hardware Checksum Offloading".

                          This is the only option that is not checked by default. So far, it worked.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post
                          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.