From: deloptes <emanoil.kotsev@deloptes.org>
To: linux-pci@vger.kernel.org
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: SSD SATA 3.3 and Broadcom / LSI SAS1068E PCI-Express Fusion-MPT SAS
Date: Wed, 16 Aug 2023 00:46:03 +0200 [thread overview]
Message-ID: <ubgv7c$43t$1@ciao.gmane.io> (raw)
In-Reply-To: 20230815174942.GA211975@bhelgaas
Bjorn Helgaas wrote:
Thank you Bjorn for answering and explaining
> 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.
>
Yes, this is what I meant. So it can be ignored as well as the ASPM.
I will check the cables, when I can get hands on the machine - just out of
curiosity.
> 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.
>
Yeah, if it were so easy, I wouldn't be bothering you.
> I think some controllers have a BIOS setup user interface; have you
> poked around in there?
I have not seen the bios of the machine for many years. I was looking
forward to plug it to a console, so that I can reboot remotely, but for
some reason it was not possible. It was may be 5y ago. I will definitely
double check this, allthough there will be nothing regarding SATA3.3 there
as these were build many years before SATA3.3 saw daylight.
As mentioned in the other posting I will attach those SSDs directly to the
mobo. There are 6 SATA ports there. I think this is the best approach.
But you know curiosity is a force you can not resist, so I still want to
know why?! :)
Thank you anyway
BR
--
FCD6 3719 0FFB F1BF 38EA 4727 5348 5F1F DCFE BCB0
next prev parent reply other threads:[~2023-08-15 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 9:15 SSD SATA 3.3 and Broadcom / LSI SAS1068E PCI-Express Fusion-MPT SAS deloptes
2023-08-14 16:20 ` Bjorn Helgaas
2023-08-14 23:35 ` deloptes
2023-08-15 14:45 ` Sathya Prakash Veerichetty
2023-08-15 22:33 ` deloptes
2023-08-15 17:49 ` Bjorn Helgaas
2023-08-15 22:46 ` deloptes [this message]
2023-08-15 23:15 ` Bjorn Helgaas
2023-09-29 15:23 ` deloptes
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='ubgv7c$43t$1@ciao.gmane.io' \
--to=emanoil.kotsev@deloptes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).