RE: 2.6.9-rc1-mm3 IDE cdrom bug

[Sid Boyce]

It seems all 2.6.9-rc1 kernels give this error ending up with the mount 
in D state, up to -bk13. Everything works fine on 2.6.8-rc4-mm1 on the 
Asus A7N8X-E, so I need to go back and find out exactly where it broke, 
I hadn't used the CDROM/DVD's in quite a while.
On the Acer 1501LCe x86_64 I get Drive Seek Incomplete errors, hdparm 
says Using DMA=1, but the mount gives a D process now, whereas it worked 
flawlessly before, suspect I may have a bad drive.
Sep  7 00:26:32 Boycie kernel: hdc: cdrom_decode_status: status=0x51 { 
DriveReady SeekComplete Error }
Sep  7 00:26:32 Boycie kernel: hdc: cdrom_decode_status: 
error=0x40LastFailedSense 0x04
Sep  7 00:26:32 Boycie kernel: hdc: command error: status=0x51 { 
DriveReady SeekComplete Error }
Sep  7 00:26:32 Boycie kernel: hdc: command error: error=0x52
Sep  7 00:26:32 Boycie kernel: ide: failed opcode was 100
Sep  7 00:26:32 Boycie kernel: end_request: I/O error, dev hdc, sector 64
Sep  7 00:26:32 Boycie kernel: Buffer I/O error on device hdc, logical 
block 8
Sep  7 00:26:32 Boycie automount[8536]: >> /dev/dvd: Input/output error
Sep  7 00:26:32 Boycie kernel: hdc: request sense failure: status=0x51 { 
DriveReady SeekComplete Error }
Sep  7 00:26:32 Boycie kernel: hdc: request sense failure: 
error=0xb0LastFailedSense 0x0b
Sep  7 00:26:32 Boycie kernel: hdc: packet command error: status=0x51 { 
DriveReady SeekComplete Error }
Sep  7 00:26:32 Boycie kernel: hdc: packet command error: error=0x40
Sep  7 00:26:32 Boycie kernel: ide: failed opcode was 100
Sep  7 00:26:32 Boycie kernel: hdc: request sense failure: status=0x51 { 
DriveReady SeekComplete Error }
Sep  7 00:26:32 Boycie kernel: hdc: request sense failure: 
error=0xb0LastFailedSense 0x0b

Regards
Sid.

--
Sid Boyce .... Hamradio G3VBV and keen Flyer
=====LINUX ONLY USED HERE=====

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/