From owner-freebsd-current@FreeBSD.ORG Sun Jul 27 16:12:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B07A37B401 for ; Sun, 27 Jul 2003 16:12:20 -0700 (PDT) Received: from mailbox.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A81943F75 for ; Sun, 27 Jul 2003 16:12:19 -0700 (PDT) (envelope-from l.ertl@univie.ac.at) Received: from wireless (adslle.cc.univie.ac.at [131.130.102.11]) by mailbox.univie.ac.at (8.12.2/8.12.2) with ESMTP id h6RNBxwt217712; Mon, 28 Jul 2003 01:12:03 +0200 Date: Mon, 28 Jul 2003 01:11:55 +0200 (CEST) From: Lukas Ertl To: John-Mark Gurney In-Reply-To: <20030727191758.GN10708@funkthat.com> Message-ID: <20030728010746.I587@korben.in.tern> References: <20030727163914.S698@korben.in.tern> <20030727191758.GN10708@funkthat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-DCC-ZID-Univie-Metrics: mailbox 4245; Body=0 Fuz1=0 Fuz2=0 cc: Gary Jennejohn cc: freebsd-current@freebsd.org cc: Mark Blackman Subject: Re: device driver memory leak in 5.1-20030726? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jul 2003 23:12:20 -0000 On Sun, 27 Jul 2003, John-Mark Gurney wrote: > Lukas Ertl wrote this message on Sun, Jul 27, 2003 at 16:43 +0200: > > > > I'm too seeing these annoying kmem_malloc panics on recent -current > > kernels. The laptop I'm using is way off of being overloaded at all, the > > only thing I do is going online using a Bluetooth USB dongle. As soon as I > > generate some network traffic, devbuf allocations go up, until at some > > point the machine panics randomly in kmem_malloc. > > I must note that the USB changes only allocates memory in the M_USB > area which is described by: > usb.c:MALLOC_DEFINE(M_USB, "USB", "USB"); > > So, that means it wouldn't be in the devbuf area. (This is the one of > the points of malloc areas is to help track down stray allocations and > memory leaks). Then I have no explanation. I'm running the box with a WiFi card, generating lots of network traffic, and the box is running fine, no panics, and low devbuf allocation. I'm running the box with the USB Bluetooth dongle, generating much less traffic (it's just a 9.6kbit GSM link), and the box panics within half an hour in kmem_malloc, with devbuf allocation up to 74MB. It must be either in the Bluetooth code or in the USB code. regards, le -- Lukas Ertl eMail: l.ertl@univie.ac.at UNIX Systemadministrator Tel.: (+43 1) 4277-14073 Vienna University Computer Center Fax.: (+43 1) 4277-9140 University of Vienna http://mailbox.univie.ac.at/~le/