[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.2108160027350.45958@angie.orcam.me.uk>
Date: Tue, 17 Aug 2021 00:30:39 +0200 (CEST)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Nikolai Zhubr <zhubr.2@...il.com>
cc: Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
"H. Peter Anvin" <hpa@...or.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
Paolo Bonzini <pbonzini@...hat.com>,
Sean Christopherson <seanjc@...gle.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wanpeng Li <wanpengli@...cent.com>,
Jim Mattson <jmattson@...gle.com>,
Joerg Roedel <joro@...tes.org>, x86@...nel.org,
linux-pci@...r.kernel.org, linux-pm@...r.kernel.org,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/6] x86: PIRQ/ELCR-related fixes and updates
Hi Nikolai,
> > Nikolai: for your system only 1/6 and 2/6 are required, though you are
> > free to experiment with all the patches. Mind that 3/6 mechanically
> > depends on the earlier change for the SIO PIRQ router referred above. In
> > any case please use the debug patch for PCI code as well as the earlier
> > patches for your other system and send the resulting bootstrap log for
> > confirmation.
>
> Here is a new log with 1/6 and 2/6 applied:
>
> https://pastebin.com/0MgXAGtG
>
> It looks like something went a bit unexpected ("runtime IRQ mapping not
> provided by arch").
Offhand it looks like your system does not supply a PIRQ table, not at
least at the usual locations we look through. The presence of the table
is reported like:
PCI: IRQ init
PCI: Interrupt Routing Table found at 0xfde10
[...]
PCI: IRQ fixup
while your system says:
PCI: IRQ init
PCI: IRQ fixup
If you have a look through /dev/mem and see if there's a "$PIR" signature
somewhere (though not a Linux kernel area of course), then we may know for
sure.
I'm a little busy at the moment with other stuff and may not be able to
look into it properly right now. There may be no solution, not at least
an easy one. A DMI quirk is not possible, because:
DMI not present or invalid.
There is a PCI BIOS:
PCI: PCI BIOS revision 2.10 entry at 0xf6f41, last bus=0
however, so CONFIG_PCI_BIOS just might work. Please try that too, by
choosing CONFIG_PCI_GOANY or CONFIG_PCI_GOBIOS (it may break things
horribly though I imagine).
Maciej
Powered by blists - more mailing lists