Open kartheekgottipati opened 1 year ago
I'm having the same issue
I am having the same issue, torch version 2.1.0
any update?
I believe the issue is with onnxruntime itself and is still not resolved. I'm going to try x86 for now.
In some sense of the word it’s an expected behavior: lambda runtime doesn’t want to leak hardware details to hosted processes, so cpuinfo fails to initialize, but PyTorch crash should be fixed
Is any SLA for solving this bug? Issue was opened more than year ago. @soumith, @apaszke, @suo, could you please help?
Also problematic in restricted build environments (like Nix) that don't expose /sys/devices/system/cpu/{possible,present}
to prevent packages from relying on the specific hardware configuration of the build system.
Any update?
AWS Lambda Arm64 pytorch 2.0.0
when running pytorch on aws lambda with pytorch 2.0.0 on arm64 i am getting the following error
[WARNING] 2023-04-10T23:55:34.026Z RUNNING WITH 1 threads Error in cpuinfo: failed to parse the list of possible processors in /sys/devices/system/cpu/possible Error in cpuinfo: failed to parse the list of present processors in /sys/devices/system/cpu/present Error in cpuinfo: failed to parse both lists of possible and present processors terminate called after throwing an instance of 'c10::Error' what(): [enforce fail at ThreadPool.cc:44] cpuinfo_initialize(). cpuinfo initialization failed frame #0: c10::ThrowEnforceNotMet(char const, int, char const, std::string const&, void const) + 0x50 (0xffff70e7ca90 in /var/task/torch/lib/libc10.so) frame #1: c10::ThrowEnforceNotMet(char const, int, char const, char const, void const*) + 0x50 (0xffff70e7cc30 in /var/task/torch/lib/libc10.so) frame #2: + 0x2c8cc78 (0xffff73b6ac78 in /var/task/torch/lib/libtorch_cpu.so)
frame #3: + 0x2c8fb64 (0xffff73b6db64 in /var/task/torch/lib/libtorch_cpu.so)
frame #4: at::set_num_threads(int) + 0x2c (0xffff71bc12bc in /var/task/torch/lib/libtorch_cpu.so)
frame #5: + 0x58d698 (0xffff7980f698 in /var/task/torch/lib/libtorch_python.so)