-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[Modular CLI]: segmentation fault in WSL #1057
Comments
Encountered the same issue when updating from 0.2.1 to 0.4.0. Full stack trace:
Modular version: modular 0.2.0 (355ea9c0)
CPU specs:
Also tried uninstalling & reinstall |
Potentially related to: #1002 |
@sangshuduo - Please update to WSL2 and do a fresh install and let us know if you still see this |
C:> wsl -l -v
Sorry, it's my primary work environment so I can't do a fresh install. Please let me know if any info I can provide for you to debug. |
@smuniraj2018 I have tried to fresh installed it and this time it works fine. I didn't document my installation steps for the first installation where it crashes, but here's what I did for the second installation:
I didn't really "run" this script because this script I wrote would somehow skip the python-env installation (I'm not experienced enough to understand why), so I ran it manually, one or a few command at each time. |
inspired by #1087 (comment) I removed ~/.modular directory and installed python3.10-venv, then used "modular auth XXXX && modular install mojo" now mojo 0.4.0 is installed. |
Issue description
run the command "modular install mojo" then modular CLI segfault.
Steps to reproduce
$ modular auth mut_cbdd6b39a2564135bd0b19fab4XXXXXX && modular install mojo
loc("#M.target<triple = \22x86_64-unknown-linux\22, cpu = \22tigerlake\22, features = \22+64bit,+adx,+aes,+avx,+avx2,+avx512bitalg,+avx512bw,+avx512cd,+avx512dq,+avx512f,+avx512ifma,+avx512vbmi,+avx512vbmi2,+avx512vl,+avx512vnni,+avx512vp2intersect,+avx512vpopcntdq,+bmi,+bmi2,+clflushopt,+clwb,+cmov,+crc32,+cx16,+cx8,+f16c,+fma,+fsgsbase,+fxsr,+gfni,+invpcid,+kl,+lzcnt,+mmx,+movbe,+movdir64b,+movdiri,+pclmul,+pku,+popcnt,+prfchw,+rdpid,+rdrnd,+rdseed,+sahf,+sgx,+sha,+shstk,+sse,+sse2,+sse3,+sse4.1,+sse4.2,+ssse3,+vaes,+vpclmulqdq,+widekl,+x87,+xsave,+xsavec,+xsaveopt,+xsaves\22, data_layout = \22e-m:e-p270:32:32-p271:32:32-p272:64:64-i64:64-f80:128-n8:16:32:64-S128\22, simd_bit_width = 512>":1:50): error: duplicate or unknown struct parameter name: cpu
[7048:7048:20231014,122042.380838:ERROR file_io_posix.cc:144] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[7048:7048:20231014,122042.380892:ERROR file_io_posix.cc:144] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
Please submit a bug report to https://github.com/modularml/mojo/issues and include the crash backtrace along with all the relevant source codes.
Stack dump:
0. Program arguments: modular install mojo
#0 0x00005624bdce8bb7 (/usr/bin/modular+0x4eebb7)
#1 0x00005624bdce686e (/usr/bin/modular+0x4ec86e)
#2 0x00005624bdce927f (/usr/bin/modular+0x4ef27f)
#3 0x00007fb663b35520 (/lib/x86_64-linux-gnu/libc.so.6+0x42520)
#4 0x00005624be0a6434 (/usr/bin/modular+0x8ac434)
#5 0x00005624be0a5abf (/usr/bin/modular+0x8ababf)
#6 0x00005624bdcadc22 (/usr/bin/modular+0x4b3c22)
#7 0x00005624bdcacd75 (/usr/bin/modular+0x4b2d75)
#8 0x00005624bdcaaec3 (/usr/bin/modular+0x4b0ec3)
#9 0x00007fb663b1cd90 (/lib/x86_64-linux-gnu/libc.so.6+0x29d90)
#10 0x00007fb663b1ce40 __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x29e40)
#11 0x00005624bdcaa55e (/usr/bin/modular+0x4b055e)
Segmentation fault
Version Info
The text was updated successfully, but these errors were encountered: