Likwid error in CascadeLake

[techsun]

Hi,

I am getting an error while running Likwid APIs

$likwid-setFrequencies -p

ERROR - [./src/access_client.c:access_client_read:336] Connection reset by peer. socket read failed

ERROR - [./src/frequency_cpu.c:getIntelHWP:861] Connection reset by peer. Cannot read register 0x770

$likwid-powermeter -I

ERROR - [./src/access_client.c:access_client_read:336] Connection reset by peer.

socket read failed Cannot gather values from MSR_PLATFORM_INFO

I did the following changes to BIOS settings

1. set uncore frequency to dynamic instead of keeping it maximum.

2. Enable node interleaving as it was disabled by default.

Before doing these changes, Likwid APIs were working fine. 

Can anyone tell me what could be the problem?

Thanks,

[techsun]

Here is the architecture info.

--------------------------------------------------------------------------------

CPU name:    Intel(R) Xeon(R) Gold 6242 CPU @ 2.80GHz

CPU type:    Intel Cascadelake SP processor

CPU stepping:    7

********************************************************************************

Hardware Thread Topology

********************************************************************************

Sockets:        2

Cores per socket:    16

Threads per core:    2

--------------------------------------------------------------------------------

[Sunil Singh]

I request you to look into this matter.

Thanks,

--

---
You received this message because you are subscribed to a topic in the Google Groups "likwid-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/likwid-users/LWQ-Z1DiroU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to likwid-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/likwid-users/0ea07568-8748-4643-bd21-49e4917e5167n%40googlegroups.com.

[Thomas Gruber]

Excuse me? We are offering LIKWID for fun and research. Nobody is requesting anything from us!

What does the node interleaving do? Does the system look like a single socket despite having multiple sockets/NUMA domains?

It seems the accessdaemon gets killed in its setup phase, to no communication can be established. Debugging the accessdaemon is difficult but at least rebuild LIKWID with DEBUG=true (in config.mk) and check your syslog. In general, provide the output of likwid-perfctr -C 0 -g ENERGY -V 3 hostname, then we can look at the client side.

Best,
Thomas