Bug 125112

Summary: ripping of audio CDs fails
Product: [Fedora] Fedora Reporter: Christoph Lorenz <christoph_lorenz>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:03:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Christoph Lorenz 2004-06-02 19:52:32 UTC 
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):
kernel-2.6.5-1.358


How reproducible:
always


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
length!
  

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 21:33:25 UTC 

*** This bug has been marked as a duplicate of 124567 ***
Comment 2 Red Hat Bugzilla 2006-02-21 19:03:56 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.