lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20230815231517.GA271814@bhelgaas>
Date:   Tue, 15 Aug 2023 18:15:17 -0500
From:   Bjorn Helgaas <helgaas@...nel.org>
To:     deloptes <emanoil.kotsev@...optes.org>
Cc:     linux-pci@...r.kernel.org, linux-scsi@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: SSD SATA 3.3 and Broadcom / LSI SAS1068E PCI-Express Fusion-MPT
 SAS

On Wed, Aug 16, 2023 at 12:46:03AM +0200, deloptes wrote:
> Bjorn Helgaas wrote:
> ...

> > 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.

I saw some mention about BIOS knobs that controlled the minimum
acceptable SATA link speed or something; that's the kind of thing I
wondered about.

> 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?! :)

Haha, yeah, I know!  I noticed in your response to Sathya that you're
running a 4.19.288 kernel, which is really, really old.  If it's
practical, the first thing I would try is booting a current kernel,
e.g., v6.4, on the chance that something has been fixed since v4.19.
I didn't try to compare the mptsas driver to see if it has changed
since then, so I don't know whether it's likely.

Bjorn

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ