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: <alpine.DEB.2.21.2512071431560.49654@angie.orcam.me.uk>
Date: Sun, 7 Dec 2025 14:40:28 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: René Rebe <rene@...ctco.de>
cc: John Paul Adrian Glaubitz <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:

> I love my quirky Sgi MIPS64 Octane and O2 also very much, but fact is: those
> systems had not only special proprietary high speed xbow interconnects, but also
> very glitchy PCI bridges that already barely work to start with.
> 
> Also that just one modern Loongson system might work, does not mean all the
> history of MIPS(64) system will be okay.

 Obviously, but then the individual problematic systems/chips need to be 
blacklisted rather than the whole MIPS port.

> That being said I did not yet found an issue on old x86 systems with the 2015
> Year check removed to d3hot those more than mainstream currently does.

 Well, x86 is special in that the kernel has to interact with the firmware 
(BIOS/ACPI/whatever) that has traditionally had its own quirks even where 
the hardware itself is sane.

  Maciej

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ