mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeffrey J. Kosowsky" <jeff.kosowsky@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: XCdroast/cdrecord crashes kernel 2.4.18 when mastering on the fly
Date: Mon, 9 Sep 2002 14:15:34 -0400	[thread overview]
Message-ID: <15740.58694.753733.167242@surgeon.pretender> (raw)


  When backing up a partition on the fly, XCdroast/cdrecord crashed (which is
  forgiveable) but it also crashed my Linux system (which is
  not). System and consoles were totally unresponsive, requiring a
  dreaded unclean reboot.

  Joerg schilling (maintainer of cdrecord) suggests problem is with Linux
  kernel and not with 'cdrecord'
  
  Any thoughts on what might be going on?
  
  Note that mastering-on-the-fly seemed to work OK if I just backed up a
  couple of very large tar files, while the crashes seem to occur when
  backing up a partition with multiple files. This difference is
  explained perhaps   by the extra overload of mastering multiple
  small files vs. a few large tar files.
  
  My system setup is as follows:
  * Brand new 24x10x40 Hi-Val CDR
  * CD recording software
    cdrtools-cdda2wav-1.11a23-1.i386.rpm
    cdrtools-mkisofs-1.11a23-1.i386.rpm
    cdrtools-cdrecord-1.11a23-1.i386.rpm  
    cdrtools-devel-1.11a23-1.i386.rpm
    xcdroast-0.98alpha10-1.i386.rpm
  * Relatively pristine RH 7.3 running kernel 2.4.18
  * System hardware is a bit old and slow (Pentium 200 MHz Overdrive
  in an old P100 Intel Aladding/Zappa PCI Motherboard)

  Even with the older system hardware, I would hope that we could get
  Xcdroast/cdrecord to at least die gracefully if things are too slow
  to master on-the-fly.

  Thanks,
  Jeff

                 reply	other threads:[~2002-09-09 18:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=15740.58694.753733.167242@surgeon.pretender \
    --to=jeff.kosowsky@verizon.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
all inboxes | Powered by JetHome®