linux-kernel - Re: [PATCH] PCI: Fix PCI bridges not to go to D3Hot on older RISC systems

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

Message-ID: <alpine.DEB.2.21.2512071429180.49654@angie.orcam.me.uk>
Date: Sun, 7 Dec 2025 14:31:50 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: René Rebe <rene@...ctco.de>
cc: glaubitz@...sik.fu-berlin.de, linux-pci@...r.kernel.org, 
    linux-kernel@...r.kernel.org, Bjorn Helgaas <bhelgaas@...gle.com>, 
    riccardo.mottola@...ero.it
Subject: Re: [PATCH] PCI: Fix PCI bridges not to go to D3Hot on older RISC
 systems

On Sat, 6 Dec 2025, René Rebe wrote:

> > So this seems like something that needs to be keyed off perhaps the 
> > capabilities of the system controller/host bridge?  If you give me a shell 
> > recipe to trigger the issue you came across, then I can see what happens 
> > with some of my MIPS systems.  I've got a bunch of options with PCI-PCIe 
> > reverse bridges and PCIe switches I could try.
> 
> Just booting a kernel with or since a5fb3ff63287 ("PCI: Allow PCI bridges to go
> to D3Hot on all non-x86”) should be enough. The systems that fail for me do
> so instantly booting, usually earlier than later. e.g. when a storage, network or
> system controller driver initializes.

 I booted 6.18 as released last week on my Malta and saw no issues in this 
area.

  Maciej