[lkml]   [2003]   [Mar]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectHelp please: DVD ROM read difficulty
Currently I'm working on a DVD player fo LINUX project.
My player use libc read() function on /dev/hdc, i.e. dvd rom in my
system, to read data.
The last issue I encountered is difficulties during reading
scratched discs.
Such disc will cause the dvd rom drive get ECC error (code = 0x40)
when perorming the read action.
And the kernel will keep retrying to get the correct data from the

This is not what I want. In the worst case, the player's input
thread is trapped in the kernel trying to read data, seems even won't get
out from kernel for ever.
Then the player is stalled and will not output anything, too bad.
The read() function should report fail and return quickly when ECC
error occurs.
This is generally the require for real time data transfer, data loss
is acceptable and delay is not acceptable.

I drilled into the file /linux/drivers/ide/ide-cd.c and modified the
function cdrom_decode_status(), make it abort on senskey==HARDWARE_ERROR. It
do aborts, but the read() function do not return -1, it just return part of
the data read.
What even worse is that there is too much latency. Normally there
will be a bunch of consecutive bad blocks ( logical block on DVD,
2048Bytes), each is read according to a *request* from system cache
mechanism, and each cause a DVD drive hardware time out ( about 10 seconds.
). This is still unacceptable.

So, the target is to:
Abort the whole read() call.
Report FAIL to player. ( The player can do a jump and get to
some good position on the disc. )

For abort:
May be I can do a cdrom_end_request() on every local queue
element, thus abort to deal with all data to be read in the current read()
syscall, holding the request lock in hand and unlock it after last request
is ended.

>>>>The first question is: WILL THIS WORK, and will it work

For report FAIL:
>>>>The second questino is: HOW TO?
I did not find any way to report this when the driver start
to read data, this should be due to the kernel archeticture, IMHO.
But I am a newbie to this part of kernel, so I believe there
will be someone have the idea.

And never the less, the third question:
>>>>Any other idea on this case? Better solution is

I have to deal with this issue, and I also hope this will contribute
to the kernel, this will give very good support to players working on LINUX,
and also make the cdrom/dvdrom works much more reasonable (IMHO we can have
two types of read() on such device that may encounter real difficulty when
doing R/W, we can do more retry when data correctness is mostly concerned,
but we won't retry for ever.)

Thanks for your help!


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

 \ /
  Last update: 2005-03-22 13:33    [W:0.029 / U:8.096 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site