William Thompson wrote:
+scsi2 : ata_piix +ata_port_schedule_eh: port EH scheduled +ata_scsi_error: ENTER +ata_port_flush_task: ENTER +ata_port_flush_task: flush #1 +ata2: ata_port_flush_task: flush #2 +ata2: ata_port_flush_task: EXIT +ata_eh_autopsy: ENTER +ata_eh_recover: ENTER +ata_eh_prep_resume: ENTER +ata_eh_prep_resume: EXIT +__ata_port_freeze: ata2 port frozen +ata_std_softreset: ENTER +ata_std_softreset: about to softreset, devmask=1 +ata_bus_softreset: ata2: bus reset via SRST +ata_dev_classify: found ATA device by sig +ata_dev_classify: unknown device +ata_std_softreset: EXIT, classes[0]=1 [1]=5 +ata_std_postreset: ENTER +ata_std_postreset: EXIT +ata_eh_thaw_port: ata2 port thawed +ata_eh_revalidate_and_attach: ENTER +ata2.00: ata_dev_read_id: ENTER, host 2, dev 0 +ata_exec_command_pio: ata2: cmd 0xEC +ata_hsm_move: ata2: protocol 2 task_state 1 (dev_stat 0x51) +ata_hsm_move: ata2: protocol 2 task_state 3 (dev_stat 0x51) +ata_port_flush_task: ENTER +ata_port_flush_task: flush #1 +ata2: ata_port_flush_task: flush #2 +ata2: ata_port_flush_task: EXIT +ata2.00: failed to IDENTIFY (I/O error, err_mask=0x1) +ata_eh_revalidate_and_attach: EXIT
.. Yep. Libata seems to be treating the ATAPI drive as ATA. Tejun, don't we have a fallback for when IDENTIFY fails? If the drive rejects it (err=0x04), then this can mean only one thing: unsupported command, so we next must try PACKET_IDENTIFY. -ml - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
