All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Eduard Bloch <blade@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: memory not released after using cdrecord/cdrdao (was: audio cd writing causes massive swap and crash)
Date: Wed, 28 Jul 2004 17:08:55 -0700	[thread overview]
Message-ID: <20040729000855.GI2334@holomorphy.com> (raw)
In-Reply-To: <20040725094605.GA18324@zombie.inka.de>

* Ed Sweetman [Sat, Jul 17 2004, 04:00:13PM]:
>> Both with 2.6.7-rc3 and 2.6.8-rc1-mm1 I get the same behavior when 
>> writing an audio cd on my plextor px-712a.  DMA is enabled and normal 
>> data cds write as expected, but audio cds will cause (at any speed) the 
>> box to start using insane amounts of swap (>150MB) and eventually cause 

On Sun, Jul 25, 2004 at 11:46:05AM +0200, Eduard Bloch wrote:
> Just FYI: we have a similar bug description in the Debian BTS, where the
> user reports that kernel does not release memory assigned to userspace
> after cdrdao or cdrecord have used it (writting in DAO mode), though he
> could not find what allocated this memory. For details:
> http://bugs.debian.org/256871 (dump attached).

Is there any way we could get a characterization of the kind of memory
that's proliferating here? e.g. could you snapshot /proc/meminfo,
/proc/slabinfo, and /proc/vmstat at regular intervals during the run?


-- wli

      parent reply	other threads:[~2004-07-29  0:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-25  9:46 memory not released after using cdrecord/cdrdao (was: audio cd writing causes massive swap and crash) Eduard Bloch
2004-07-26  1:30 ` Ed Sweetman
2004-07-26  9:10   ` OOM-killer going crazy. (was: Re: memory not released after using cdrecord/cdrdao) Jan-Frode Myklebust
2004-07-26 10:55     ` Nick Piggin
2004-07-26 11:10       ` Jan-Frode Myklebust
2004-07-26 11:43         ` OOM-killer going crazy Nick Piggin
2004-07-26 12:46           ` Jan-Frode Myklebust
2004-07-27  1:00             ` Nick Piggin
2004-07-26 13:02     ` Ed Sweetman
2004-07-27  4:19       ` Nick Piggin
2004-07-27 10:07         ` Jens Axboe
2004-07-27 13:23           ` Ed Sweetman
2004-07-27 13:30             ` Nick Piggin
2004-07-27 22:38               ` Ed Sweetman
2004-07-28  1:00                 ` Nick Piggin
2004-07-28  6:30                   ` Ed Sweetman
2004-07-28  6:45                     ` Jens Axboe
2004-07-28 12:58                       ` Ed Sweetman
2004-07-28 13:31                         ` Jens Axboe
2004-07-29  0:08 ` William Lee Irwin III [this message]

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=20040729000855.GI2334@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=blade@debian.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.