DVD+-R[W] regression in 2.6.12/13
Hello together,
with my machine, an
"hdparm -I /dev/dvdrecorder" leads to the output:
/dev/dvdrecorder:
HDIO_DRIVE_CMD(identify) failed: Input/output error
The kernel tells me:
[4296893.262000] hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
[4296893.262000] hdd: drive_cmd: error=0x04 { AbortedCommand }
[4296893.262000] ide: failed opcode was: 0xecThis happens with 2.6.12 and 2.6.13. DMA works fine, though. And burning CDs/DVDs seems to work fine, too.
The same hdparm command to a "normal" CD or DVD ROM drive (no writer) does not produces any error messages, though.
So what does this strange opcode do, and why does it fail in the latest kernels?
/dev/dvdrecorder is a Plextor 708A, the error also occurs with a Plextor 716A.
Best regards
Oliver
Signature · 19 lines
The problem with engineers is that they tend to cheat in order to get
results.
The problem with mathematicians is that they tend to work on toy
problems in order to get results.
The problem with program verifiers is that they tend to cheat at toy
problems in order to get results.
--
__
________________________________________creating IT solutions
Dr. Oliver Tennert
Senior Solutions Engineer
CAx Professional Services
science + computing ag
phone +49(0)7071 9457-598 Hagellocher Weg 71-75
fax +49(0)7071 9457-411 D-72070 Tuebingen, Germany
[email protected] www.science-computing.deQuoted 11 lines · Oliver Tennert
"hdparm -I
/dev/dvdrecorder" leads to the output:
/dev/dvdrecorder:
HDIO_DRIVE_CMD(identify)failed: Input/output errorThe kernel tells me:
[4296893.262000] hdd: drive_cmd: status=0x51 { DriveReady SeekComplete Error } [4296893.262000] hdd: drive_cmd: error=0x04 { AbortedCommand } [4296893.262000] ide: failed opcode was: 0xec
Those messages are "normal" for an ATAPI drive.
hdparm first tries the IDENTIFY opcode (0xec), and if that fails (above) it then tries the PACKET_IDENTIFY opcode (0xa1), which should work for ATAPI.
I'm not sure why the "failed: Input/output error" (-EIO) result is being returned from the ATA layer in this case. Driver bug, most likely.
Cheers
Oh, you *should* be able to get the results you are looking for (hdparm -I) by trying it this way:
hdparm --Istdin </proc/ide/hdd/identify
Cheers
Quoted 6 lines · Mark Lord
Oh, you *should* be able to get the results you are looking for (hdparm -I) by trying it this way:
hdparm --Istdin </proc/ide/hdd/identifyCheers
Oh yes, you are right! It works. But what is the reason behind this new behaviour?
Best regards
Oliver
Signature · 14 lines
I used to work in a fire hydrant factory. You couldn't park anywhere
near the place.
-- Steven Wright
--
__
________________________________________creating IT solutions
Dr. Oliver Tennert
Senior Solutions Engineer
CAx Professional Services
science + computing ag
phone +49(0)7071 9457-598 Hagellocher Weg 71-75
fax +49(0)7071 9457-411 D-72070 Tuebingen, Germany
[email protected] www.science-computing.deQuoted 2 lines · Mark Lord
I'm not sure why the "failed: Input/output error" (
-EIO) result is being returned from the ATA layer in this case. Driver bug, most likely.
Because the command failed an error was reported back instead of success status/info.
Alan
Quoted 7 lines · Alan Cox
Quoted 2 lines · Mark Lord
I'm not sure why the "failed: Input/output error" (
-EIO) result is being returned from the ATA layer in this case. Driver bug, most likely.Because the command failed an error was reported back instead of success status/info.
Well, yes, that's -EIO, as expected from the IDENTIFY command. But the PACKET_IDENTIFY should not be failing on the ATAPI drive.
-ml