From: Arjan van de Ven <arjan@infradead.org>
To: Ariel <askernel2615@dsgml.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: memory leak in scsi_cmd_cache 2.6.15
Date: Mon, 23 Jan 2006 07:18:18 +0100 [thread overview]
Message-ID: <1137997104.2977.7.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0601222045180.12815@pureeloreel.qftzy.pbz>
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?
next prev parent reply other threads:[~2006-01-23 6:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 2:13 memory leak in scsi_cmd_cache 2.6.15 Ariel
2006-01-22 6:58 ` Andrew Morton
2006-01-22 18:18 ` Ariel
2006-01-22 8:16 ` Arjan van de Ven
2006-01-22 8:20 ` Arjan van de Ven
2006-01-22 18:51 ` Ariel
2006-01-22 19:07 ` Arjan van de Ven
2006-01-22 19:16 ` Chase Venters
2006-01-22 19:24 ` Arjan van de Ven
2006-01-22 19:46 ` Chase Venters
2006-01-23 2:19 ` Ariel
2006-01-22 19:24 ` Chase Venters
2006-01-23 0:58 ` Jamie Heilman
2006-01-23 2:14 ` Ariel
2006-01-23 6:18 ` Arjan van de Ven [this message]
2006-01-23 6:28 ` Chase Venters
2006-01-23 6:46 ` Ariel
2006-01-23 7:25 ` Jamie Heilman
2006-01-23 8:33 ` Jens Axboe
2006-01-27 11:28 ` Jamie Heilman
2006-01-28 19:27 ` Jens Axboe
2006-01-26 18:12 ` Ariel
2006-01-27 16:23 ` Nix
2006-01-28 19:27 ` Jens Axboe
2006-01-28 19:46 ` Chase Venters
2006-01-28 21:29 ` Jens Axboe
2006-01-29 15:50 ` Pasi Kärkkäinen
2006-01-29 16:38 ` James Bottomley
2006-01-29 17:10 ` Pasi Kärkkäinen
2006-01-29 19:57 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1137997104.2977.7.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=askernel2615@dsgml.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).