linux-kernel - Re: PCI bridge window issue

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: <051199db-1c34-3e70-c028-73f850ff30f0@linux.intel.com>
Date: Tue, 2 Dec 2025 21:35:47 +0200 (EET)
From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To: René Rebe <rene@...ctco.de>
cc: glaubitz@...sik.fu-berlin.de, linux-pci@...r.kernel.org, 
    LKML <linux-kernel@...r.kernel.org>, bhelgaas@...gle.com, 
    riccardo.mottola@...ero.it
Subject: Re: PCI bridge window issue

On Tue, 2 Dec 2025, René Rebe wrote:

> Hi Ilpo,
> 
> On Tue, 2 Dec 2025 20:20:09 +0200 (EET), Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com> wrote:
> 
> > On Tue, 2 Dec 2025, René Rebe wrote:
> > 
> > > s390x. Maybe users of those want to allow list after testing? Now that
> > > I think about it I was wondering why ALSA RAD1 audio is not longer
> > > working in my Sgi Octane with the PCI window not being enabled. Would
> > > not suprise me it was some change like this, too. Should bisect next
> > 
> > Hi René,
> > 
> > Could you please send me a dmesg and contents of the /proc/iomem (taken 
> > with root right so it shows the real addresses) so I can look at this PCI 
> > bridge window issue. If you know a working kernel, having logs from 
> > working and broken case would be very helpful to easily locate the 
> > differences.
> 
> Thank you so much for offering help with that different
> issue. Sgi/Octane IP30 only went upstream some years ago. I only have
> the likewise not upstream snd-rad1 working with much older out of tree
> kernels. Thanks you for the hints, I'll try to find some time to to
> further debug this soon to bring the snd-rad1 ALSA driver upstream,
> too.

Okay, if it's an old issue, it's likely not because of the recent PCI core 
changes.

If there are "can't assign" or "no compatible bridge window" lines for 
PCI resources in the log, those happen before some endpoint driver even 
comes into picture so it could be PCI core issue so in that sense it might 
not matter if the endpoint driver is in-tree or out-of-tree as long as the 
kernel you're testing with is otherwise "new enough" to contain the recent 
changes and fixes to PCI subsystem.

-- 
 i.

> > At this point, no need to bisect as I might be able to figure it out even 
> > without pinpointing the commit. To avoid spending on issues that are 
> > already know and have a fix, please check you're not running somewhat old 
> > kernel as I've already fixed a few things that have gotten broken due to 
> > recent made PCI bridge window fitting and assignment algorithm changes.
> 
> I can not easily bisect mips64 sgi-ip30 anyway. As it was out of tree
> for 20y and the uptreamed code changed a lot during cleanup for
> merging.
> 
> Good to have a contact to look into this next.
> 
> Thanks!
> 	René
> 
>