On Wed, Mar 10, 2010 at 5:01 PM, Tejun Heo <tj@xxxxxxxxxx> wrote: > Hello, > > On 03/11/2010 09:53 AM, Robert Hancock wrote: >> That doesn't sound like a great solution. I'd think that the speed >> limiting should be reset upon disabling the device so that we start over >> at 3Gbps again when you reconnect.. > > libata EH already does that. It resets the speed limit mask after the > device is disabled and when the *next* reset happens on device > hotplug, the highest speed will be applied. It's just that there > usually is no need to do an extra reset right after disabling a > device. > > Does 1.5Gbps work at all on those marvell controllers? It's *very* > strange to miss hotplug under 1.5Gbps. Those signals are OOB and > don't even follow the usual signal frequency. 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. -Justin -- 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
