linux-kernel - Re: [PATCH] PCI: mvebu: Use devm_request_irq() for registering interrupt handler

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: <CAEzXK1qwHf5no6B2eCX1U7NGe-BoJYFLTHPkbM=_XpgrMAE2dw@mail.gmail.com>
Date: Sun, 9 Mar 2025 23:10:58 +0000
From: Luís Mendes <luis.p.mendes@...il.com>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Marc Zyngier <maz@...nel.org>, Pali Rohár <pali@...nel.org>, 
	Bjorn Helgaas <bhelgaas@...gle.com>, Thomas Petazzoni <thomas.petazzoni@...tlin.com>, 
	Lorenzo Pieralisi <lorenzo.pieralisi@....com>, Rob Herring <robh@...nel.org>, 
	Krzysztof Wilczyński <kw@...ux.com>, 
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] PCI: mvebu: Use devm_request_irq() for registering
 interrupt handler

Sorry for the delay, but last week was a busy work week and I had to
struggle to package Linux kernel 6.14-rc5 because it fails to
cross-compile... it tries to use target compiler flags with the host
compiler. I ended up compiling the kernel in a mvebu armhf machine.
Also I noticed that some hash algos are failing.

All logs presented were obtained from a SolidRun A388 ClearFog Base,
if more detailed PCI logs are needed I have the other machine, the
Armada Duo that has 2 PCIe slots and handles an AMD RX 550 GPU. Just
let me know.

- Complete dmesg log, booted with "pci=nomsi"  is available here:
https://pastebin.com/wDj0NGFN
- Complete output of "sudo lspci -vv" is available here:
https://pastebin.com/f4yHRhLr
- Contents of /proc/interrupts is available here: https://pastebin.com/ejDUuhbJ
- Output of "grep -r . /proc/irq/" is available here:
https://pastebin.com/4jvFBBhy

Let me know if more information is needed.

On Mon, Mar 3, 2025 at 8:21 PM Bjorn Helgaas <helgaas@...nel.org> wrote:
>
> On Sat, Mar 01, 2025 at 07:49:23PM +0000, Luís Mendes wrote:
> > ... I would like to offer my help for testing the patches with your
> > guidance.
> >
> > ... In any way, long story short I've read in some threads about
> > mvebu that PCIe is broken, and I say that it is not, the secret to
> > have PCIe working is to use a good u-boot bootloader. Many recent
> > u-boot versions cause the PCIe not to work on boot and I haven't
> > figured out why yet. In fact my A388 systems are working with the
> > amdgpu driver and an AMD Polaris, a RX 550 with 4GB VRAM. I have
> > been succesfully using PCIe with this old u-boot version:
> > https://github.com/SolidRun/u-boot-armada38x repo and branch
> > u-boot-2013.01-15t1-clearfog.
>
> Glad to hear that.  Making this work with more versions of u-boot
> would be great, and maybe we can make progress on that eventually.
>
> For right now, I want to try to make progress on Pali's patches.  I'm
> pretty much in the dark as far as mvebu and IRQ details, but it might
> help enlighten me if you could collect these:
>
>   - complete dmesg log, booted with "pci=nomsi"
>   - complete output of "sudo lspci -vv"
>   - contents of /proc/interrupts
>   - output of "grep -r . /proc/irq/"
>
> For now just pick one of your systems, probably the solidrun one since
> that sounds like one that other folks might have.
>
> Bjorn