From: Bjorn Helgaas <helgaas@kernel.org>
To: deloptes <emanoil.kotsev@deloptes.org>
Cc: linux-pci@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Sathya Prakash Veerichetty <sathya.prakash@broadcom.com>
Subject: Re: SSD SATA 3.3 and Broadcom / LSI SAS1068E PCI-Express Fusion-MPT SAS
Date: Tue, 15 Aug 2023 12:49:42 -0500 [thread overview]
Message-ID: <20230815174942.GA211975@bhelgaas> (raw)
In-Reply-To: <ubedo7$151n$1@ciao.gmane.io>
On Tue, Aug 15, 2023 at 01:35:35AM +0200, deloptes wrote:
> Bjorn Helgaas wrote:
>
> > I don't know why that would be. Are there any hints in the dmesg log?
> > Can you collect the complete dmesg log with the old drives and again
> > with the new SSDs so we can compare them? I assume you have good
> > cables? I assume the same cables worked at 3.0 Gb/s with the old
> > drives.
> >
> > I would *expect* that SATA r3.3 would be completely backwards
> > compatible, so since mptsas worked just fine at 3.0 Gb/s with the old
> > SATA r3.0 drives, it should also work just fine at 3.0 Gb/s with the
> > new SATA r3.3 drives. But I have no actual knowledge about that.
>
> Thank you for your answer. I am also confused and couldn't think of any
> meaningful reason. This is why I allowed myself to bother you.
>
> I did not change anything - wiring or such. The server has 12 disk bays on
> the front. Old disks were pulled out and new disks were inserted into the
> bays.
>
> You (probably much knowable in this matters than me) also assume negotiation
> should result in 3.0Gb/s. And if I understand correctly it should be not a
> driver issue.
>
> The only difference I could find out for now is that Rev3.3 introduced PWDIS
> on Pin 3. To check if the cables provide wiring on P3 I should disassemble
> the server, but I can do this in September :/ and it is a lot of effort.
>
> I am attaching a portion of the log and dmesg with the relevant information.
> I see that ASPM is disabled by default (could it be related to P3?).
ASPM is a PCIe feature that applies to the PCIe Links between 00:02.0
and 01:00.0 (the first 1068E) and 00:15.0 and 08:00.0 (the second
1068E).
PWDIS is a feature on the SATA cables between the SAS1068E adapters
and the SSDs.
PWDIS/P3 should not be related to ASPM. I assume you're referring to
the "disabling ASPM on pre-1.1 PCIe device" message. That should
happen with both the old r3.0 HDDs and the new r3.3 SSDs.
I wish I had some good ideas for you, but I don't know anything about
the SATA side. I googled for "1068 ssd sata 1.5 gb/s" and found a few
hints about system firmware, LSI firmware, etc, but nothing concrete.
I think some controllers have a BIOS setup user interface; have you
poked around in there?
Bjorn
next prev parent reply other threads:[~2023-08-15 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <uba6vj$10n6$1@ciao.gmane.io>
2023-08-14 16:20 ` SSD SATA 3.3 and Broadcom / LSI SAS1068E PCI-Express Fusion-MPT SAS Bjorn Helgaas
2023-08-14 23:35 ` deloptes
2023-08-15 14:45 ` Sathya Prakash Veerichetty
2023-08-15 17:49 ` Bjorn Helgaas [this message]
[not found] <ubgv7c$43t$1@ciao.gmane.io>
2023-08-15 23:15 ` Bjorn Helgaas
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=20230815174942.GA211975@bhelgaas \
--to=helgaas@kernel.org \
--cc=emanoil.kotsev@deloptes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sathya.prakash@broadcom.com \
/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