'Illegal instruction' on a server with Intel Atom N2800 (bonnell)

[pini-gh]

Hi,

I am experimenting with node-template v3.0.0+monthly-2021-05, and while it runs fine on my laptop, it won't even start on my dedicated server featuring CPU Intel Atom N2800 (bonnell arch):

$ ./node-template 
Illegal instruction

Any hint about how to chase this would be very much appreciated.

[nuke-web3]

Somewhat related: https://github.com/substrate-developer-hub/substrate-node-template/issues/179

similar error resolved by installing the right toolchain:
paritytech/polkadot#3482

did you install the req. things on both machines?
https://substrate.dev/docs/en/knowledgebase/getting-started/

[pini-gh]

The build is done via a Dockerfile:

FROM alpine as build

RUN apk update && \
        apk add ca-certificates curl && \
        update-ca-certificates && \
        apk add --update \
                cmake \
                make \
                pkgconfig \
                gcc \
                g++ \
                musl-dev \
                linux-headers \
                protoc \
                openssl-dev \
                clang-dev

# install latest stable rust
RUN curl https://sh.rustup.rs -sSf | sh -s -- -y

# Copy source tree
COPY . .

# build
ARG threads=1
RUN source ~/.cargo/env && \
        RUSTFLAGS="-C target-feature=-crt-static" \
                cargo build --release -j $threads

Both machines (laptop and dedicated server) have Intel x86_64 CPU. I usually build on my laptop because it's the fastest. But building directly on the dedicated server gives the very same results.

[nuke-web3]

This might be an issue with docker... I would suggest looking for issues running docker with rust on arch, I think this has been reported elsewhere... Something to do with deps on your host machine docker depends on. I think SSL related or clang related

[pini-gh]

No, this has nothing to do with Docker. I've just built natively on the dedicated server and it shows the same behavior, unfortunately.

[nuke-web3]

right, I think it is your host server that is lacking dependencies that docker needs, and thus both inside a container and on the host OS you see this issue.

Can you elaborate on your server specs & OS?
https://substrate.dev/docs/en/knowledgebase/getting-started/ for instructions on the dependencies.

[pini-gh]

right, I think it is your host server that is lacking dependencies that docker needs

I've just said that I've tested a native non Docker build. So this can't be related to Docker.

Can you elaborate on your server specs & OS?

The server is a KS02 from kimsufi.com:

• CPU Intel Atom N2800 2c/4t 1,86GHz
• RAM 4GB DDR3 1066 MHZ
• Hard disk 1TB

Flags from cat /proc/cpuinfo:

flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl nonstop_tsc cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm dtherm arat

The OS is an up to date Debian 10 (Buster).

[pini-gh]

@nukemandan I can give you an ssh access to this server. It is a temporary install with nothing critical. I just need a public ssh key.

[nuke-web3]

I am not sure if your core is missing something that would lead to your error, that is out of the scope of substrate unfortunately.

Did you install the required Debian dependencies we out in the guide I mentioned?

[pini-gh]

The 'illegal instruction' error is not "missing dependancy" related. My guess is that a dependency of another dependency has some generated assembly code incompatible with this Atom x86_64 savior. What I don't know is: how to debug that?

[nuke-web3]

Unclear to me. I am asking the team to take a look at this issue and help us out. 🙏🏼

[koute]

The 'illegal instruction' error is not "missing dependancy" related. My guess is that a dependency of another dependency has some generated assembly code incompatible with this Atom x86_64 savior. What I don't know is: how to debug that?

If you run the binary under gdb it should point at what exact instruction your Atom doesn't like. Something like this:

$ gdb ./node-template 
(gdb) run
...
Program received signal SIGILL, Illegal instruction.
...
(gdb) disas
(gdb) bt

should give us the necessary information.