Hi, me: > > Else we could repeat the old experiment which i made > > with a user on the debburn-devel list. > > It resulted in this error > > 5 1A 00 PARAMETER LIST LENGTH ERROR > > when any mode page was sent. Joe MacDonald: > That was the list of steps you sent yesterday?
I learned from your remote experiment with the empty tray on Linux that the drive gives no hint of an unusual length of mode page 05h. > > > Date: Mon, 10 Sep 2007 13:12:24 -0400 This here inquired the mode page 05h from the drive: Executing 'mode sense g1' command on Bus 0 Target 0, Lun 0 timeout 40s CDB: 5A 00 05 00 00 00 00 00 3C 00 cmd finished after 0.001s timeout 40s Mode Sense Data 00 3A 41 00 00 00 00 00 05 32 61 04 08 10 00 00 00 00 00 00 00 00 00 96 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 I also believe to see the failed attempts to set that mode page for testing the available write modes. Search for: "CDB: 55 10 00 00 00 00 00 00 3C" Executing 'mode select g1' command on Bus 0 Target 0, Lun 0 timeout 40s CDB: 55 10 00 00 00 00 00 00 3C 00 cdrecord: Input/output error. mode select g1: scsi sendcmd: no error CDB: 55 10 00 00 00 00 00 00 3C 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 55 00 00 0C 1A 00 00 00 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x1A Qual 0x00 (parameter list length error) Fru 0x0 Sense flags: Blk 0 (not valid) resid: 60 cmd finished after 0.003s timeout 40s We don't see the mode page itself, but the Parameter List Length 3Ch in byte 7+8 of the CDB would match a page length of 32h which is typical for mode page 05h and also is the replied length above. We see several of these calls. All fail with Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x1A Qual 0x00 (parameter list length error) Fru 0x0 The same was experienced by cdrskin a few months ago. So i would say the symptoms are stable and reproducible on several individual systems. So the bug is ripe to be shown to the kernel people. > Ubuntu ships wodim and most of my testing has been post-wodim-removal. I am quite sure that you will see the same failing commands in a trace of wodim. My first encounter with the problem was on debburn-devel list about wodim. Option -V should work with wodim too. I am looking forward in great hope to your further activities in this case. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
