Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964840AbWAWGS1 (ORCPT ); Mon, 23 Jan 2006 01:18:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964839AbWAWGS1 (ORCPT ); Mon, 23 Jan 2006 01:18:27 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:51625 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S964836AbWAWGS0 (ORCPT ); Mon, 23 Jan 2006 01:18:26 -0500 Subject: Re: memory leak in scsi_cmd_cache 2.6.15 From: Arjan van de Ven To: Ariel Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org In-Reply-To: References: <1137917798.3328.2.camel@laptopd505.fenrus.org> <1137918044.3328.6.camel@laptopd505.fenrus.org> <1137956841.3328.36.camel@laptopd505.fenrus.org> Content-Type: text/plain Date: Mon, 23 Jan 2006 07:18:18 +0100 Message-Id: <1137997104.2977.7.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1204 Lines: 31 On Sun, 2006-01-22 at 21:14 -0500, Ariel wrote: > On Sun, 22 Jan 2006, Arjan van de Ven wrote: > >>> On Sun, 2006-01-22 at 09:16 +0100, Arjan van de Ven wrote: > >>>> On Sat, 2006-01-21 at 21:13 -0500, Ariel wrote: > > >>>>> I have a memory leak in scsi_cmd_cache. > > >>>> does this happen without the binary nvidia driver too? (it appears > >>>> you're using that). That's a good datapoint to have if so... > > > please repeat this without nvidia ever being loaded. Just having a > > module loaded before can already cause corruption that ripples through > > later, so just unloading is not enough to get a clean result. > > I rebooted without nvidia or vmware ever being loaded and got a > leak of 1.12KB/s. So I think we can rule that out. great > > A commonality I'm noticing is SATA. SATA had a big update in this > version, so perhaps that's where to start looking. I wonder if it can be narrowed even more, like to the exact chipset driver? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/