public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Sweetman <safemode@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: audio cd writing causes massive swap and crash
Date: Sat, 17 Jul 2004 16:00:13 -0400	[thread overview]
Message-ID: <40F9854D.2000408@comcast.net> (raw)

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 
the box to crash before finishing the cd.  CPU usage during the write is 
very low, but the feeling of lagginess begins after the first few tracks 
(and as the memory begins to be sucked away).   I've used both cdrecord 
from cdrtools in debian and from the site and both have the same 
behavior.  I dont know how i'd go about finding out what the problem is, 
so far I've coastered over 10 cds trying different ways of burning an 
audio cd but it appears that burnfree, speed have nothing to do with the 
problem. 

Here's some drive info if it helps. 

Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
Device type    : Removable CD-ROM
Version        : 0
Response Format: 1
Vendor_info    : 'PLEXTOR '
Identifikation : 'DVDR   PX-712A  '
Revision       : '1.01'
Device seems to be: Generic mmc2 DVD-R/DVD-RW.
cdrecord: This version of cdrecord does not include DVD-R/DVD-RW support 
code.
cdrecord: See /usr/share/doc/cdrecord/README.DVD.Debian for details on 
DVD support.
Using generic SCSI-3/mmc   CD-R/CD-RW driver (mmc_cdr).
Driver flags   : MMC-3 SWABAUDIO BURNFREE VARIREC FORCESPEED SPEEDREAD 
SINGLESESSION HIDECDR
Supported modes: TAO PACKET SAO SAO/R96P SAO/R96R RAW/R16 RAW/R96P RAW/R96R


now in cdrecord i use the option -swab not sure if that counters the 
driver flags or what, either way I doubt it would be causing this problem. 

the drive by the way is mmc4 compliant, so it's weird that it says mmc2.
any more info that's needed just tell me.


             reply	other threads:[~2004-07-17 20:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-17 20:00 Ed Sweetman [this message]
2004-07-17 19:34 ` audio cd writing causes massive swap and crash Andrew Morton
2004-07-19  0:07   ` Chris Wedgwood
2004-07-17 20:41 ` bert hubert
2004-07-18  7:19 ` Jens Axboe
2004-07-19 12:12   ` Ed Sweetman
2004-07-19 20:26     ` Ed Sweetman
2004-07-22  4:41       ` Ed Sweetman
2004-07-22 12:54         ` Jens Axboe
2004-07-22 20:44           ` Martin Schlemmer
2004-07-22 23:30             ` Ed Sweetman
2004-07-22 21:40               ` Jens Axboe
2004-07-24 17:56               ` Ed Sweetman

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=40F9854D.2000408@comcast.net \
    --to=safemode@comcast.net \
    --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