From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Lord Subject: Re: Hotplug issue with Marvell 6121 Date: Wed, 10 Mar 2010 22:33:16 -0500 Message-ID: <4B98647C.6010604@teksavvy.com> References: <150c16851003091651r4ce4259v693f1310d0aa95ef@mail.gmail.com> <150c16851003101446m633ad174tc784a94e2a2a5a5b@mail.gmail.com> <4B983F08.6080701@gmail.com> <4B9840D3.7050109@kernel.org> <150c16851003101832o358a8b4aj760384020658d1fc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from ironport2-out.teksavvy.com ([206.248.154.183]:12992 "EHLO ironport2-out.pppoe.ca" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751621Ab0CKDdT (ORCPT ); Wed, 10 Mar 2010 22:33:19 -0500 In-Reply-To: <150c16851003101832o358a8b4aj760384020658d1fc@mail.gmail.com> Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: Justin Maggard Cc: Tejun Heo , Robert Hancock , linux-ide@vger.kernel.org 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