From: Praveen Murali <pmurali@logicube.com>
To: linux-scsi@vger.kernel.org, dan.j.williams@intel.com,
JBottomley@Parallels.com
Subject: Re: eSATA Drive Detection issues on mvsas
Date: Tue, 15 Oct 2013 17:15:55 -0700 [thread overview]
Message-ID: <525DDABB.2040906@logicube.com> (raw)
In-Reply-To: <525C89D3.5090008@logicube.com>
Dan/James,
Can you please take a look at this and let me know if I am at the
right place? Or point me in the right direction? As I understand, this
deost not look like an mvsas driver issue.
Thanks,
Praveen
On 10/14/2013 05:18 PM, Praveen Murali wrote:
> Hi,
> I have couple of external drives (Western Digital and Seagate) that
> have an eSATA interface. My Linux box with a Marvell HBA (9445)
> running Ubuntu 12.04 with 3.2.48 kernel doest not seem to detect the
> drive. I tried with the latest upstream kernel and it behaves the
> same. But both the drives detect fine if I enter the mvsas BIOS during
> bootup. So I have hooked up a SATA analyzer and this is what I found
> - When I tried to detect the drives in the mvsas BIOS, all the ATA
> commands that the bios issues have the port multiplier byte set to 0.
> - If I bootup my Linux system and then connect the drives, the first
> IDENTIFY command has the port multiplier set to 0 (this one is
> successful) and the subsequent IDENTIFY command has port multiplier
> set to 1 (this one fails).
> - If I connect any other SATA drives I have to the HBA, all the ATA
> commands have port multiplier set to 1 but they detects and work fine.
>
> Just to rule out the port-multiplier possibility I changed the
> following line in drivers/scsi/libsas/sas_ata.c - fucntion
> sas_ata_qc_issue()
>
> ata_tf_to_fis(&qc->tf, 1, 0, (u8*)&task->ata_task.fis);
>
> to
>
> ata_tf_to_fis(&qc->tf, 0, 0, (u8*)&task->ata_task.fis);
>
> now all my drives seem to detect just fine. I believe, the eSATA
> interface on these external drives is a port multiplier, which is why
> the command fails. Also, the normal drives ignore this field thats why
> they work fine with port multiplier being set to either 0 or 1.
>
> Question(s): Are my above assumtions correct? If so, what is the
> reasoning behind setting the port multiplier to 1 by default in libsas
> layer?
>
> Thanks,
> Praveen
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-10-16 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 0:18 eSATA Drive Detection issues on mvsas Praveen Murali
2013-10-16 0:15 ` Praveen Murali [this message]
2013-10-16 1:11 ` Dan Williams
2013-10-16 17:28 ` Praveen Murali
2013-10-17 19:24 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525DDABB.2040906@logicube.com \
--to=pmurali@logicube.com \
--cc=JBottomley@Parallels.com \
--cc=dan.j.williams@intel.com \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.