Hello,
On Tue, Apr 01, 2014 at 09:17:35PM +0000, Biji John wrote:
> I'm running into an intermittent issue while trying to run one of
> our boards. It has the Marvell 9170 SATA controller connected to one
> of our PCIe buses. On the other side is an MSATA device. I'm running
> kernel 3.4.76. Intermittently, the link will not come up, it looks
> like the driver tries to bring the link up at 3Gbps, and then
> eventually fails, and the kernel will hang waiting for the root
> device. From doing a Google search, I noticed that this version of
> the ahci driver does not have the entries for 9170 (and 9178) in
> ahci_pci_tbl. Is this expected behavior? After adding the following
> patch, I'm seeing improvement, and am wondering how the patch might
> be helping in this regard.
>
> { PCI_DEVICE(0x1b4b, 0x9170),
> .driver_data = board_ahci_yes_fbs }, /* 88se9170 */
So, if the device doesn't have a specific entry, it'd use the default
board_ahci entry. The only difference is whether FBS is turned on for
port multipliers. The change that you made above is highly unlikely
to make any difference for initialing link init and probing. Does it
work reliably with libata.force=1.5Gbps?
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
