From owner-freebsd-current@FreeBSD.ORG Sun Jul 27 12:14:54 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 6308737B401 for ; Sun, 27 Jul 2003 12:14:54 -0700 (PDT) Received: from peedub.jennejohn.org (p213.54.227.172.tisdip.tiscali.de [213.54.227.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19AA243FA3 for ; Sun, 27 Jul 2003 12:14:53 -0700 (PDT) (envelope-from garyj@jennejohn.org) Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.12.9/8.11.6) with ESMTP id h6RJEjjr001156; Sun, 27 Jul 2003 21:14:46 +0200 (CEST) (envelope-from garyj@peedub.jennejohn.org) Message-Id: <200307271914.h6RJEjjr001156@peedub.jennejohn.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Lukas Ertl In-Reply-To: Message from Lukas Ertl of "Sun, 27 Jul 2003 16:43:32 +0200." <20030727163914.S698@korben.in.tern> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Jul 2003 21:14:45 +0200 From: 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 19:14:54 -0000 Lukas Ertl writes: > 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 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. > I did some playing around today with various kernels. A kernel from July 12 at 12:01 works just fine. A kernel from July 15 at 23:30 hangs (with the IRQ9 thread and g_down each using 50% of the CPU). Killing the mount with ^C leaves the (in my case) mount_msdos hung in the background and it's un-killable. It's probably stuck waiting for USB. A kernel from July 16 at 12:01 exhibits similar symptoms to the kernel from July 15. July 15 is about the time that a massive update of the USB code from NetBSD was made. I didn't try kernels from July 13 or July 14. I've observed other problems with -current: 1) mount_msdos results in a kernel panic (NULL pointer deref) 2) mounting linuxprocfs also results in a panic At the moment I'm running a world from July 15 and a kernel from July 12. --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org gj[at]denx.de