Not signed in (Sign In)
    • CommentAuthorKennyJ
    • CommentTimeJan 9th 2009
     permalink
    I'm Having problems installing Mono 2.0.1 on Ubuntu 8.04.1 LTS (Hardy) per the instructions at:
    http://devarthur.blogspot.com/2008/10/compiling-mono-201-on-ubuntu-gutsy.html
    Everything actually seems to install without any problems until I try to test the installation per the instructions at:
    http://www.ibm.com/developerworks/library/l-mono/index.html#N1021B

    then I get this error:

    root@Jonesland:/var# mcs example.cs
    TYPE: 7
    V: ves_icall_System_Threading_Thread_ResetAbort
    **
    ** ERROR:(mini-amd64.c:199):amd64_patch: assertion failed: (amd64_is_imm32 (disp))
    Stacktrace:


    Native stacktrace:

    /usr/local/bin/mono [0x42a1f5]
    /lib/libpthread.so.0 [0x7f839b0547d0]
    /lib/libc.so.6(gsignal+0x35) [0x7f839aa95095]
    /lib/libc.so.6(abort+0x110) [0x7f839aa96af0]
    /usr/lib/libglib-2.0.so.0(g_assertion_message+0x117) [0x7f839b6c8d87]
    /usr/lib/libglib-2.0.so.0 [0x7f839b6c9222]
    /usr/local/bin/mono [0x4384eb]
    /usr/local/bin/mono [0x52c318]
    /usr/local/bin/mono [0x55a128]
    /usr/local/bin/mono [0x55ae1a]
    /usr/local/bin/mono [0x55b4f5]
    /usr/local/bin/mono [0x4c1595]
    /usr/local/bin/mono(mono_runtime_init+0x14b) [0x47dc7b]
    /usr/local/bin/mono [0x528b9c]
    /usr/local/bin/mono(mono_main+0x35e) [0x41788e]
    /lib/libc.so.6(__libc_start_main+0xf4) [0x7f839aa811c4]
    /usr/local/bin/mono(realloc+0x3b1) [0x416f59]

    Debug info from gdb:


    =================================================================
    Got a SIGABRT while executing native code. This usually indicates
    a fatal error in the mono runtime or one of the native libraries
    used by your application.
    =================================================================
  1.  permalink
    I'm getting the same error, this is listed as a bug with the XEN kernel that's being used:
    https://bugs.launchpad.net/ubuntu/+source/linux/+bug/237724
    • CommentAuthormillisami
    • CommentTimeFeb 26th 2009
     permalink
    Me too getting the same problem and trying to fix this since 2 days and haven't got any luck.
    Have you guys fixed this problem??
    Can anybody fix this??
    • CommentAuthorbburdick
    • CommentTimeFeb 26th 2009
     permalink
    Hey guys, I did a little digging into the problem and think that upgrading your Slice to the latest kernel should fix it. We can reboot your Slice into the latest kernel for you if you submit a support ticket from the "Help" section of the Slicemanager and ask us to upgrade you. The latest we have available is 2.6.24-23.48.
    • CommentAuthorbskinner
    • CommentTimeFeb 28th 2009
     permalink
    I just had my kernel updated to 2.6.24-23-xen and still no love on the ** ERROR:(mini-amd64.c:192):amd64_patch: assertion failed: (amd64_is_imm32 (disp))

    Following the bug reference that lordmortis quoted above, they say they have a patch for it here:
    http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commitdiff;h=6b2514fb662158f2def03a618c5c671c95f636a8

    But I couldn't tell you how to go about getting this applied into my slice. Any thoughts?
    • CommentAuthormillisami
    • CommentTimeMar 1st 2009
     permalink
    @bburdick, I filed the request to upgrade my kernel, its updated and did the installation.
    But still no-luck, I'm getting the same weirdo problem again nagging around!! Its killing me.
    Why ain't there the bug-free version of Mono for Ubuntu Hardy??
    • CommentAuthorbskinner
    • CommentTimeMar 3rd 2009
     permalink
    Well, since the kernel upgrade didn't solve the issue, I went an recompiled mono from the source with the following change taken from this article: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/237724


    matteo wrote on 2008-06-14:

    I have been suggested a work around for mono to work with the bugged kernel:

    1. Download mono source
    2. Edit file mini/mini-amd64.h adding #define MONO_ARCH_NOMAP32BIT at the end of the file, just before the last #endif
    3. Compile mono using ./configure --prefix=/usr if you want to replace the current mono installation and make you life easier with GAC
    4. If the case, add in GAC the assemblies not fund by the new mono installation (http://www.mono-project.com/Assemblies_and_the_GAC)

    Note that this is a workaround for the kernel bug outlined in my previous post, not a fix for mono.

    Hope it helps


    I don't get that assertion error any longer and can compile and run mono programs now.
    • CommentAuthordavel
    • CommentTimeJun 25th 2009
     permalink
    I'm having to set up an EC2 machine to run FogBugz after this kernel bug bit me on Slicehost.
    I didn't want to get into the whole "build Mono from source" ball of wax.
    Please support a newer kernel soon!
    •  
      CommentAuthorjason
    • CommentTimeJun 25th 2009
     permalink
    davel,

    We have a 2.6.26 kernel in testing that should be available very soon. Send in a support ticket and we can update you when it's ready.
    • CommentAuthorbburdick
    • CommentTimeJul 8th 2009
     permalink
    Hey folks, good news! We've just made the 2.6.24-24.55 kernel available and have done some internal testing that shows that the mono issues described in this thread are fixed with this version. If you'd like us to get your slice updated for you, please shoot us a support ticket from the 'help' section of the slicemanager and we will take care of it for you right away. Cheers!