From: Karl Vogel <karl.vogel@seagha.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8.1+patches: Still a memory leak with cdrecord
Date: Fri, 27 Aug 2004 14:09:57 +0000 (UTC) [thread overview]
Message-ID: <Xns9552A4ACE4078gmovkeb@80.91.224.252> (raw)
In-Reply-To: <412F27C1.6030100@bio.ifi.lmu.de>
Frank Steiner <fsteiner-mail@bio.ifi.lmu.de> wrote in
news:412F27C1.6030100@bio.ifi.lmu.de:
> I'm not able to really track the problem down, because it is not
> permanent. PCs that were leaking yesterday, went fine this morning
> for the first 2-3 CDs, then started leaking again. Another PC
> that was leaking first, is now burning CDs without problems. All
> that with DMA always off for all the burners. I've also one
> PC that is always burning CDs without any leak (and they
> are all running the same kernel and have the same distribution/
> packet selection installed...).
>
> I've no idea what's causing that flip-flop between leaking/non-leaking
> behaviour, but some bug is still there. What can I do to provide
> useful debugging information?
>
> Following is the output of the oom killer.
I'm not sure, but this sounds a bit similar to a problem I am seeing. Are
you by any chance using the CFQ scheduler?! (elevator=cfq) If so, give
elevator=as or elevator=deadline a go.
The problem I'm seeing is that processes that allocate large amounts of
memory, are OOM killed or cause swap storms.
-- http://thread.gmane.org/gmane.linux.kernel/228156
next prev parent reply other threads:[~2004-08-27 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 12:23 Frank Steiner
2004-08-27 14:09 ` Karl Vogel [this message]
2004-08-27 14:33 ` Frank Steiner
2004-08-27 15:41 ` Karl Vogel
2004-08-30 8:57 ` Frank Steiner
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=Xns9552A4ACE4078gmovkeb@80.91.224.252 \
--to=karl.vogel@seagha.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®