You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was observed that, on CPUs that are made offline using echo 0 > /sys/devices/system/cpu/cpuX/online, the topology directory does not contain information related to core_id and physical_package_id.
Due to the missing file, a related message WARNING: failed to read int from file: open /sys/devices/system/cpu/cpuX/topology/physical_package_id: no such file or directory is raised, and a similar behaviour is also observed if the core_id file is missing too.
In the case of a large compute node, this may lead to plenty of warnings printed along with other information if many CPUs are offline.
One such instance which was observed on the system is
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu10/topology/physical_package_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu10/topology/core_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu11/topology/physical_package_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu11/topology/core_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu12/topology/physical_package_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu12/topology/core_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu13/topology/physical_package_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu13/topology/core_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu14/topology/physical_package_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu14/topology/core_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu15/topology/physical_package_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu15/topology/core_id: no such file or directory
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpu16/topology/physical_package_id: no such file or directory
... - From cpu8 to cpu64.
This can be overcome by checking the online file in the cpuX directory for the bit 1 before proceeding to access the physical_package_id/core_id file.
The text was updated successfully, but these errors were encountered:
It was observed that, on CPUs that are made offline using
echo 0 > /sys/devices/system/cpu/cpuX/online
, thetopology
directory does not contain information related to core_id and physical_package_id.Due to the missing file, a related message
WARNING: failed to read int from file: open /sys/devices/system/cpu/cpuX/topology/physical_package_id: no such file or directory
is raised, and a similar behaviour is also observed if thecore_id
file is missing too.In the case of a large compute node, this may lead to plenty of warnings printed along with other information if many CPUs are offline.
One such instance which was observed on the system is
This can be overcome by checking the
online
file in thecpuX
directory for the bit1
before proceeding to access the physical_package_id/core_id file.The text was updated successfully, but these errors were encountered: