Recent 2.6 kernels can't read an entire ATAPI CD or DVD
Hi, Jens -
I'm having trouble reading a DVD or CD image from an ATAPI drive that identifies itself as a 'LITEON DVD-ROM LTD163D'. This is with vanilla 2.6.7 on a system running Fedora Core 2.
Regardless of what I do, I get the same errors:
Jul 27 21:18:30 camp4 kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error }
Jul 27 21:18:30 camp4 kernel: hdc: command error: error=0x54
Jul 27 21:18:30 camp4 kernel: end_request: I/O error, dev hdc, sector 837264
Jul 27 21:18:30 camp4 kernel: Buffer I/O error on device hdc, logical block 104658I have ide-cd compiled as a module. This occurs whether or not ide-cd is loaded (I don't have ide-scsi enabled), and whether or not I have DMA turned on.
I don't believe there is anything wrong with the drive, as it used to work OK on 2.4, 2.5, and early 2.6 kernels, and I believe the media to be fine, as the disk in question plays back on a Mac and a DVD player.
Googling for "error=0x54", I see a lot of reports of this kind of problem, but never with any resolutions, so I'm stumped. Is there any information I can give you that would help?
Thanks,
<b
Quoted 17 lines · Bryan O'Sullivan
Hi, Jens -
I'm having trouble reading a DVD or CD image from an ATAPI drive that identifies itself as a 'LITEON DVD-ROM LTD163D'. This is with vanilla 2.6.7 on a system running Fedora Core 2.
Regardless of what I do, I get the same errors:
Jul 27 21:18:30 camp4 kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Jul 27 21:18:30 camp4 kernel: hdc: command error: error=0x54 Jul 27 21:18:30 camp4 kernel: end_request: I/O error, dev hdc, sector 837264 Jul 27 21:18:30 camp4 kernel: Buffer I/O error on device hdc, logical block 104658I have ide-cd compiled as a module. This occurs whether or not ide-cd is loaded (I don't have ide-scsi enabled), and whether or not I have DMA turned on.
Quoted 7 lines
I don't believe there is anything wrong with the drive, as it used to work OK on 2.4, 2.5, and early 2.6 kernels, and I believe the media to be fine, as the disk in question plays back on a Mac and a DVD player.
Googling for "error=0x54", I see a lot of reports of this kind of problem, but never with any resolutions, so I'm stumped. Is there any information I can give you that would help?
When does this happen - during kernel load, or during run of init scripts?
Signature · 1 line
Jens Axboe
yeah i get this kind of error in my logs as well from my liteon dvd-rom at home. thats like 6 months old and happened on fc2 when i had that installed on it. haven't noticed anything on mandrake 10 (the current distro i use at home) with 2.6.7.
i got the same error on my old notebook, a compaq presario... that was prior to the drive being sent to that big junk yard in the sky. i forget what model that was. but i was running then... rh9.
hope this bit helps guys resolve this.
-cocoy
Quoted 34 lines · Jens Axboe
Quoted 17 lines · Bryan O'Sullivan
Hi, Jens -
I'm having trouble reading a DVD or CD image from an ATAPI drive that identifies itself as a 'LITEON DVD-ROM LTD163D'. This is with vanilla 2.6.7 on a system running Fedora Core 2.
Regardless of what I do, I get the same errors:
Jul 27 21:18:30 camp4 kernel: hdc: command error: status=0x51 { DriveReady SeekComplete Error } Jul 27 21:18:30 camp4 kernel: hdc: command error: error=0x54 Jul 27 21:18:30 camp4 kernel: end_request: I/O error, dev hdc, sector 837264 Jul 27 21:18:30 camp4 kernel: Buffer I/O error on device hdc, logical block 104658I have ide-cd compiled as a module. This occurs whether or not ide-cd is loaded (I don't have ide-scsi enabled), and whether or not I have DMA turned on.
Quoted 7 lines
I don't believe there is anything wrong with the drive, as it used to work OK on 2.4, 2.5, and early 2.6 kernels, and I believe the media to be fine, as the disk in question plays back on a Mac and a DVD player.
Googling for "error=0x54", I see a lot of reports of this kind of problem, but never with any resolutions, so I'm stumped. Is there any information I can give you that would help?
When does this happen - during kernel load, or during run of init scripts?
--
Jens Axboe
Quoted 6 lines
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
Quoted 10 lines · Edward Angelo Dayao
yeah i get this kind of error in my logs as well from my liteon dvd-rom at home. thats like 6 months old and happened on fc2 when i had that installed on it. haven't noticed anything on mandrake 10 (the current distro i use at home) with 2.6.7.
i got the same error on my old notebook, a compaq presario... that was prior to the drive being sent to that big junk yard in the sky. i forget what model that was. but i was running then... rh9.
hope this bit helps guys resolve this.
(dont top post!)
Sounds like something fc2 is doing, I'd suggest filing a bug report with them.
Signature · 1 line
Jens Axboe
Quoted 10 lines · Jens Axboe
Quoted 9 lines · Edward Angelo Dayao
yeah i get this kind of error in my logs as well from my liteon dvd-rom at home. thats like 6 months old and happened on fc2 when i had that installed on it. haven't noticed anything on mandrake 10 (the current distro i use at home) with 2.6.7.
i got the same error on my old notebook, a compaq presario... that was prior to the drive being sent to that big junk yard in the sky. i forget what model that was. but i was running then... rh9.
Quoted 6 lines
Quoted 1 line
hope this bit helps guys resolve this.
(dont top post!)
Sounds like something fc2 is doing, I'd suggest filing a bug report with them.
Curious. The relevant code should match mainline 1:1 there unless I'm mistaken. Arjan ?
Dave
Quoted 13 lines · Dave Jones
Quoted 12 lines · Jens Axboe
Quoted 10 lines · Edward Angelo Dayao
yeah i get this kind of error in my logs as well from my liteon dvd-rom at home. thats like 6 months old and happened on fc2 when i had that installed on it. haven't noticed anything on mandrake 10 (the current distro i use at home) with 2.6.7.
i got the same error on my old notebook, a compaq presario... that was prior to the drive being sent to that big junk yard in the sky. i forget what model that was. but i was running then... rh9.
hope this bit helps guys resolve this.
Quoted 7 lines
Quoted 4 lines
(dont top post!)
Sounds like something fc2 is doing, I'd suggest filing a bug report with them.
Curious. The relevant code should match mainline 1:1 there unless I'm mistaken. Arjan ?
we don't patch the ide layer, ide-cd or isofs... so really curious.
Quoted 16 lines · Arjan van de Ven
Quoted 15 lines · Dave Jones
Quoted 14 lines · Jens Axboe
Quoted 10 lines · Edward Angelo Dayao
yeah i get this kind of error in my logs as well from my liteon dvd-rom at home. thats like 6 months old and happened on fc2 when i had that installed on it. haven't noticed anything on mandrake 10 (the current distro i use at home) with 2.6.7.
i got the same error on my old notebook, a compaq presario... that was prior to the drive being sent to that big junk yard in the sky. i forget what model that was. but i was running then... rh9.
hope this bit helps guys resolve this.
(dont top post!)
Quoted 7 lines
Quoted 5 lines
Quoted 2 lines
Sounds like something fc2 is doing, I'd suggest filing a bug report with them.
Curious. The relevant code should match mainline 1:1 there unless I'm mistaken. Arjan ?
we don't patch the ide layer, ide-cd or isofs... so really curious.
I meant that something from userspace is triggering these errors, it's not necessarily a kernel issue.
Signature · 1 line
Jens Axboe
Quoted 20 lines · Jens Axboe
Quoted 19 lines · Arjan van de Ven
Quoted 18 lines · Dave Jones
Quoted 16 lines · Jens Axboe
Quoted 10 lines · Edward Angelo Dayao
yeah i get this kind of error in my logs as well from my liteon dvd-rom at home. thats like 6 months old and happened on fc2 when i had that installed on it. haven't noticed anything on mandrake 10 (the current distro i use at home) with 2.6.7.
i got the same error on my old notebook, a compaq presario... that was prior to the drive being sent to that big junk yard in the sky. i forget what model that was. but i was running then... rh9.
hope this bit helps guys resolve this.
(dont top post!)
Sounds like something fc2 is doing, I'd suggest filing a bug report with them.
Quoted 7 lines
Quoted 4 lines
Quoted 2 lines
Curious. The relevant code should match mainline 1:1 there unless I'm mistaken. Arjan ?
we don't patch the ide layer, ide-cd or isofs... so really curious.
I meant that something from userspace is triggering these errors, it's not necessarily a kernel issue.
Sorry, I mixed up two different threads. On this thread, I agree it's probably a kernel issue. Can you check what capacity isosize gives you on the device, and what /proc/ide/hdc/capacity tells you?
Signature · 1 line
Jens Axboe
Quoted 3 lines · Jens Axboe
On this thread, I agree it's
probably a kernel issue. Can you check what capacity isosize gives you on the device, and what/proc/ide/hdc/capacitytells you?
This is a basically unpatched 2.6.7 kernel:
~ # uname -a
Linux abcd.serpentine.com 2.6.7-1.1791-up #1 Sat Jul 10 14:22:15 PDT 2004 i686 athlon i386 GNU/Linux
~ # isosize /dev/hdc
8164939776
~ # cat /proc/ide/hdc/capacity
15947148
<b
Quoted 12 lines · Bryan O'Sullivan
Quoted 3 lines · Jens Axboe
On this thread, I agree it's
probably a kernel issue. Can you check what capacity isosize gives you on the device, and what/proc/ide/hdc/capacitytells you?This is a basically unpatched 2.6.7 kernel:
~ # uname -a
Linux abcd.serpentine.com 2.6.7-1.1791-up #1 Sat Jul 10 14:22:15 PDT 2004 i686 athlon i386 GNU/Linux
Quoted 5 lines
~ # isosize
/dev/hdc
8164939776~ # cat
/proc/ide/hdc/capacity
15947148
Looks pretty perfect, maybe it's read-ahead screwing it up. Try if setting hdparm -a0 /dev/hdc makes a difference.
Signature · 1 line
Jens Axboe
Quoted 2 lines · Jens Axboe
Looks pretty perfect, maybe it's read-ahead screwing it up. Try if setting hdparm -a0
/dev/hdcmakes a difference.
I am seeing similar errors[1] on later 2.6, too, with about 50% of my audio CD collection. Some work, some do not. I see no pattern.
Already tried disabling read-ahead, does not matter. Also tried a different drive.
Robert Love
[1]
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54end_request: I/O error, dev hdc, sector 8
Buffer I/O error on device hdc, logical block 1
...
Quoted 10 lines · Robert Love
Quoted 2 lines · Jens Axboe
Looks pretty perfect, maybe it's read-ahead screwing it up. Try if setting hdparm -a0
/dev/hdcmakes a difference.I am seeing similar errors[1] on later 2.6, too, with about 50% of my audio CD collection. Some work, some do not. I see no pattern.
Already tried disabling read-ahead, does not matter. Also tried a different drive.
read-ahead doesn't matter on ripping audio, just for fs work.
The audio problems might be fixed in 2.6.8-rc1-mm1 + the bounce patch posted a few times (unfortunately 2.6.8-rc2-mm1 drops the patch for some reason).
Quoted 7 lines
Robert Love
[1]
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54end_request: I/O error, dev hdc, sector 8
Buffer I/O error on device hdc, logical block 1
So this happens during ripping, or? The problem with the errors like the above is that they don't indicate a specific problem. I can't just look at the error and see what causes it, it could be a million things.
Signature · 1 line
Jens Axboe
Quoted 1 line · Jens Axboe
read-ahead doesn't matter on ripping audio, just for fs work.
This isn't ripping, just playing.
Quoted 3 lines
The audio problems might be fixed in 2.6.8-rc1-mm1 + the bounce patch posted a few times (unfortunately 2.6.8-rc2-mm1 drops the patch for some reason).
Yah, I will retest with 2.6.8-rc2-mm1.
Quoted 7 lines
Quoted 5 lines
[1]
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54end_request: I/O error, dev hdc, sector 8
Buffer I/O error on device hdc, logical block 1So this happens during ripping, or?
During playback. Or any poking of the drive whatsoever, actually.
There will be multiple errors on different blocks, until ultimately IDE times out and does an ATAPI reset.
Quoted 3 lines
The problem with the errors like the above is that they don't indicate a specific problem. I can't just look at the error and see what causes it, it could be a million things.
I know :P
Robert Love
Quoted 5 lines · Robert Love
Quoted 1 line · Jens Axboe
read-ahead doesn't matter on ripping audio, just for fs work.
This isn't ripping, just playing.
Strange, something else must be accessing the drive at the same time.
Quoted 5 lines
Quoted 3 lines
The audio problems might be fixed in 2.6.8-rc1-mm1 + the bounce patch posted a few times (unfortunately 2.6.8-rc2-mm1 drops the patch for some reason).
Yah, I will retest with 2.6.8-rc2-mm1.
If it's just playback, don't bother.
Quoted 6 lines
Quoted 6 lines
Quoted 5 lines
[1]
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54end_request: I/O error, dev hdc, sector 8
Buffer I/O error on device hdc, logical block 1
Quoted 6 lines
Quoted 1 line
So this happens during ripping, or?
During playback. Or any poking of the drive whatsoever, actually.
There will be multiple errors on different blocks, until ultimately IDE times out and does an ATAPI reset.
So the question is - what else is accessing the drive?
Signature · 1 line
Jens Axboe
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jens Axboe wrote:
| On Fri, Jul 30 2004, Robert Love wrote: | |>On Fri, 2004-07-30 at 07:53 +0200, Jens Axboe wrote: |> |> |>>read-ahead doesn't matter on ripping audio, just for fs work. |> |>This isn't ripping, just playing. | | | Strange, something else must be accessing the drive at the same time. | | So the question is - what else is accessing the drive?
Could it be famd?
Prakash
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBCen4xU2n/+9+t5gRAks0AKDxR4217lUGmNNDznYZU6VOWdE1IQCeKNou 2njaepIb6XS11k/7Imj8zto=
=KRNO
-----END PGP SIGNATURE-----
Quoted 1 line · Prakash K. Cheemplavam
Could it be famd?
I thought about that, killed it, still happens.
The only "something is poking the drive" theory does not make sense, though, since it consistently works with some CD's and not others.
Robert Love
Quoted 8 lines · Robert Love
Quoted 1 line · Prakash K. Cheemplavam
Could it be famd?
I thought about that, killed it, still happens.
The only "something is poking the drive" theory does not make sense, though, since it consistently works with some CD's and not others.
Well, your io error doesn't correlate that story :-)
But I'm just puzzled. I guess I could re-rip my entire CD collection and see what happens here.
Signature · 1 line
Jens Axboe
Quoted 1 line · Jens Axboe
Strange, something else must be accessing the drive at the same time.
Don't see anything.
Quoted 1 line
If it's just playback, don't bother.
Did not work anyhow.
Quoted 1 line
So the question is - what else is accessing the drive?
Nothing but the CD player - it is doing CDDB, though, so that is where the reads are coming from.
It works/fails consistently - for example, I have one CD that never works and one CD that does, as if the CD is physically damaged. Works elsewhere, though.
Robert Love
Quoted 5 lines · Robert Love
Quoted 1 line · Jens Axboe
Strange, something else must be accessing the drive at the same time.
Don't see anything.
There must be something if you have the buffer io errors and matching sector number.
Quoted 8 lines
Quoted 1 line
If it's just playback, don't bother.
Did not work anyhow.
Quoted 1 line
So the question is - what else is accessing the drive?
Nothing but the CD player - it is doing CDDB, though, so that is where the reads are coming from.
CDDB lookups don't generate io to the drive (apart from that it already grabbed to show you the toc).
Quoted 3 lines
It works/fails consistently - for example, I have one CD that never works and one CD that does, as if the CD is physically damaged. Works elsewhere, though.
And the CD that never works, is that consistent across different drives?
Signature · 1 line
Jens Axboe
Quoted 1 line · Jens Axboe
And the CD that never works, is that consistent across different drives?
Yes. So in this machine I have two drives (a CD-RW and a DVD-ROM) and the same disk works in neither.
I think I should do a binary search backward to find where it started failing.
Robert Love
Quoted 1 line · Jens Axboe
read-ahead doesn't matter on ripping audio, just for fs work.
When I tried using dd with readahead off, I got the same error almost immediately, instead of after a number of seconds. In other words, it made the problem worse.
<b
Quoted 13 lines · Dave Jones
Quoted 12 lines · Jens Axboe
Quoted 10 lines · Edward Angelo Dayao
yeah i get this kind of error in my logs as well from my liteon dvd-rom at home. thats like 6 months old and happened on fc2 when i had that installed on it. haven't noticed anything on mandrake 10 (the current distro i use at home) with 2.6.7.
i got the same error on my old notebook, a compaq presario... that was prior to the drive being sent to that big junk yard in the sky. i forget what model that was. but i was running then... rh9.
hope this bit helps guys resolve this.
Quoted 7 lines
Quoted 4 lines
(dont top post!)
Sounds like something fc2 is doing, I'd suggest filing a bug report with them.
Curious. The relevant code should match mainline 1:1 there unless I'm mistaken. Arjan ?
I'm having similar problems running vanilla 2.6.7 with Debian-amd64 on an
Athlon 64 using a Philips DVDR824P. It refuses to read some of my dvd+r discs to the end, while some may even refuse to mount. In both cases the errors are of the "attempting to access beyond end of device" type.
Interestingly the same discs on my laptop with 2.6.7 and an LG GCA-4040N dvd+rw writer read fine. After some time (and some cd burns later) one of the discs which used to give errors on the Philips writer started to read fine again, which left me a bit confused.
Sorry for not being too detailed about system configuration at this time. If
you have interest in this, I can give more detailed system info and try to report as soon as this happens again with the exact error messages. Unfortunately I have not yet managed to create a test iso image or similar which would reproduce the problem reliably, but I can add that something similar also happenned with cdroms.
Best regards
Claudio