From: John McGowan <jmcgowan@inch.com>
To: linux-kernel@vger.kernel.org
Subject: kernel 2.6.8.1: memory leak? cdrecord problem?
Date: Sat, 21 Aug 2004 13:26:46 -0400 [thread overview]
Message-ID: <20040821172646.GA8781@localhost.localdomain> (raw)
KERNEL 2.6.8.1: Memory leak? CDrecord problem?
-----------------------------------
KERNEL 2.6.7: compiled cdrecord.
Works fine. Burns data disks fine.
Burns audio disks fine.
UPGRADED TO KERNEL 2.6.8.1 (using the patches):
Used version of cdrecord compiled under 2.7
Burns data disks fine.
I have 256 Meg RAM (and 500+ Meg swap).
Burning a 400+Meg wav file to audio CD (40+minute
radio show) causes, after 130-180Meg have been
burned (depending on what I am running):
OUT OF MEMORY: closing down atd
and memory keeps being used up:
OUT OF MEMORY: closing down cupsd
OUT OF MEMORY: closing down crond
(etc.)
If I am lucky, cdrecord gets closed down before
something critical gets killed.
Often I am unlucky.
UNDER KERNEL 2.6.8.1:
Recompiled cdrecord under 2.6.8.1.
Burns data disks fine.
Burning a 400+ Meg wav file to audio CD causes:
OUT OF MEMORY: closing down atd
OUT OF MEMORY: closing down cupsd
OUT OF MEMORY: closing down crond
(etc.)
(Fedora Core1; kernel upgraded to (now) 2.6.7
(I went back to 2.6.7 so I could
burn audio CDs)
Using Pioneer DVD burner with ATAPI
(dev=ATAPI:0,0,0 in cdrecord) interface.)
next reply other threads:[~2004-08-21 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 17:26 John McGowan [this message]
2004-08-21 17:44 ` kernel 2.6.8.1: memory leak? cdrecord problem? Diego Calleja
2004-08-22 3:35 ` Con Kolivas
2004-08-26 11:57 ` Frank Steiner
2004-08-26 12:34 ` 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=20040821172646.GA8781@localhost.localdomain \
--to=jmcgowan@inch.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