Downloaded Ubuntu 18.04 from here https://www.microsoft.com/store/productId/9N9TNGVNDL3Q
Downloaded Linux ARM (glibc) 64-bit from https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.1.0-rc1-download.md
OS Name Microsoft Windows 10 Pro Insider Preview
Version 10.0.17666 Build 17666
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Manufacturer ASUSTeK COMPUTER INC.
System Model NovaGo TP370QL
System Type ARM64-based PC
System SKU 6
Processor Snapdragon(TM) 835, 2208 Mhz, 8 Core(s), 8 Logical Processor(s)
BIOS Version/Date Qualcomm Inc. TP370QL.253, 3/30/2018
SMBIOS Version 3.0
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product NovaGo TP370QL
BaseBoard Version 1.0
Architecture: aarch64
Byte Order: Little Endian
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 1
Core(s) per socket: 8
Socket(s): 1
Vendor ID: ARM
Model: 0
Model name: Cortex-A57
Stepping: r1p0
CPU max MHz: 2208.0000
BogoMIPS: 1900
Hypervisor vendor: Windows Subsystem for Linux
Virtualization type: container
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32
dotnet new
dotnet --info
dotnet --version
snickler@WOATARGET:~/dotnet-2.1-rc1$ ./dotnet new
Illegal instruction (core dumped)
snickler@WOATARGET:~/dotnet-2.1-rc1$ ./dotnet --info
Illegal instruction (core dumped)
snickler@WOATARGET:~/dotnet-2.1-rc1$ ./dotnet --version
Illegal instruction (core dumped)
Hey @BenHillis @terrajobst - any thoughts on what's causing these Illegal Instruction errors?
I'm not sure, I know @Brian-Perkins has been looking at some arm64 issues recently.
One thing I didn't add - the --list-runtimes and --list-sdks switches are the only ones that don't return Illegal Instruction
snickler@WOATARGET:~/dotnet-2.1-rc1$ ./dotnet --list-sdks
2.1.300-rc1-008673 [/home/snickler/dotnet-2.1-rc1/sdk]
snickler@WOATARGET:~/dotnet-2.1-rc1$ ./dotnet --list-runtimes
Microsoft.NETCore.App 2.1.0-rc1 [/home/snickler/dotnet-2.1-rc1/shared/Microsoft.NETCore.App]
I attempted to install from the instructions linked in the OP and it doesn't appear ARM64 versions are present. If someone can provide a set of commands I can run from a clean Ubuntu 18 install in order to repro this, it would be very helpful.
@Brian-Perkins I updated the main post with the link to the Ubuntu 18.04 download that works for ARM64.
Also, it seems that the dotnet-sdk-latest-Linux-arm64.tar.gz from https://github.com/dotnet/cli/blob/master/README.md (which is currently 2.1.400-preview-008858 at the time of this post) also doesn't work properly.
I am still having trouble locating ARM64 dotnet binaries.
@Brian-Perkins on https://github.com/dotnet/core/blob/master/release-notes/download-archives/2.1.0-rc1-download.md, it's the 64-bit link on the Linux ARM (glibc) row.
Thank you. I thought I had tried that link, but on attempt number two it looks good. I ended up here which wasn't as useful.
@Brian-Perkins - Have you been able to reproduce?
I was able to reproduce. It is complaining about a cache flush instruction -- I am looking into it.
Great, Thanks!
From: Brian-Perkins notifications@github.com
Sent: Thursday, May 17, 2018 11:53:36 AM
To: dotnet/core
Cc: Jeremy Sinclair; Author
Subject: Re: [dotnet/core] Illegal Instruction when using dotnet commands on 2.1.300-rc1 SDK with Ubuntu 18.04 ARM64 on WSL (#1561)
I was able to reproduce. It is complaining about a cache flush instruction -- I am looking into it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fcore%2Fissues%2F1561%23issuecomment-389915978&data=02%7C01%7C%7C1fa56466078f4e2b073c08d5bc0e5a16%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636621692175750660&sdata=ISXqGhoWhw8P%2FcyWMKIkjguygoWpEX%2FudmcSIkH2saA%3D&reserved=0, or mute the threadhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD1IpWE4VD6VLs934lRIqrVT2pZ9cggkks5tzZ0AgaJpZM4T-yJf&data=02%7C01%7C%7C1fa56466078f4e2b073c08d5bc0e5a16%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636621692175750660&sdata=wb69Ng4%2BfWgOveUgqwjRXwAcWlx%2FF4RyixGKu7mEzdA%3D&reserved=0.
We are working on a WSL fix for this. I will add another update when it makes it out in an Insiders Build.
This is great to hear. Thanks so much @bitcrazed @Brian-Perkins
I know what I'm trying out when I get home tonight. Thanks for digging into this. I'll let you know if I happen to run into anything.
Get Outlook for Androidhttps://aka.ms/ghei36
From: Brian-Perkins notifications@github.com
Sent: Thursday, June 14, 2018 5:23:33 PM
To: dotnet/core
Cc: Jeremy Sinclair; Author
Subject: Re: [dotnet/core] Illegal Instruction when using dotnet commands on 2.1.300-rc1 SDK with Ubuntu 18.04 ARM64 on WSL (#1561)
This should be resolved in Insider Build 17692https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fblogs.windows.com%2Fwindowsexperience%2F2018%2F06%2F14%2Fannouncing-windows-10-insider-preview-build-17692&data=02%7C01%7C%7C48399c27f6ae4bd1bce808d5d23d159d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636646082146039126&sdata=lzXWkVlVK5erxwEJZJT3CaALgsNXmzjCuQKeYMVr7MA%3D&reserved=0 - WSL specific release notes herehttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWSL%2Freleases%2Ftag%2F17692&data=02%7C01%7C%7C48399c27f6ae4bd1bce808d5d23d159d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636646082146039126&sdata=6ilnSbsM7WOoUrrsQn8d37OuAb1P7cfcAhGnzoeYymI%3D&reserved=0 if you are on the Insider track. There is no fix yet for the RS4 release -- I will update when that changes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fcore%2Fissues%2F1561%23issuecomment-397442559&data=02%7C01%7C%7C48399c27f6ae4bd1bce808d5d23d159d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636646082146039126&sdata=85osk8JCx%2FkieAwx%2FW7fH0smu%2BBIDVLvddddTYW21x8%3D&reserved=0, or mute the threadhttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD1IpUxeNWTk_C2B6DdlyY4itwL4RBbsks5t8tRVgaJpZM4T-yJf&data=02%7C01%7C%7C48399c27f6ae4bd1bce808d5d23d159d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636646082146039126&sdata=VOGOggi0mGlTpW3qC4WlMEjxJheP8bLCV4r0M%2BHcoec%3D&reserved=0.
I will mark this issue as fixed, but I'm opening another issue that I've discovered while trying to use it.
Most helpful comment
We are working on a WSL fix for this. I will add another update when it makes it out in an Insiders Build.