| 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
| ||
|
Date: Thu, 11 Jan 2024 09:02:41 -0500 From: Brian Masney <bmasney@...hat.com> To: Lucas Karpinski <lkarpins@...hat.com> Cc: Andy Gross <agross@...nel.org>, Bjorn Andersson <andersson@...nel.org>, Konrad Dybcio <konrad.dybcio@...aro.org>, Rob Herring <robh+dt@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>, linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v2] arm64: dts: qcom: sa8540p-ride: disable pcie2a node On Tue, Jan 09, 2024 at 10:20:50AM -0500, Lucas Karpinski wrote: > pcie2a and pcie3a both cause interrupt storms to occur. However, when > both are enabled simultaneously, the two combined interrupt storms will > lead to rcu stalls. Red Hat is the only company still using this board > and since we still need pcie3a, just disable pcie2a. > > Signed-off-by: Lucas Karpinski <lkarpins@...hat.com> Reviewed-by: Brian Masney <bmasney@...hat.com> To elaborate further: Leaving both pcie2a and pcie3a enabled will lead to rcu stalls and the board fails to boot when both are enabled. We have the latest firmware that we've been able to get from QC. Disabling one of the pcie nodes works around the boot issue. There's nothing interesting on pcie2a on the development board, and pcie3a is enabled because it has 10GB ethernet that works upstream. The interrupt storm on pcie3a can still occur on this platform, however that's a separate issue. Brian
Powered by blists - more mailing lists