Linux: failed to determine memory area for node: open /sys/devices/system/node/node0/memory_failure/state: no such file or directory

[matildeY]

Failed to get topologyNodes return error
failed to determine memory area for node: open /sys/devices/system/node/node0/memory_failure/state: no such file or directory

1- since latest linux kernel there is a new directory called "memory_failure" that matches pattern defined in function memoryTotalPhysicalBytesFromPath and makes it failed.

2- is it possible to call "memTotalPhysicalBytes" instead of "memoryTotalPhysicalBytesFromPath" in function "AreaForNode" which contains a fallback function to the syslog approach ?

[jaypipes]

Hi @matildeY! Thanks for submitting this bug report. Do you think that the fix for a related bug will resolve this issue? I'm planning on cutting a ghw release with that fix today (was waiting on a couple other PRs to merge first). If you could pull the latest main branch and check on your system whether the issue still appears that would be super helpful. Thank you!

[matildeY]

hi, thanks for your answer, before submitting this bug i've tried with the main branch and the error is still present.

The memoryTotalUsableBytesFromPath call is ok and does not return error

[jaypipes]

hi, thanks for your answer, before submitting this bug i've tried with the main branch and the error is still present.

The memoryTotalUsableBytesFromPath call is ok and does not return error

OK, thank you for verifying that @matildeY! I will push a fix ASAP.

[asiffer]

Hi! I got the same warning when calling ghw.GPU :
WARNING: failed to determine memory area for node: open /sys/devices/system/node/node0/memory_failure/state: no such file or directory
(it is hidden when I use the ghw.WithDisableWarnings() option)

[jaypipes]

Hi! I got the same warning when calling ghw.GPU : WARNING: failed to determine memory area for node: open /sys/devices/system/node/node0/memory_failure/state: no such file or directory (it is hidden when I use the ghw.WithDisableWarnings() option)

Hi @asiffer! What version of ghw are you using? I believe I fixed that issue but have not yet cut a new release of ghw that includes it.

[asiffer]

Thanks @jaypipes for your quick response!
v0.10.0 in my go.mod file

[jaypipes]

@asiffer I just cut a new release: https://github.com/jaypipes/ghw/releases/tag/v0.11.0

Wait a bit for Go mod/packaging to publish the new package and then update your go.mod. Should be good to go after that! :)

[asiffer]

Awesome 🤩 Thanks a lot!

[ffromani]

@asiffer @matildeY
Hi! could you please kindly confirm version v0.11.0 fixes your issues, so we can close this bug? Thanks!

[asiffer]

Yes the last version fixed it 👍🏻 Thanks again