Bug 125112 - ripping of audio CDs fails
ripping of audio CDs fails
Status: CLOSED DUPLICATE of bug 124567
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2004-06-02 15:52 EDT by Christoph Lorenz
Modified: 2007-11-30 17:10 EST (History)
0 users

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

Attachments (Terms of Use)

  None (edit)
Description Christoph Lorenz 2004-06-02 15:52:32 EDT
Description of problem:

When you rip a audio cd (e.g. with cdparanoia), after some seconds
(probably at a scratch on the CD - the exact position is not
reproducable), ripping stops and the kernel gives the following error
message: "dropping to single frame dma".
From that time on, ripping only rips total silence. The only way, to
fix this, is to reboot(!).
This happens with a stock (unmodified!) Fedora Kernel

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

How reproducible:

Steps to Reproduce:
1. cdparanoia -X -- 1 rip.wav
2. after some time, cdparanoia exists with the following error:
   outputting to rip.wav

   (== PROGRESS == [                 V            *| 045541 00 ] ==
8-X * ==)   
   Removing aborted file: rip.wav

3. dmesg gives the following message:
   cdrom: dropping to single frame dma
4. rip again - rip.wav will now contain 100% silence. At full track

Actual results:
   no audio ripped. only total silence.

Expected results:
   no silent audio files ripped

Additional info:
   this error did not occur on Fedora Core 1 with Kernel 2.4
   The cdrom and the audio CD are 100% OK
Comment 1 Jef Spaleta 2004-06-22 17:33:25 EDT

*** This bug has been marked as a duplicate of 124567 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:03:56 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.