Thanks, in that case of only kernel <5.15 being truly affected that means Jammy and onwards are working (that was released with 5.15). So we would first think we are looking at Focal and older, which are all in ESM mostly getting only security fixes these days. But as you said this isn't a full system, but EKS as also seen on 5.10.245-241.978.amzn2.aarch64 not being an Ubuntu kernel.
Even not being an Ubuntu kernel we'd like to avoid this to crash if Ubuntu is run in EKS, and it might therefore make sense to fix it despite not being our kernel. For testing that would mean we could maybe boot a focal system (kernel 5.4) and see it it crashes there as-is. Or if it still needs a HW platform underneath that truly has massive NUMA attributes. Next - test if it can be reproduced with e.g. a noble on a focal kernel without complex Numa setup P.S. and a happy new year too ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2136104 Title: numactl gives "Invalid argument" error when trying to set a node for memory using membind To manage notifications about this bug go to: https://bugs.launchpad.net/appmajix/+bug/2136104/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
