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

[Modular CLI]: Attempting to update via 'modular update mojo' segfaults #1087

Closed
MostHated opened this issue Oct 19, 2023 · 4 comments
Closed
Labels
modular-cli modular tool issues mojo-repo Tag all issues with this label

Comments

@MostHated
Copy link

MostHated commented Oct 19, 2023

Issue description

I simply attempted to run modular update mojo and receive the error below:

zsh ❯ modular update mojo
loc("#M.target<triple = \22x86_64-unknown-linux\22, cpu = \22znver4\22, features = \22+64bit,+adx,+aes,+avx,+avx2,+avx512bf16,+avx512bitalg,+avx512bw,+avx512cd,+avx512dq,+avx512f,+avx512ifma,+avx512vbmi,+avx512vbmi2,+avx512vl,+avx512vnni,+avx512vpopcntdq,+bmi,+bmi2,+clflushopt,+clwb,+clzero,+cmov,+crc32,+cx16,+cx8,+f16c,+fma,+fsgsbase,+fxsr,+gfni,+invpcid,+lzcnt,+mmx,+movbe,+mwaitx,+pclmul,+pku,+popcnt,+prfchw,+rdpid,+rdpru,+rdrnd,+rdseed,+sahf,+sha,+shstk,+sse,+sse2,+sse3,+sse4.1,+sse4.2,+sse4a,+ssse3,+vaes,+vpclmulqdq,+wbnoinvd,+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
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 update mojo
 #0 0x000055d0e69acd47 (/usr/bin/modular+0x4e8d47)
 #1 0x000055d0e69aa9fe (/usr/bin/modular+0x4e69fe)
 #2 0x000055d0e69ad40f (/usr/bin/modular+0x4e940f)
 #3 0x00007f55d9442520 (/lib/x86_64-linux-gnu/libc.so.6+0x42520)
 #4 0x000055d0e6d6d254 (/usr/bin/modular+0x8a9254)
 #5 0x000055d0e6d6c8df (/usr/bin/modular+0x8a88df)
 #6 0x000055d0e6988884 (/usr/bin/modular+0x4c4884)
 #7 0x000055d0e6987c6a (/usr/bin/modular+0x4c3c6a)
 #8 0x000055d0e696f053 (/usr/bin/modular+0x4ab053)
 #9 0x00007f55d9429d90 (/lib/x86_64-linux-gnu/libc.so.6+0x29d90)
#10 0x00007f55d9429e40 __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x29e40)
#11 0x000055d0e696e6ee (/usr/bin/modular+0x4aa6ee)
[1]    2485672 segmentation fault (core dumped)  modular update mojo

Steps to reproduce

All I attempted to do was:

  • Run modular update mojo

Version Info

  • Provide Modular CLI version by pasting the output of modular -v: modular 0.2.1 (5144fffe)
  • What OS did you install modular CLI on ?
    See system info below:
System Details
OS: Ubuntu 22.04.3 LTS x86_64
Host: X670E Taichi
Kernel: 6.4.12-060412-generic
Uptime: 2 days, 12 hours, 15 mins
Packages: 3219 (dpkg), 71 (flatpak), 27 (snap)
Shell: zsh 5.8.1
Resolution: 2560x1080
DE: GNOME 42.9
WM: Mutter
WM Theme: Adwaita
Theme: Yaru-dark [GTK2/3]
Icons: Yaru [GTK2/3]
Terminal: alacritty
CPU: AMD Ryzen 9 7950X (32) @ 4.500GHz
GPU: AMD ATI 5a:00.0 Device 164e
GPU: AMD ATI Radeon RX 6800/6800 XT / 6900 XT
Memory: 29673MiB / 63398MiB
@MostHated MostHated added the modular-cli modular tool issues label Oct 19, 2023
@jackos
Copy link
Collaborator

jackos commented Oct 19, 2023

Looks related to: #1002

@MostHated
Copy link
Author

MostHated commented Oct 19, 2023

Strange. I tried it again, just for giggles, and the output was different this time:

I see it says a dir doesn't exist. Though, it does up to a point:
/home/mosthated/.modular/crashdb/attachments exists.

zsh ❯ modular update mojo
loc("#M.target<triple = \22x86_64-unknown-linux\22, cpu = \22znver4\22, features = \22+64bit,+adx,+aes,+avx,+avx2,+avx512bf16,+avx512bitalg,+avx512bw,+avx512cd,+avx512dq,+avx512f,+avx512ifma,+avx512vbmi,+avx512vbmi2,+avx512vl,+avx512vnni,+avx512vpopcntdq,+bmi,+bmi2,+clflushopt,+clwb,+clzero,+cmov,+crc32,+cx16,+cx8,+f16c,+fma,+fsgsbase,+fxsr,+gfni,+invpcid,+lzcnt,+mmx,+movbe,+mwaitx,+pclmul,+pku,+popcnt,+prfchw,+rdpid,+rdpru,+rdrnd,+rdseed,+sahf,+sha,+shstk,+sse,+sse2,+sse3,+sse4.1,+sse4.2,+sse4a,+ssse3,+vaes,+vpclmulqdq,+wbnoinvd,+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
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 update mojo
[595007:595008:20231019,170038.267715:ERROR directory_reader_posix.cc:42] opendir /home/mosthated/.modular/crashdb/attachments/bbbf88a4-0d5b-457b-a752-70fda13c20be: No such file or directory (2)
 #0 0x00005639fd902d47 (/usr/bin/modular+0x4e8d47)
 #1 0x00005639fd9009fe (/usr/bin/modular+0x4e69fe)
 #2 0x00005639fd90340f (/usr/bin/modular+0x4e940f)
 #3 0x00007f649c242520 (/lib/x86_64-linux-gnu/libc.so.6+0x42520)
 #4 0x00005639fdcc3254 (/usr/bin/modular+0x8a9254)
 #5 0x00005639fdcc28df (/usr/bin/modular+0x8a88df)
 #6 0x00005639fd8de884 (/usr/bin/modular+0x4c4884)
 #7 0x00005639fd8ddc6a (/usr/bin/modular+0x4c3c6a)
 #8 0x00005639fd8c5053 (/usr/bin/modular+0x4ab053)
 #9 0x00007f649c229d90 (/lib/x86_64-linux-gnu/libc.so.6+0x29d90)
#10 0x00007f649c229e40 __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x29e40)
#11 0x00005639fd8c46ee (/usr/bin/modular+0x4aa6ee)
[595007:595008:20231019,170038.533963:ERROR http_transport_libcurl.cc:483] HTTP status 404
[1]    594995 segmentation fault (core dumped)  modular update mojo

I reinstalled modular, the attempted to reinstall mojo, but receive the following while doing so:

zsh ❯ modular uninstall mojo
loc("#M.target<triple = \22x86_64-unknown-linux\22, cpu = \22znver4\22, features = \22+64bit,+adx,+aes,+avx,+avx2,+avx512bf16,+avx512bitalg,+avx512bw,+avx512cd,+avx512dq,+avx512f,+avx512ifma,+avx512vbmi,+avx512vbmi2,+avx512vl,+avx512vnni,+avx512vpopcntdq,+bmi,+bmi2,+clflushopt,+clwb,+clzero,+cmov,+crc32,+cx16,+cx8,+f16c,+fma,+fsgsbase,+fxsr,+gfni,+invpcid,+lzcnt,+mmx,+movbe,+mwaitx,+pclmul,+pku,+popcnt,+prfchw,+rdpid,+rdpru,+rdrnd,+rdseed,+sahf,+sha,+shstk,+sse,+sse2,+sse3,+sse4.1,+sse4.2,+sse4a,+ssse3,+vaes,+vpclmulqdq,+wbnoinvd,+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
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 uninstall mojo
 #0 0x000055ebce764d47 (/usr/bin/modular+0x4e8d47)
 #1 0x000055ebce7629fe (/usr/bin/modular+0x4e69fe)
 #2 0x000055ebce76540f (/usr/bin/modular+0x4e940f)
 #3 0x00007f1a44c42520 (/lib/x86_64-linux-gnu/libc.so.6+0x42520)
 #4 0x000055ebceb25254 (/usr/bin/modular+0x8a9254)
 #5 0x000055ebceb248df (/usr/bin/modular+0x8a88df)
 #6 0x000055ebce7399ad (/usr/bin/modular+0x4bd9ad)
 #7 0x000055ebce727053 (/usr/bin/modular+0x4ab053)
 #8 0x00007f1a44c29d90 (/lib/x86_64-linux-gnu/libc.so.6+0x29d90)
 #9 0x00007f1a44c29e40 __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x29e40)
#10 0x000055ebce7266ee (/usr/bin/modular+0x4aa6ee)
[1]    654203 segmentation fault (core dumped)  modular uninstall mojo

libc6-dev is the most current it can be for ubuntu 22.04, libc6-dev is already the newest version (2.35-0ubuntu3.3)

@MostHated
Copy link
Author

MostHated commented Oct 23, 2023

I was able to 'resolve' this by clearing out the .modular folder/doing modular clean, and then ran modular install mojo, which then worked at that point.

@jackos
Copy link
Collaborator

jackos commented Nov 1, 2023

Great thanks for reporting back @MostHated

@jackos jackos closed this as completed Nov 1, 2023
@ematejska ematejska added the mojo-repo Tag all issues with this label label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
modular-cli modular tool issues mojo-repo Tag all issues with this label
Projects
None yet
Development

No branches or pull requests

3 participants