From: Bjorn Helgaas <helgaas@kernel.org>
To: Erik Quaeghebeur <kernelbugs@equaeghe.nospammail.net>
Cc: linux-pci@vger.kernel.org
Subject: Re: [Bug 212261] New: pci 0000:00:00.2: can't derive routing for PCI INT A
Date: Sat, 13 Mar 2021 16:08:09 -0600 [thread overview]
Message-ID: <20210313220809.GA2401557@bjorn-Precision-5520> (raw)
In-Reply-To: <bug-212261-41252@https.bugzilla.kernel.org/>
On Sat, Mar 13, 2021 at 01:19:39PM +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=212261
>
> Bug ID: 212261
> Summary: pci 0000:00:00.2: can't derive routing for PCI INT A
> Product: Drivers
> Version: 2.5
> Kernel Version: 5.10.22
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: PCI
> Assignee: drivers_pci@kernel-bugs.osdl.org
> Reporter: kernelbugs@equaeghe.nospammail.net
> Regression: No
>
> I'm on a Lenovo T14 AMD, with a Ryzen 4750U. In the logs, I find
>
> pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
> pci 0000:00:00.2: can't derive routing for PCI INT A
> pci 0000:00:00.2: PCI INT A: not connected
>
> where the last two lines are warnings. Various bugreports related to this can
> be found elsewhere.
>
> I guess there is either something wrong with the hardware/firmware or with the
> kernel. I'd hope this warning can be fixed. Feel free to ask for more
> information.
Thanks for the report!
What device is 00:00.2? Does it work? If not, did it ever work,
i.e., is this a regression? If it's a regression, what's the newest
kernel you know of where it did work?
Can you please attach a complete dmesg log and output of
"sudo lspci -vvv" to the bugzilla?
Can you also add links to any related bug reports you're aware of?
Bjorn
parent reply other threads:[~2021-03-13 22:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-212261-41252@https.bugzilla.kernel.org/>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210313220809.GA2401557@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=kernelbugs@equaeghe.nospammail.net \
--cc=linux-pci@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox