From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Bjorn Helgaas <bhelgaas@google.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>
Cc: linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org,
Thomas Lendacky <Thomas.Lendacky@amd.com>,
Mario Limonciello <mario.limonciello@dell.com>
Subject: AMD Ryzen: pci 0000:00:00.2: can't derive routing for PCI INT A
Date: Thu, 28 May 2020 17:45:10 +0200 [thread overview]
Message-ID: <8579bd14-e369-1141-917b-204d20cff528@molgen.mpg.de> (raw)
Dear Linux folks,
On most (if not all) AMD Ryzen systems, including the Dell OptiPlex
5055, [1][2], Linux prints the warning below:
$ dmesg --level=warn
[ 0.871377] pci 0000:00:00.2: can't derive routing for PCI INT A
[ 0.871732] pci 0000:00:00.2: PCI INT A: not connected
[ 0.884890] PPR NX GT IA GA PC GA_vAPIC
$ more /proc/version
Linux version 5.4.39.mx64.334 (root@lol.molgen.mpg.de) (gcc version
7.5.0 (GCC)) #1 SMP Thu May 7 14:27:50 CEST 2020
pmenzel@donut:~$ dmesg | grep 'DMI:'
[ 0.000000] DMI: Dell Inc. OptiPlex 5055 Ryzen CPU/0P03DX, BIOS
1.1.20 05/31/2019
The system seems to work fine. What effect might be caused by the
missing routing information?
I assume this is a firmware issue? Can I patch the ACPI tables to
provide the correct information?
Should this indeed be an AMD AGESA issue, it be great, if somebody with
contacts at AMD could be forward this to the appropriate folks.
Kind regards,
Paul
[1]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804589
[2]: https://bugs.launchpad.net/dell-sputnik/+bug/1881121
reply other threads:[~2020-05-28 15:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8579bd14-e369-1141-917b-204d20cff528@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=Thomas.Lendacky@amd.com \
--cc=bhelgaas@google.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario.limonciello@dell.com \
--cc=rjw@rjwysocki.net \
/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;
as well as URLs for NNTP newsgroup(s).