From: Abhijit Paithankar <apaithan@akamai.com>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: "Prakash, Sathya" <Sathya.Prakash@lsi.com>,
Douglas Gilbert <dgilbert@interlog.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: LSISAS1068 ioerr_cnt 0x1 on clean boot up
Date: Mon, 13 Oct 2008 19:55:04 -0700 [thread overview]
Message-ID: <20081014025504.GA10518@akamai.com> (raw)
In-Reply-To: <660360F4F2570145BD872F298951B17A5C94F055@cosmail03.lsi.com>
* Moore, Eric (Eric.Moore@lsi.com) wrote:
> Abhijit - You're patch would allow page 0x19 to STP devices, which I doubt is supported either. I think you should be doing the following instead:
>
> + if (rphy->identify.device_type == SAS_END_DEVICE &&
> + (rphy->identify.target_port_protocols & SAS_PROTOCOL_SSP))
> + sas_read_port_mode_page(sdev);
Yes, thanks for pointing that out. I think it needs to be OR-ed with
SAS_PROTOCOL_SATA.
Here is the updated patch.
Signed-off-by: Abhijit Paithankar <apaitha@akamai.com>
Index: linux-2.6.27/drivers/message/fusion/mptsas.c
===================================================================
--- linux-2.6.27.orig/drivers/message/fusion/mptsas.c 2008-10-13 17:31:57.000000000 -0700
+++ linux-2.6.27/drivers/message/fusion/mptsas.c 2008-10-13 19:51:57.000000000 -0700
@@ -839,11 +839,15 @@ mptsas_sas_enclosure_pg0(MPT_ADAPTER *io
static int
mptsas_slave_configure(struct scsi_device *sdev)
{
+ struct sas_rphy *rphy;
if (sdev->channel == MPTSAS_RAID_CHANNEL)
goto out;
- sas_read_port_mode_page(sdev);
+ rphy = dev_to_rphy(sdev->sdev_target->dev.parent);
+ if (rphy->identify.device_type == SAS_END_DEVICE &&
+ !(rphy->identify.target_port_protocols & (SAS_PROTOCOL_SATA | SAS_PROTOCOL_SSP)))
+ sas_read_port_mode_page(sdev);
out:
return mptscsih_slave_configure(sdev);
next prev parent reply other threads:[~2008-10-14 3:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 1:46 LSISAS1068 ioerr_cnt 0x1 on clean boot up Abhijit Paithankar
2008-10-07 9:17 ` Prakash, Sathya
2008-10-07 23:37 ` Abhijit Paithankar
2008-10-08 9:16 ` Bernd Schubert
2008-10-08 17:47 ` Abhijit Paithankar
2008-10-08 10:52 ` Douglas Gilbert
2008-10-09 0:51 ` Abhijit Paithankar
2008-10-13 11:40 ` Prakash, Sathya
2008-10-14 0:40 ` Abhijit Paithankar
2008-10-14 2:23 ` Moore, Eric
2008-10-14 2:55 ` Abhijit Paithankar [this message]
2008-10-14 6:39 ` Prakash, Sathya
2008-10-14 17:49 ` Abhijit Paithankar
2008-10-14 18:43 ` Abhijit Paithankar
2008-10-14 18:42 ` Abhijit Paithankar
2008-10-15 6:43 ` Abhijit Paithankar
2008-10-15 22:40 ` Moore, Eric
2008-10-14 2:56 ` Abhijit Paithankar
2008-10-14 6:45 ` Prakash, Sathya
2008-10-14 15:36 ` Moore, Eric
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=20081014025504.GA10518@akamai.com \
--to=apaithan@akamai.com \
--cc=Eric.Moore@lsi.com \
--cc=Sathya.Prakash@lsi.com \
--cc=dgilbert@interlog.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox