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

Missing implementation of get_mempolicy and NUMA support #344

Open
andradei opened this issue Jan 19, 2024 · 6 comments
Open

Missing implementation of get_mempolicy and NUMA support #344

andradei opened this issue Jan 19, 2024 · 6 comments

Comments

@andradei
Copy link

andradei commented Jan 19, 2024

ps command uncovers the lack of the C method get_mempolicy in the system.

So the error message on the screenshot below appears everytime ps is ran. If another program uses get_mempolicy internally, it will display the same error.

To Reproduce
Run ps command

Expected behavior
Don't show error:

get_mempolicy: Function not implemented

Screenshots
image

Enviroment:

  • Microsoft Windows [Version 10.0.22621.3007]
  • Webroot
  • WSL2
  • ArchWSL 20.10.16.0
  • ArchWSL Installer type: scoop install extras/archwsl
  • Launcher version: 22020900

Additional Info

Found this discussion that seems relevant: https://unix.stackexchange.com/questions/575470/numactl-this-system-does-not-support-numa-policy

@librehugohu
Copy link

librehugohu commented Jan 22, 2024

Similar question. My error message seems caused by powershell.

image

@damienbutt
Copy link

I am also getting this on all of my Arch installs.

For me, it seems to be the eval "$(fnm env --use-on-cd)" call at the end of my .zshrc. This is for Fast Node Manager.

If I comment that line out the problem goes away.

@maple3142
Copy link

I temporarily solved this by downgrading numactl to 2.0.16-1 and prevent it from upgrading. (Add numactl to IgnorePkg in /etc/pacman.conf)

@andradei
Copy link
Author

andradei commented Feb 7, 2024

So is this something that will "solve itself" when ps, fnm and others get updated to support newer versions on numactl?

@sirianni
Copy link

So is this something that will "solve itself" when ps, fnm and others get updated to support newer versions on numactl?

No. I think the issue is that the kernel for ArchWSL does not have NUMA enabled.

@maple3142
Copy link

maple3142 commented Feb 13, 2024

numactl version 2.0.18-1 has fixed this issue by removing the warning message (numactl/numactl#212), so it is fine to unpin it and do an upgrade normally.

No. I think the issue is that the kernel for ArchWSL does not have NUMA enabled.

But ArchWSL doesn't provide an kernel at all. The default kernel used in WSL2 is compiled and provided by Microsoft, and they don't have NUMA enabled by default.

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

5 participants