[Bug 263469] PCI class 0x13 (instrumentation) not given a name
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 263469] PCI class 0x13 (instrumentation) not given a name"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Fri, 22 Apr 2022 14:40:43 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263469 --- Comment #1 from commit-hook@FreeBSD.org --- A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/src/commit/?id=f010b9c2b9b0a550656de8a5b5ad1469630c3e2c commit f010b9c2b9b0a550656de8a5b5ad1469630c3e2c Author: John F. Carr <email@example.com> AuthorDate: 2022-04-22 14:28:34 +0000 Commit: Stefan Eßer <se@FreeBSD.org> CommitDate: 2022-04-22 14:39:23 +0000 pci: recognize "non-essential instrumentation" devices Some AMD EPYC VCPUs generated boot message of the type: pci4: <unknown> at device 0.0 (no driver attached) These are displayed for device class 0x13 devices, e.g.: none8@pci0:130:0:0: class=0x130000 rev=0x00 hdr=0x00 vendor=0x1022 \ device=0x148a subvendor=0x1022 subdevice=0x148a vendor = 'Advanced Micro Devices, Inc. [AMD]' device = 'Starship/Matisse PCIe Dummy Function' class = non-essential instrumentation Since these devices serve no purpose (no driver attaches) I have enabled the reporting of suich devices only for verbose boots (a diversion from the patch provided in the PR). A verbose boot will now display such devices as: pci4: <non-essential instrumentation> at device 0.0 (no driver attached) PR: 263469 Reported by: firstname.lastname@example.org (John F. Carr) MFC after: 1 week sys/dev/pci/pci.c | 1 + 1 file changed, 1 insertion(+) -- You are receiving this mail because: You are the assignee for the bug.