Bug 28567 - AMD-Vi: Unable to read/write to IOMMU perf counter
Summary: AMD-Vi: Unable to read/write to IOMMU perf counter
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: 8
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-09 20:39 CET by Pe Alfa
Modified: 2021-03-23 18:04 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pe Alfa 2021-03-09 20:39:11 CET 
I just installed Mageia 8 (64 bits) in a new Lenovo Ideapad 3 (AMD Ryzen 7 4800h + nVidia GTX 1650) and this error appears at the start:

pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.

I do:
dmesg | grep -e IOMMU
[0.722808] pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
[0.724431] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
[1.392921] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>

Is it a bug? Should I fix it?

Thanks

Pepe Álvarez
Comment 1 Lewis Smith 2021-03-09 21:30:17 CET 
Thank you for the report.

Assigning to kernel team.

Assignee: bugsquad => kernel

Comment 2 Pe Alfa 2021-03-23 14:58:25 CET 
Hi!

After last update:

uname -a
Linux lenovo.pealfa.duckdns.org 5.10.25-desktop-1.mga8 #1 SMP Sat Mar 20 16:45:02 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

# dmesg | grep -e DMAR -e IOMMU
[    0.764292] pci 0000:00:00.2: AMD-Vi: IOMMU performance counters supported
[    0.767103] pci 0000:00:00.2: AMD-Vi: Found IOMMU cap 0x40
[    0.769617] perf/amd_iommu: Detected AMD IOMMU #0 (2 banks, 4 counters/bank).
[    1.442067] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel <jroedel@suse.de>

Good news?
Comment 3 Thomas Backlund 2021-03-23 18:04:56 CET 
Yep.

the fix for this landed in upstream 5.10.24

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.