I have tried to rip several audio CDs with a selection of applications, but have primarily used Sound Juicer (0.5.7 from portage). Most times I have done this, the HDD light will stay solid on about half way through the rip, and I get the following messages written to syslog: Jan 26 19:21:46 lappy hdc: packet command error: status=0x51 { DriveReady SeekComplete Error } Jan 26 19:21:46 lappy hdc: packet command error: error=0x30 Jan 26 19:21:46 lappy ATAPI device hdc: Jan 26 19:21:46 lappy Error: Medium error -- (Sense key=0x03) Jan 26 19:21:46 lappy (reserved error code) -- (asc=0x02, ascq=0x00) Jan 26 19:21:46 lappy The failed "Read CD" packet command was: Jan 26 19:21:46 lappy "be 04 00 03 a7 35 00 00 08 f8 00 00 00 00 00 00 " hdc is my CD-ROM drive - this message is repeated continuously until sound-juicer is killed. I am using gentoo-dev-sources-2.6.1 and can provide my .config or any other information on request. Reproducible: Always Steps to Reproduce: 1. Start sound-juicer and begin ripping a CD. 2. Check /var/log/messages once things stop and the HDD light glows. Actual Results: Had to kill sound-juicer to recover. CD ripping failed. Expected Results: Ripped the CD(s) successfully. System uname: 2.6.1-gentoo i686 Intel(R) Pentium(R) M processor 1300MHz Gentoo Base System version 1.4.3.10 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -funroll-loops -pipe -mno-sse2" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -funroll-loops -pipe -mno-sse2" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.uk.gentoo.org/gentoo-portage" USE="X apm arts avi berkdb cdr crypt cups encode esd foomaticdb gdbm gif gnome gpm gtk gtk2 imlib java jpeg libg++ libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python quicktime readline samba sdl slang spell ssl svga tcltk tcpd truetype vim-with-x x86 xml2 xmms xv zlib"
Interestingly, with DMA disabled for the CD-ROM drive it still hangs, but without the HDD light lit solid.
sounds like a flaky cdrom ... not much can be done about it in userspace i used to have a laptop where the cdrom would spin down in the middle of reading it ... was a pain to install linux off a cd ;)
I'm certain there isn't a problem with the CD-ROM or CD-ROM drive. This works fine under gentoo-sources-2.4.22-r5, so it must be related to gentoo-dev-sources-2.6.1. I have yet to try with the unpatched development-sources-2.6.1.
well it's kernel related at any rate ;)
I have some good and some bad news. First the good news, Greg isn't nuts. I get those same type of errors messages. However, there is a bit of bad news. First off, while I get the errors, It doesn't actually slop anything on my system from working. I can still rip CD's and play DVD's but my kernel logs are totally full of errors. I have tried turning multi-mode by default on and off in the kernel and it has no effect on the error message except with it on I can't rip CD's or watch DVD's. I have also tried with 2.6.0 kernels, 2.6.1 kernels, and the rc kernels for 2.6.2 and it still doesn't work. Doesn't matter if they are gentoo-dev kernels or kernels from kernel.org. I have also booted slackware 9.1 and had the same issues. So it is not a Gentoo problem but a kernel problem. I sent messages to the kernel mailing list and if I hear anything I will let you know Greg. Anyway, I guess my point in all this is to say it doesn't appear to be a Gentoo bug. And further more, try messing with the multimode setting, perhaps it'll restore your ability to have a working system. It is under the Devices Drivers/ATA stuff in the kernel.
Just checked my kernel ATA settings. I have multimode enabled which in the help is the suggested setting relating to the error message I receive. Thanks for the additional info John.
Closing this, as it's an upstream bug and it has already been reported on lkml.
