From owner-freebsd-current@FreeBSD.ORG Sun Jul 27 22:33:51 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 42D9337B401 for ; Sun, 27 Jul 2003 22:33:51 -0700 (PDT) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 598F243FAF for ; Sun, 27 Jul 2003 22:33:50 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: (qmail 68377 invoked by uid 1002); 28 Jul 2003 05:33:49 -0000 Received: from adsl-64-58-12-196.mho.net (HELO freebsd.org) (64.58.12.196) by smtp.mho.net with SMTP; 28 Jul 2003 05:33:49 -0000 Message-ID: <3F24B5C6.4010403@freebsd.org> Date: Sun, 27 Jul 2003 23:33:58 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John-Mark Gurney References: <20030727163914.S698@korben.in.tern> <20030727191758.GN10708@funkthat.com> In-Reply-To: <20030727191758.GN10708@funkthat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.org cc: Gary Jennejohn cc: Mark Blackman cc: Lukas Ertl 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: Mon, 28 Jul 2003 05:33:51 -0000 John-Mark Gurney wrote: > Lukas Ertl wrote this message on Sun, Jul 27, 2003 at 16:43 +0200: > >>On Sun, 27 Jul 2003, Mark Blackman wrote: >> >> >>>Perhaps it's a USB bug. There seems to be some correspondence between >>>the use of the USB Speedtouch ADSL modem and the out-of-control >>>devbuf allocations. >> >>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). > > >>I have different core dumps and backtraces available, but they don't seem >>to be of much use in this case. I really suspect the USB stuff to be >>leaking. > > > It may be leaking, but it won't be leaking devbuf memory. The only > thing that is in usb (in dev/usb) that uses M_DEVBUF is ukbd. > bus_dma_tag_create() allocates out of M_DEVBUF. Could it be that tags are being created and never destroyed? Scott