Bug 83825 - Burning a CD using RH8.0 at runlevel 5 causes failed burn (coaster) and lots of scsi errors.
Burning a CD using RH8.0 at runlevel 5 causes failed burn (coaster) and lots ...
Status: CLOSED DUPLICATE of bug 83826
Product: Red Hat Linux
Classification: Retired
Component: magicdev (Show other bugs)
8.0
i386 Linux
high Severity high
: ---
: ---
Assigned To: Owen Taylor
David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-09 12:37 EST by Leigh Orf
Modified: 2006-02-21 13:51 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:51:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Leigh Orf 2003-02-09 12:37:54 EST
Description of problem: Burning a CD with RedHat 8.0 consistenly
fails with scsi errors due to concurrent access to /dev/scd0 by
magicdev process


Version-Release number of selected component (if applicable):


How reproducible: Log in under runlevel 5 (X). A process called
magicdev will be spawned.


Steps to Reproduce:
1. Log in at runlevel 5 (X)
1. sudo cdrecord -audio -dao dev=0,0,0 speed=4 *.wav
2. cdrecord will begin burning and will crash. many scsi errors in /var/log/messages

Actual results:


Expected results:


Additional info: If you kill magicdev this problem goes away! Magicdev
is concurrently accessing /dev/scd0 which messes up the cd burn.

As far as I can tell anyone who tries to burn a CD using RH 8.0
with the ide-scsi module should have this problem.

I am using the default 8.0 configuration except I am using the sawfish
window manager.
Comment 1 David Lawrence 2003-02-09 18:12:27 EST

*** This bug has been marked as a duplicate of 83826 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:51:40 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.