Date: Tue, 4 Sep 2001 05:15:10 -0700 (PDT) From: Soonmyung Hong <sonnet@teatime.org> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/30307: dmesg output: looutput: mbuf allocation failed Message-ID: <200109041215.f84CFAt72206@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 30307 >Category: kern >Synopsis: dmesg output: looutput: mbuf allocation failed >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Sep 04 05:20:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Soonmyung Hong >Release: FreeBSD 4.4-RC #0 i386 >Organization: Innovay Inc >Environment: FreeBSD svr1.netssenger.com 4.4-RC FreeBSD 4.4-RC #0: Mon Aug 27 22:38:53 KST 2001 root@svr1.netssenger.com:/usr/src/sys/compile/HELFIRE i386 >Description: Basically, It is same problem as kern/20927. But It makes actual trouble. If it happened, networking doesn't work properly(ex: can't login via network, etc). In previous PR(kern/20927) itojun mentioned "out of mbuf" problem. But in my experience, machine's netstat -m report enough mbuf remained. It seems like after enough progress of mbuf fragmentation, system couldn't get contiguous mbuf. I got this problem twice, and that machine's uptime is 30day, 41day. >How-To-Repeat: Unfortunately, have no idea. It is heavy loaded network server machine uses about 2500 connection via loopback interface. >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200109041215.f84CFAt72206>