Hello, On 12/19/2009 08:26 AM, Alex Vandiver wrote: > On 12/03/2009 09:19 AM, Tejun Heo wrote: >> 1. Change sata_deb_timing_hotplug to sata_deb_timing_long in >> ata_piix.c::piidx_sidpr_hardreset() and see whether it solves the >> problem? > > Nope -- in fact, _three_ of the drives failed to come up once, with > this change. Wow, that's unexpected. Can you please post log of this with the debugging patch applied? >> 2. Switch the controller into ahci mode in BIOS if possible and see >> whether the problem goes away. > > Sadly, the BIOS doesn't have an option for this. Ah... that's sad. >> 3. Try kernel parameter "libata.force=nohrst" and see whether it makes >> any difference. > > I wasn't able to replicate the problem with this kernel parameter. > dmesg for such a boot is attached. Alright, thanks for verifying. >> 4. You can tell libata to reset the port by running the following command. >> >> echo "- - -" > /sys/class/scsi_host/hostN/scan >> >> N would be 0 or 1 on your configuration. Can you please run the >> above command repeatedly and see whether it triggers a reset >> failure? If so, the above will be far more convenient way to test >> than rebooting repeatedly. > > I wasn't able to get this to fail, sadly. If the boot _had_ failed, > however, this technique did bring the drive online. 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? 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
