At Sun Dec 20 23:50:15 -0500 2009, Tejun Heo wrote: > Wow, that's unexpected. Can you please post log of this with the > debugging patch applied? I've only been able to replicate this once, and I didn't manage to save its dmesg, sadly. I'll see if I can get it to crop up again, though. > Hmmm... interesting. So, the boot time probing is somehow different > from probing initiated by manual scan (they both use hardreset). Can > you please post log of manual scans with debug patch applied? The output of a manual scan is: [ 255.236938] ata1.00: hard resetting link [ 255.465422] ata1.00: XXX debounce start, SStatus=123 [ 257.551239] ata1.00: XXX debounce done, SStatus=123, DET stable for 2090 msecs [ 257.551246] ata1.01: hard resetting link [ 257.780776] ata1.01: XXX debounce start, SStatus=123 [ 259.866589] ata1.01: XXX debounce done, SStatus=123, DET stable for 2090 msecs [ 260.026328] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 260.026342] ata1.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 260.087511] ata1.00: configured for UDMA/133 [ 260.127736] ata1.01: configured for UDMA/133 [ 260.127740] ata1: EH complete - Alex -- Networking -- only one letter away from not working -- 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
