linux-kernel - Re: arm64: juno-r2: SSD detect failed on mainline and next

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>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250402-thistle-oxpecker-of-fragrance-d2ebb5@sudeepholla>
Date: Wed, 2 Apr 2025 17:18:19 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Naresh Kamboju <naresh.kamboju@...aro.org>
Cc: Robin Murphy <robin.murphy@....com>,
	Linux ARM <linux-arm-kernel@...ts.infradead.org>,
	Sudeep Holla <sudeep.holla@....com>, iommu@...ts.linux.dev,
	open list <linux-kernel@...r.kernel.org>,
	lkft-triage@...ts.linaro.org,
	Linux Regressions <regressions@...ts.linux.dev>,
	Lorenzo Pieralisi <lpieralisi@...nel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>, Rob Herring <robh@...nel.org>,
	Dan Carpenter <dan.carpenter@...aro.org>,
	Arnd Bergmann <arnd@...db.de>,
	Anders Roxell <anders.roxell@...aro.org>
Subject: Re: arm64: juno-r2: SSD detect failed on mainline and next

On Wed, Apr 02, 2025 at 04:34:08PM +0100, Robin Murphy wrote:
> On 31/03/2025 5:03 am, Naresh Kamboju wrote:
> > Regressions on arm64 Juno-r2 devices detect SSD tests failed on the
> > Linux next and Linux mainline.
> > 
> > First seen on the v6.14-7245-g5c2a430e8599
> >   Good: v6.14
> >   Bad: v6.14-7422-gacb4f33713b9
> 
> Sorry, I can't seem to reproduce this on my end, both today's mainline and
> acb4f33713b9 with my config, and even acb4f33713b9 with the linked LKFT
> config, all work OK on my Juno r2 (using a SATA SSD and PCIe networking).
> The only thing which stands out in your log is that PCI seems to give up
> probing and assigning resources beyond the switch downstream ports (so SATA
> and ethernet are never discovered), whereas on mine it does[2]. However that
> all happens before the first IOMMU instance probes (which conveniently is
> the PCIe one), so it's hard to imagine how that could have an effect
> anyway...
> 
> The only obvious difference is that I'm using EDK2 rather than U-Boot, so
> that's done all the PCIe configuration once already, but it doesn't seem
> like that's significant - looking back at a random older log[1], the
> on-board endpoints were still being picked up right after reconfiguring the
> switch, well before the IOMMU comes into the picture.
> 

Highly unlikely it is related to this issue, but I do see you are using
the default DTB files and not juno-*-scmi.dtb which aligns with the SCP
firmware you might be running. Just noticed SCPI timeout in the log, so
none of the power management calls will work. By default all the required
power domains must be on though.

-- 
Regards,
Sudeep