From owner-freebsd-bugs Tue Jun 12 5:30:19 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0738937B616 for ; Tue, 12 Jun 2001 05:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.3/8.11.3) id f5CCU1N78956; Tue, 12 Jun 2001 05:30:01 -0700 (PDT) (envelope-from gnats) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 4909337B405 for ; Tue, 12 Jun 2001 05:28:40 -0700 (PDT) (envelope-from nobody@FreeBSD.org) Received: (from nobody@localhost) by freefall.freebsd.org (8.11.3/8.11.3) id f5CCSe678796; Tue, 12 Jun 2001 05:28:40 -0700 (PDT) (envelope-from nobody) Message-Id: <200106121228.f5CCSe678796@freefall.freebsd.org> Date: Tue, 12 Jun 2001 05:28:40 -0700 (PDT) From: conrad@th.physik.uni-bonn.de To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-1.0 Subject: i386/28098: mbus leakage in FreeBSD 4.3R somewhere Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Number: 28098 >Category: i386 >Synopsis: mbus leakage in FreeBSD 4.3R somewhere >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Jun 12 05:30:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Jan Conrad >Release: FreeBSD 4.3R >Organization: Univ. Bonn, Germany >Environment: FreeBSD wigner.th.physik.uni-bonn.de 4.3-RELEASE FreeBSD 4.3-RELEASE #1: Thu May 24 18:01:27 CEST 2001 conrad@merlin.th.physik.uni-bonn.de:/freebsd/misc/src/sys/compile/MERLIN i386 >Description: There seems to be a mbuf leakage which can be triggered by userland programs (i.e.: gtk-gnutella run by our young folk :-) in 4.3R. The mbufs remain allocated AFTER THE PROGRAM TERMINATES! After the program was running one gets outputs like the following: [159]# netstat -m 1397/4224/6144 mbufs in use (current/peak/max): 1337 mbufs allocated to data 60 mbufs allocated to packet headers 69/806/1536 mbuf clusters in use (current/peak/max) 2668 Kbytes allocated to network (57% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines Normal operation looks like (we run a FreeBSD cluster and our machines are very stable otherwise...) [20]# netstat -m 80/624/6144 mbufs in use (current/peak/max): 77 mbufs allocated to data 3 mbufs allocated to packet headers 64/184/1536 mbuf clusters in use (current/peak/max) 524 Kbytes allocated to network (11% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines If one lets run the program for a longer time, the following error message is generated: Jun 12 11:54:20 wigner /kernel: looutput: mbuf allocation failed Letting it run even further, the system panics with a page fault and dumps core. However the core dump gives no reference to mbufs whatsoever (dumps etc. are available). Du to the broken '-M' of netstat I can give no mbuf output from the core... In addition, even if the system did not yet panic and the program is terminated (with the above err msg occuring several times) the box may panic after a while. This case I observed once, and the mbuf usage had gone back to something like 3000/6144/6144 before the crash >How-To-Repeat: run gtk-gnutella for a while >Fix: unknown >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message