public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* kernel 2.6.8.1: memory leak? cdrecord problem?
@ 2004-08-21 17:26 John McGowan
  2004-08-21 17:44 ` Diego Calleja
  0 siblings, 1 reply; 5+ messages in thread
From: John McGowan @ 2004-08-21 17:26 UTC (permalink / raw)
  To: linux-kernel

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.)

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2004-08-26 12:43 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-21 17:26 kernel 2.6.8.1: memory leak? cdrecord problem? John McGowan
2004-08-21 17:44 ` Diego Calleja
2004-08-22  3:35   ` Con Kolivas
2004-08-26 11:57     ` Frank Steiner
2004-08-26 12:34       ` Frank Steiner

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox