It seems the last line of `lscpu --all --extended` may be the way to go:

https://superuser.com/questions/1735953/how-do-i-identify-which-cores-are-which-on-an-intel-hybrid-cpu

https://stackoverflow.com/questions/71122837/how-to-detect-e-cores-and-p-cores-in-linux-alder-lake-system

Thanks for the output. The problem can be explained by running a kernel that does not support the CPU. I have no idea on how to know if the kernel supports the CPU, so could you try with the newest kernel that you can easily install? Does the output change?

Attachments generated with:
 
pack() { bzip2 -9 | base64; };

lscpu | pack > lscpu_base64
cat /proc/cpuinfo | pack > cpuinfo_base64
tar c /sys/devices/system/cpu* | pack > systemcpu_base64


Associated Stackoverflow question where this issue was noticed: https://stackoverflow.com/questions/78412126/how-does-gnu-parallel-do-multiple-jobs-per-core/78421090?noredirect=1#comment138303084_78421090