From owner-freebsd-current@FreeBSD.ORG Thu Nov 6 08:08:35 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 9CFAB16A4CE for ; Thu, 6 Nov 2003 08:08:35 -0800 (PST) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB63D43FE5 for ; Thu, 6 Nov 2003 08:08:32 -0800 (PST) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id MUA74016 for ; Thu, 06 Nov 2003 08:08:31 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 4D10F5D07 for ; Thu, 6 Nov 2003 08:08:31 -0800 (PST) To: current@freebsd.org Date: Thu, 06 Nov 2003 08:08:31 -0800 From: "Kevin Oberman" Message-Id: <20031106160831.4D10F5D07@ptavv.es.net> Subject: Kernel memory leak in ATAPI/CAM or ATAng? 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: Thu, 06 Nov 2003 16:08:35 -0000 I have learned a bit more about the problems I have been having with the DVD drive on my T30 laptop. When I have run the drive for an extended time (like 2 or 3 hours), I invariably have my system lock up because it can't malloc kernel memory for the ATAPI/CAM or ATA device. (Usually it's both.) The only recovery seems to be to reboot the system. I suspect a memory leak because it seems to be linked to total amount of data transferred, even in multiple invocations of the program. Of course, once the kernel grabs VM, I guess it generally does not actually release it, but it should re-use the existing allocation and not keep allocating more. I posted my config and dmesg files yesterday. I have tried tuning KVM_SIZE stuff with no real success, just the loss of the ability to run with APM loaded. (This is possibly due to mis-tuning.) Any ideas on where I can look for more information? I'm going to try doing some monitoring with vmstat while running to see if I can spot anything, but I am not sure just what I am looking for. The VM system is not something I know much about, but I did read Terry Lambert's excellent message to current on KVM tuning and I'm hoping that this might help, but, if there really is a memory leak, tuning will not fix it. FWIW, this problem did not exist a few month ago prior to ATAng. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634