From owner-freebsd-current@FreeBSD.ORG Sun Jul 27 12:18:29 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 057D637B401 for ; Sun, 27 Jul 2003 12:18:29 -0700 (PDT) Received: from mail.cyberonic.com (mail.cyberonic.com [4.17.179.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15BB343F85 for ; Sun, 27 Jul 2003 12:18:28 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (node-40244c0a.sfo.onnet.us.uu.net [64.36.76.10]) by mail.cyberonic.com (8.12.8/8.12.5) with ESMTP id h6RJnl0n012798; Sun, 27 Jul 2003 15:49:48 -0400 Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.9/8.11.6) id h6RJHwo3082135; Sun, 27 Jul 2003 12:17:58 -0700 (PDT) (envelope-from jmg) Date: Sun, 27 Jul 2003 12:17:58 -0700 From: John-Mark Gurney To: Lukas Ertl Message-ID: <20030727191758.GN10708@funkthat.com> Mail-Followup-To: Lukas Ertl , Mark Blackman , Gary Jennejohn , freebsd-current@freebsd.org References: <20030727163914.S698@korben.in.tern> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030727163914.S698@korben.in.tern> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html 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 Reply-To: John-Mark Gurney 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 19:18:29 -0000 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. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."