On 03/10/10 21:32, Justin Maggard wrote:
It's not the 1.5Gbps that is causing the problem. It appears to be the act of changing speeds. I added "libata.force=3:1.5Gbps" to my kernel command line, and hotplugs seemed to work fine on that port (presumably due to the fact that libata EH won't change the link speed limit if it's already at 1.5Gbps). The other port on the controller still had hotplug problems. So everything seems to be pointing to the Marvell controller having problems when you change speeds.
... If it's like their non-AHCI controllers (sata_mv), then the chipset/phy could be very particular about the sequence/timing used when changing speeds. -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
