ArchWSL icon indicating copy to clipboard operation
ArchWSL copied to clipboard

Missing implementation of get_mempolicy and NUMA support

Open andradei opened this issue 1 year ago • 6 comments

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

andradei avatar Jan 19 '24 23:01 andradei

Similar question. My error message seems caused by powershell.

image

librehugohu avatar Jan 22 '24 13:01 librehugohu

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.

damienbutt avatar Jan 22 '24 21:01 damienbutt

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)

maple3142 avatar Jan 31 '24 20:01 maple3142

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

andradei avatar Feb 07 '24 14:02 andradei

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.

sirianni avatar Feb 12 '24 14:02 sirianni

numactl version 2.0.18-1 has fixed this issue by removing the warning message (https://github.com/numactl/numactl/issues/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.

maple3142 avatar Feb 13 '24 05:02 maple3142