Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IIO is not returning any value #896

Open
arun2arunraj opened this issue Dec 27, 2024 · 2 comments
Open

IIO is not returning any value #896

arun2arunraj opened this issue Dec 27, 2024 · 2 comments

Comments

@arun2arunraj
Copy link

arun2arunraj commented Dec 27, 2024

hi Team,

We are getting the following error message in one of our test server. Not sure why the IIO related details are not popping up. Any help would be much appreciated.

Note. I am running PCM as a docker image. In my host machine, I could see the pci.ids file. But I cant see the pci.ids in the docker image. Should I bind the hwdata into the container to get this metrics ?

pcm-iio

Intel(r) Performance Counter Monitor ($Format:%ci ID=%h$)

This utility measures IIO information

===== Processor information =====
Linux arch_perfmon flag : yes
Hybrid processor : no
IBRS and IBPB supported : yes
STIBP supported : yes
Spec arch caps supported : yes
Max CPUID level : 27
CPU family : 6
CPU model number : 106
Number of physical cores: 64
Number of logical cores: 128
Number of online logical cores: 128
Threads (logical cores) per physical core: 2
Num sockets: 2
Physical cores per socket: 32
Last level cache slices per socket: 32
Core PMU (perfmon) version: 5
Number of core PMU generic (programmable) counters: 8
Width of generic (programmable) counters: 48 bits
Number of core PMU fixed counters: 4
Width of fixed counters: 48 bits
Nominal core frequency: 2200000000 Hz
IBRS enabled in the kernel : yes
STIBP enabled in the kernel : no
The processor is not susceptible to Rogue Data Cache Load: yes
The processor supports enhanced IBRS : yes
Package thermal spec power: 185 Watt; Package minimum power: 84 Watt; Package maximum power: 652 Watt;

INFO: Linux perf interface to program uncore PMUs is present
Socket 0: 4 memory controllers detected with total number of 8 channels. 3 UPI ports detected. 4 M2M (mesh to memory)/B2CMI blocks detected. 0 HBM M2M blocks detected. 0 EDC/HBM channels detected. 0 Home Agents detected. 3 M3UPI/B2UPI blocks detected.
Socket 1: 4 memory controllers detected with total number of 8 channels. 3 UPI ports detected. 4 M2M (mesh to memory)/B2CMI blocks detected. 0 HBM M2M blocks detected. 0 EDC/HBM channels detected. 0 Home Agents detected. 3 M3UPI/B2UPI blocks detected.
Socket 0: 1 PCU units detected. 6 IIO units detected. 6 IRP units detected. 32 CHA/CBO units detected. 0 MDF units detected. 1 UBOX units detected. 0 CXL units detected. 0 PCIE_GEN5x16 units detected. 0 PCIE_GEN5x8 units detected.
Socket 1: 1 PCU units detected. 6 IIO units detected. 6 IRP units detected. 32 CHA/CBO units detected. 0 MDF units detected. 1 UBOX units detected. 0 CXL units detected. 0 PCIE_GEN5x16 units detected. 0 PCIE_GEN5x8 units detected.
Initializing RMIDs

Detected Intel(R) Xeon(R) Gold 6338N CPU @ 2.20GHz "Intel(r) microarchitecture codename Icelake-SP" stepping 6 microcode level 0xd0003d1
/usr/share/hwdata/pci.ids file is not available. Ensure that the "hwdata" package is properly installed or download https://raw.githubusercontent.com/pciutils/pciids/master/pci.ids and copy it to the current directory.
Error info:event config file opCode-6-106.txt or /usr/local/share/pcm/opCode-6-106.txt is not available, you can try to manually copy it from PCM source package.
Event configure file have the problem and cause the program exit, please double check it!

@ogbrugge-work
Copy link
Contributor

I would assume that yes you have to make sure pcm in docker can access those files.

@rdementi
Copy link
Contributor

rdementi commented Jan 7, 2025

I think the main issue is that opCode-*.txt files are not available. Did you run "make install" inside the container to let pcm build process install opCode-*.txt files?
Not having hwdata is not a showstopper but to solve it you need to install the hwdata package inside the container.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants