Re: DVD/CD Read Problem: cdrom_decode_status: status=0x51 {DriveReady SeekComplete Error}

Andrey Borzenkov (
Sun, 13 Jul 2003 19:51:07 +0400

> I get the following errors and an unkillable process when trying to play
> DVDs, using the latest 2.5.75:
> Jul 13 00:15:03 joehill kernel: hdc: cdrom_decode_status: status=0x51 {
DriveReady SeekComplete Error }
> Jul 13 00:15:03 joehill kernel: hdc: cdrom_decode_status:
error=0x30LastFailedSense 0x03

this is ide-cd problem. drivers/ide/ide-cd:cdrom_decode_status():

} else if ((err & ~ABRT_ERR) != 0) {
/* Go to the default handler
for other errors. */
return 1;
} else if (sense_key == MEDIUM_ERROR) {
/* No point in re-trying a zillion times on a bad
* sector... If we got here the error is not
e */
ide_dump_status (drive, "media error (bad sector)",
cdrom_end_request(drive, 0);

The above sense key is exactly MEDIUM_ERROR but driver never has chance to
stop "retring zillion times" simply because it immediately falls down into
driver->error again. So "innocent" media error results half an hour retries
and disabled DMA.

> and sometimes:
> Jul 13 00:15:03 joehill kernel: hdc: ide_intr: huh? expected NULL handler on
> This problem has been discussed several times before on this list[1], but
> no resolution or fixes that I can find.
> I don't believe this is a userspace issue. Other OS's are able to deal with
> playing video DVDs by skipping read errors quickly. There should be some
> way to tell the kernel not to keep retrying for certain (i.e., non-data)
> CD/DVDs. I can't see any possible way to do this in application space,
> though.

they are not user-space issues. Try to swap two conditions above and see what
happens. I cannot test it anymore for reason below ...


> I'm not sure why it's getting errors at all, incidentally, as this occurs
> with brand new DVDs out of the shrink wrap, and a relatively new DVD
> player (HP F2015B, manufactured by Quanta).

I just had to ditch brand new Toshiba SD-R1312 because I got exactly the same
errors on multisession CDs. Single sessions were OK but multisessions almost
never could be reas properly resulting in flood of positioning errors.

While this may be Linux bug in read-ahead handling, this drive usually had the
same problem under Windows (and even after I let it be replaced) so I guess
it is firmware problem. Some of them are just beter than other :)

So I do not have drive that readily generates these errors anymore and cannot
test this patch.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at