sam song wrote: > [USI]: ata pass through(16) cdb: 85 0b 06 00 41 00 00 00 00 00 00 00 00 e0 > fd 00 > [<unknown opcode>: 85 0b 06 00 41 00 00 00 00 00 00 00 00 e0 fd 00 ] > scsi_status=0x2, host_status=0x0, driver_status=0x8 > info=0x1 duration=8184280 milliseconds [--snip--] > ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen > ata2.00: cmd fd/41:00:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 33280 out > res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) > ata2: port is slow to respond, please be patient (Status 0xd0) > ata2: device not ready (errno=-16), forcing hardreset > ata2: soft resetting port > ata2.00: configured for UDMA/133 > ata2: EH complete > sd 2:0:0:0: [sdb] 1953525168 512-byte hardware sectors (1000205 MB) > sd 2:0:0:0: [sdb] Write Protect is off > sd 2:0:0:0: [sdb] Mode Sense: 00 3a 00 00 > sd 2:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA Hmmm... It's timeout. How long does the command take? It's a bit weird because 36000s but the reported command duration is 136s. How long did the command take actually? -- tejun - 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
