public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: linux-kernel@vger.kernel.org, centaur@netmagic.net
Subject: Re: PROBLEM: 2.4.21 crashes hard running cdrecord in X.
Date: Mon, 16 Jun 2003 15:46:34 +1000	[thread overview]
Message-ID: <3EED59BA.8040104@torque.net> (raw)

Per Nystrom wrote:
 > Alright, I've really gotten it narrowed down now.
 >
 > The hard crash occurs only when magicdev is running.  I tried turning
 > off all my preferences for auto- mounting, running, and playing
 > data/audio cds in my preferences, and voila!  cdrecord works without a
 > hiccup in X too.

Per,
Interesting. My SCSI Yamaha 4416 burner also doesn't like magicdev
running during a burn by cdrecord. The effect is to lock up
burner (not the whole system). Since a device lockup leads
to an attempted device reset (and the latter is quite fragile
in the ide-scsi driver), my guess is that my Yamaha and your
Sony writer have the same firmware weakness.

Magicdev sends out a Test Unit Ready command every few seconds
and it seems some burners can't handle this while burning (or
in the final fixate stage). The simple solution is to turn off
magicdev (then your system will no longer detect CDROMs being
placed in the drive).

Doug Gilbert


             reply	other threads:[~2003-06-16  5:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-16  5:46 Douglas Gilbert [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-24 16:27 PROBLEM: 2.4.21 crashes hard running cdrecord in X Ralf Hoelzer
2003-06-24 17:15 ` Dave Bentham
2003-06-16  0:22 Per Nystrom
2003-06-16  0:55 ` Con Kolivas
2003-06-16  2:00   ` Per Nystrom
2003-06-16  2:46     ` Per Nystrom
2003-06-16  8:38       ` Roland Mas
2003-06-16 12:56       ` Jan Knutar
2003-06-16 23:46         ` Per Nystrom
2003-06-18  6:44           ` Per Nystrom
2003-06-18 17:21             ` Scott McDermott
2003-06-21 12:15   ` Alan Cox

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=3EED59BA.8040104@torque.net \
    --to=dougg@torque.net \
    --cc=centaur@netmagic.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