Hello, The warning message seems suspicious. I'll look into it. Wu Fengguang wrote: ... > [ 5986.864611] ata1.00: qc timeout (cmd 0xec) > [ 5987.153668] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) > [ 5987.159861] ata1.00: revalidation failed (errno=-5) > [ 5987.164854] ata1: hard resetting link > [ 5987.500647] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) > [ 5997.508508] ata1.00: qc timeout (cmd 0xec) > [ 5997.512720] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) > [ 5997.518913] ata1.00: revalidation failed (errno=-5) > [ 5997.523893] ata1: limiting SATA link speed to 1.5 Gbps > [ 5997.529149] ata1: hard resetting link > [ 5997.860516] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) > [ 6027.868126] ata1.00: qc timeout (cmd 0xec) > [ 6027.872339] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x4) > [ 6027.878530] ata1.00: revalidation failed (errno=-5) > [ 6027.883507] ata1.00: disabled > [ 6027.886603] ata1: hard resetting link > [ 6028.220134] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) > [ 6028.226450] ata1: EH complete > [ 6028.229748] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK > [ 6028.237583] Restarting system. > [ 6028.240745] machine restart But the above failures seem to indicate that IRQ delivery went out the window during shutdown before ATA shuts down properly. I don't think this is something caused by libata proper. Would it possible for you to bisect the problem? Thanks. -- 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
