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
update to 5.18.0.268-0xamarin1+ubuntu1404b1 fails #13240
Comments
/cc @directhex |
This is a crash in AOT'd code. Could be a bug triggered by a different locale (German in this case). @Nichtraucher could you post the output of |
sure
buttlong output here: https://pastebin.com/KL4fMWhd |
What is your CPU? Can you delete |
That helped - the update went through. |
Update failed for me on AMD K7, K10 and Intel Pineview. I used these steps on Ubuntu 18.04.2:
Logout then back in to get the .profile environment variable to set. Presumably, these older non-sse4.1 machines will only work with the JIT AOT as opposed to the newer implementation. I do a quick check on .profile to populate the MONO_ENV_OPTIONS if it doesn't exist or update the value if it does. |
As per #12182, LLVM AOT is only used on systems with SSSE4.1 - did we change our optimizations for legacy AOT? |
If it helps any, I'm having the exact same issue on an AMD Athlon LE-1640 single core, 2698.91Mhz CPU on Lubuntu 18.04.2 LTS. Also had the EXACT same issue on the December 24th, 2018 Mono update which took me about 6 hours to stumble through a fix. Still not certain what the ultimate solution was, but many hours were spent figuring out how to uninstall Mono components that refused to uninstall, followed by re-installing components. ¯\_(ツ)_/¯ I'll try the fixes listed above and report back. Edit: Removing the amd64 directory with its attendant mscorelib.dll.so file did produce a change. Upon running sudo apt --fix-broken install it advanced further, ending with: ... I then ran, sudo apt-get upgrade The following packages will be upgraded: ...which completed without errors. Now, for a reboot.... Edit: Reboot was a success and all three of my Mono-based daemons appear to be up and running fine. I wish this post was around last Christmas. It's a much more elegant solution than what I came up with. :) |
Ubuntu users might want to clear /var/crash to avoid being spammed by "A system problem has been detected" messages.
I have to say that this particular update failure is truly terrifying so when I read:
Then:
There was no way I was going to take a chance on having the problem reoccur. Better to set the environment variable in .profile, to ensure SSE4.1 optimized AOT doesn't have the slightest chance of slipping through. I know which of my computers are affected. It just isn't worth the headache. |
You shouldn't get the SSSE4.1-requiring AOT on CPUs which don't support it - it's specific to LLVM AOT, which is disabled on CPUs which don't support it. This bug seems more like we made changes to our optimizations in non-LLVM AOT? I'll have to investigate the AOT code |
I can't verify that you're definitely not producing LLVM AOT, without a |
Steps to Reproduce
Current Behavior
update fails due to unresolved dependencies and other errors (see terminal output below)
Expected Behavior
the update goes through smoothly
On which platforms did you notice this
[ ] macOS
[x ] Linux
[ ] Windows
Version Used:
Linux version 4.4.0-142-generic (buildd@lcy01-amd64-006) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1
14.04.4) # 16814.04.1-Ubuntu SMP Sat Jan 19 11:26:28 UTC 2019I'm using the repositories provided by mono.
Mono version:
Mono JIT compiler version 5.18.0.268 (tarball Thu Feb 28 15:28:45 UTC 2019)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: altstack
Notifications: epoll
Architecture: amd64
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(600)
Suspend: preemptive
GC: sgen (concurrent by default)
Stacktrace
terminal output here: https://pastebin.com/2wVtmGDQ
I assume that this is the same or a similar issue as the one that I've reported previously here: #12182 ?
The text was updated successfully, but these errors were encountered: