Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

2.6.6-beta crashes with "illegal instruction" #11321

Closed
nikita-fuchs opened this issue Dec 10, 2019 · 35 comments
Closed

2.6.6-beta crashes with "illegal instruction" #11321

nikita-fuchs opened this issue Dec 10, 2019 · 35 comments

Comments

@nikita-fuchs
Copy link

After updating from 2.5.1 to 2.6.6, it crashes with "Illegal Instruction", right after displaying the updated conversion rate. Here are the full logs before the crash:

2019-12-10 13:58:35 UTC main INFO parity_ethereum::run  Starting Parity-Ethereum/v2.6.6-beta-5162bc2-20191205/x86_64-linux-gnu/rustc1.39.0
2019-12-10 13:58:35 UTC main INFO parity_ethereum::run  Keys path /parity/parityData/keys/ethereum
2019-12-10 13:58:35 UTC main INFO parity_ethereum::run  DB path /parity/parityData/chaindata/ethereum/db/906a34e69aec8c0d
2019-12-10 13:58:35 UTC main INFO parity_ethereum::run  State DB configuration: fast
2019-12-10 13:58:35 UTC main INFO parity_ethereum::run  Operating mode: active
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG fetch  processing requests ...
2019-12-10 13:58:35 UTC main INFO ethcore_service::service  Configured for Ethereum using Ethash engine
2019-12-10 13:58:35 UTC main DEBUG verification  Allocating 12 verifiers, 12 initially active
2019-12-10 13:58:35 UTC main DEBUG verification  Verifier auto-scaling disabled
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #0
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #1
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #2
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #3
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #4
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #5
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #6
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #7
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #8
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #9
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #10
2019-12-10 13:58:35 UTC main DEBUG verification  Adding verification thread #11
2019-12-10 13:58:35 UTC main DEBUG fetch  fetching: "https://api.etherscan.io/api?module=stats&action=ethprice"
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC main DEBUG pip  Initializing light protocol handler
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC main DEBUG sync  Setting the initial state to `Idle`. Our best block: #8629127
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC main DEBUG network  Listening at V4(0.0.0.0:30301)
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-1 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-1 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-2 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-1 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-1 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-2 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-1 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-1 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-1 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-1 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-2 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-2 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-2 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-2 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-1 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-5 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-4 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-7 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC main DEBUG jsonrpc_ws_server::server  Bound to local address: 127.0.0.1:7546
2019-12-10 13:58:35 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-7 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-7 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-7 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-7 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC event.loop0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC event.loop0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC event.loop0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC event.loop0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC event.loop0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC event.loop0 WARN jsonrpc_ipc_server::server  Removed existing file '/parity/parityData/jsonrpc.ipc'.
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-7 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC event.loop0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-7 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-7 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-6 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-7 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC http.worker00 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC http.worker00 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC http.worker20 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC http.worker10 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC http.worker20 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC http.worker10 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC http.worker30 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC http.worker30 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC http.worker00 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC http.worker20 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC http.worker10 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC http.worker30 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:35 UTC fetch DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-0 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:36 UTC fetch DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 INFO miner  Updated conversion rate to Ξ1 = US$147.30 (32327932 wei/gas)
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG miner  minimal_gas_price: Got gas price! 32327932
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 0 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 1 events, 0.000s
2019-12-10 13:58:36 UTC tokio-runtime-worker-3 DEBUG tokio_reactor  loop process - 0 events, 0.000s
  • Parity Ethereum version: 2.6.6-beta
  • Operating system: Ubuntu 18.04.3 LTS
  • Installation: one-line installer
  • Fully synchronized: no, only till around block 8.1 mil.
  • Network: mainnet
  • Restarted: yes
@dvdplm
Copy link
Collaborator

dvdplm commented Dec 10, 2019

Could it be that the CPU you're using does not support the aes-ni instructions? CPUs sold in the last decade do support them but some older or lower tier CPUs lack support. If this is your case I'm afraid you need to build parity-ethereum from source.

@nikita-fuchs
Copy link
Author

nikita-fuchs commented Dec 10, 2019 •
edited
Loading

It's an i7 8th gen, but building from source is a neat idea of course. Giving it a try, hold tight.
Edit: Before 2.6.6beta, everything ran smoothly and stable btw.

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 10, 2019

It's an i7 8th gen,

Hmm, can you be more specific, e.g. cat /proc/cpuinfo | grep 'model name' | uniq?

@makuro
Copy link

makuro commented Dec 10, 2019

the cpu is a Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz

do you need more specs?

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 10, 2019

@makuro @nikita-fuchs are you two speaking about the same CPU or…? i7-8700 certainly supports aes-ni so whatever is going on here that's not it (or @nikita-fuchs CPU is not the same as @makuro talking about, who knows).
@nikita-fuchs the log you posted is cut off before the actual crash it seems, can you post it please?

@makuro
Copy link

makuro commented Dec 10, 2019

@dvdplm yes, we are talking about the same cpu, I think @nikita-fuchs just mixed up the input.

the log is complete, afterwards is just one more line which says:

illegal instructions

that's all there is to it. Sadly. We tried the run of parity with -l debug and the result is the one above. before we added the auto_update directive to the config.toml. Then we updated via one-line installer and tried to rerun ist again and just got the message above.

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 10, 2019

@makuro Got it. Did you try building the beta from source? Same result?

@makuro
Copy link

makuro commented Dec 10, 2019

@dvdplm not yet, will do this tomorrow morning and get back to you here

@niklasad1
Copy link
Collaborator

hmm, this seems strange according to http://www.cpu-world.com/CPUs/Core_i7/Intel-Core%20i7%20i7-8700.html

It does support: aes, sse2 and ssse3 which we require

@makuro
Copy link

makuro commented Dec 11, 2019 •
edited
Loading

@dvdplm

so I did the install from source like described here: https://github.com/paritytech/parity-ethereum and installed it from source.
during that I added the clang and Yasm to the system which was missing.

I checked the installation before installing it with cargo check

The system does still not start. I tried running it without any config and starting with our old config. Both brings the same error.

Loading config file from /parity/config.toml
Option '--whisper' has been removed and is no longer supported.
2019-12-11 11:51:12 UTC main INFO parity_ethereum::run Starting Parity-Ethereum/v2.7.0-nightly-f1f64930c-20191210/x86_64-unknown-linux-gnu/rustc1.39.0
2019-12-11 11:51:12 UTC main INFO parity_ethereum::run Keys path /parity/parityData/keys/ethereum
2019-12-11 11:51:12 UTC main INFO parity_ethereum::run DB path /parity/parityData/chaindata/ethereum/db/906a34e69aec8c0d
2019-12-11 11:51:12 UTC main INFO parity_ethereum::run State DB configuration: fast
2019-12-11 11:51:12 UTC main INFO parity_ethereum::run Operating mode: active
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC fetch DEBUG fetch processing requests ...
2019-12-11 11:51:12 UTC main INFO ethcore_service::service Configured for Ethereum using Ethash engine
2019-12-11 11:51:12 UTC main DEBUG verification Allocating 12 verifiers, 12 initially active
2019-12-11 11:51:12 UTC main DEBUG verification Verifier auto-scaling disabled
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #0
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #1
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #2
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #3
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #4
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #5
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #6
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #7
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #8
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #9
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #10
2019-12-11 11:51:12 UTC main DEBUG verification Adding verification thread #11
2019-12-11 11:51:12 UTC main DEBUG fetch fetching: "https://api.etherscan.io/api?module=stats&action=ethprice"
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC fetch DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC main DEBUG pip Initializing light protocol handler
2019-12-11 11:51:12 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC fetch DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC main DEBUG sync Setting the initial state to Idle. Our best block: #8629127
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC main DEBUG network Listening at V4(0.0.0.0:30301)
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-2 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-1 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-2 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-1 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC fetch DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-2 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-1 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-1 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-2 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-3 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-8 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-7 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-5 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC main DEBUG jsonrpc_ws_server::server Bound to local address: 127.0.0.1:7546
2019-12-11 11:51:12 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-5 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-5 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-5 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-5 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-8 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-8 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC event.loop0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC event.loop0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC event.loop0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC event.loop0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC event.loop0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC event.loop0 WARN jsonrpc_ipc_server::server Removed existing file '/parity/parityData/jsonrpc.ipc'.
2019-12-11 11:51:12 UTC event.loop0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-8 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-8 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-8 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-6 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-8 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC http.worker00 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC http.worker00 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC http.worker10 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC http.worker10 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC http.worker20 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC http.worker20 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC http.worker30 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC http.worker30 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC http.worker00 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC http.worker20 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC http.worker10 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC http.worker30 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:12 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:12 UTC fetch DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 INFO miner Updated conversion rate to Ξ1 = US$145.87 (32644854 wei/gas)
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG miner minimal_gas_price: Got gas price! 32644854
2019-12-11 11:51:13 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-0 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:13 UTC fetch DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 0 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 1 events, 0.000s
2019-12-11 11:51:13 UTC tokio-runtime-worker-4 DEBUG tokio_reactor loop process - 0 events, 0.000s
Illegal instruction (core dumped)

@makuro
Copy link

makuro commented Dec 11, 2019

I did run the tests with cargo test -allafterwards after updating the git submodules.

it returned the same error. the complete output of the tests is included in the attached files.

here is the output from the cargo test -allcommand:

warning: ./parity-ethereum/ethcore/Cargo.toml: An explicit [[bench]] section is specified in Cargo.toml which currently
disables Cargo from automatically inferring other benchmark targets.
This inference behavior will change in the Rust 2018 edition and the following
files will be included as a benchmark target:

./parity-ethereum/ethcore/benches/builtin_contract.rs
This is likely to break cargo build or cargo test as these files may not be
ready to be compiled as a benchmark target today. You can future-proof yourself
and disable this warning by adding autobenches = false to your [package]
section. You may also move the files to a location where Cargo would not
automatically infer them to be a target, such as in subfolders.

For more information on this warning you can consult
rust-lang/cargo#5330
Finished dev [unoptimized + debuginfo] target(s) in 0.17s
Running target/debug/deps/account_db-2f093053a10e2aad
Running target/debug/deps/blooms_db-5028e87084d3a1a8
Running target/debug/deps/chainspec-70fcf154a9200c47
Running target/debug/deps/cli_signer-2a365ea8d8cac389
Running target/debug/deps/common_types-acf0696b72a0b72d
Running target/debug/deps/dir-15e7dc08d1689e06
Running target/debug/deps/eip_152-d34191b4d70ce6eb
Running target/debug/deps/eip_712-0cf13ef63a8b06f2
Running target/debug/deps/ethash-d634af310e524877
Running target/debug/deps/ethcore-8320c5ed4d944f7f
error: process didn't exit successfully: ./parity-ethereum/target/debug/deps/ethcore-8320c5ed4d944f7f` (signal: 4, SIGILL: illegal instruction)

test_result.log

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 11, 2019

Very curious. I have to admit I'm a bit stumped.

Can you try these things:

  • run cargo test inside the ethcore/ folder: same issue yes?
  • can you try forcing the native CPU compilation target with RUSTFLAGS=-C target-cpu=native cargo run in repository root?
  • can you post the full output of cat /proc/cpuinfo on the machine you compile and run on?
  • do you have another computer you can try the built binary on? Same behaviour?
  • can you try running the tests from the parity-crypto crate from here (clone the repo, go into parity-crypto/ and run cargo test)?

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 11, 2019

Also, can you post the full parity configuration TOML file? (or the command line switches you use, if that's how you start parity).

@makuro
Copy link

makuro commented Dec 11, 2019

cat /proc/cpuinfo

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.057
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 0
cpu cores : 6
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.564
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 1
cpu cores : 6
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.102
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 2
cpu cores : 6
apicid : 4
initial apicid : 4
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.000
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 3
cpu cores : 6
apicid : 6
initial apicid : 6
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 4
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.089
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 4
cpu cores : 6
apicid : 8
initial apicid : 8
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 5
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 799.937
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 5
cpu cores : 6
apicid : 10
initial apicid : 10
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 6
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.060
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 0
cpu cores : 6
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.043
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 1
cpu cores : 6
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 8
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.620
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 2
cpu cores : 6
apicid : 5
initial apicid : 5
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 9
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.125
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 3
cpu cores : 6
apicid : 7
initial apicid : 7
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 10
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.136
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 4
cpu cores : 6
apicid : 9
initial apicid : 9
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

processor : 11
vendor_id : GenuineIntel
cpu family : 6
model : 158
model name : Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
stepping : 10
microcode : 0xca
cpu MHz : 800.010
cache size : 12288 KB
physical id : 0
siblings : 12
core id : 5
cpu cores : 6
apicid : 11
initial apicid : 11
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips : 6384.00
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

@makuro
Copy link

makuro commented Dec 11, 2019

/parity-ethereum/ethcore# /root/.cargo/bin/cargo test --all
warning: ./parity-ethereum/ethcore/Cargo.toml: An explicit [[bench]] section is specified in Cargo.toml which currently
disables Cargo from automatically inferring other benchmark targets.
This inference behavior will change in the Rust 2018 edition and the following
files will be included as a benchmark target:

  • ./parity-ethereum/ethcore/benches/builtin_contract.rs

This is likely to break cargo build or cargo test as these files may not be
ready to be compiled as a benchmark target today. You can future-proof yourself
and disable this warning by adding autobenches = false to your [package]
section. You may also move the files to a location where Cargo would not
automatically infer them to be a target, such as in subfolders.

For more information on this warning you can consult
rust-lang/cargo#5330
Finished dev [unoptimized + debuginfo] target(s) in 0.17s
Running./parity-ethereum/target/debug/deps/account_db-2f093053a10e2aad
Running ./parity-ethereum/target/debug/deps/blooms_db-5028e87084d3a1a8
Running ./parity-ethereum/target/debug/deps/chainspec-70fcf154a9200c47
Running ./parity-ethereum/target/debug/deps/cli_signer-2a365ea8d8cac389
Running ./parity-ethereum/target/debug/deps/common_types-acf0696b72a0b72d
Running ./parity-ethereum/target/debug/deps/dir-15e7dc08d1689e06
Running ./parity-ethereum/target/debug/deps/eip_152-d34191b4d70ce6eb
Running ./parity-ethereum/target/debug/deps/eip_712-0cf13ef63a8b06f2
Running ./parity-ethereum/target/debug/deps/ethash-d634af310e524877
Running ./parity-ethereum/target/debug/deps/ethcore-8320c5ed4d944f7f
error: process didn't exit successfully: ./parity-ethereum/target/debug/deps/ethcore-8320c5ed4d944f7f (signal: 4, SIGILL: illegal instruction)

test_result.log

@makuro
Copy link

makuro commented Dec 11, 2019 •
edited
Loading

  • run cargo test inside the ethcore/ folder: same issue yes?

right, output is above

  • can you try forcing the native CPU compilation target with RUSTFLAGS=-C target-cpu=native cargo run in repository root?

do I set this as an env var or do I add this to cargo run ?

  • can you post the full output of cat /proc/cpuinfo on the machine you compile and run on?

output is above

  • do you have another computer you can try the built binary on? Same behaviour?

I do but I need to check if I can use it or it is used for something else

  • can you try running the tests from the parity-crypto crate from here (clone the repo, go into parity-crypto/ and run cargo test)?

will do next

@makuro
Copy link

makuro commented Dec 11, 2019 •
edited
Loading

can you try running the tests from the parity-crypto crate from here (clone the repo, go into parity-crypto/ and run cargo test)?

test_result.log

works without error

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 11, 2019

  • run cargo test inside the ethcore/ folder: same issue yes?
    run cargo test inside the ethcore/ folder: same issue yes?
    right, output is above

No, that's from cargo test --all. Just cargo test please.

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 11, 2019

do I set this as an env var or do I add this to cargo run ?

Either works.

@makuro
Copy link

makuro commented Dec 11, 2019

  • run cargo test inside the ethcore/ folder: same issue yes?
    run cargo test inside the ethcore/ folder: same issue yes?
    right, output is above

No, that's from cargo test --all. Just cargo test please.

here is the output:
Compiling syn v1.0.11
Compiling memchr v2.2.1
Compiling crunchy v0.2.2
Compiling clap v2.33.0
Compiling tiny-keccak v2.0.1
Compiling parity-crypto v0.4.2 (/home/leondrino/parity-common/parity-crypto)
Compiling csv-core v0.1.6
Compiling bstr v0.2.8
Compiling csv v1.1.1
Compiling proc-macro-hack v0.5.11
Compiling serde_derive v1.0.103
Compiling hex-literal-impl v0.2.1
Compiling hex-literal v0.2.1
Compiling criterion v0.3.0
Finished dev [unoptimized + debuginfo] target(s) in 10.41s
Running /home/leondrino/parity-common/target/debug/deps/parity_crypto-5dd9ad92f0883830
Doc-tests parity-crypto

test_result.log

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 11, 2019

can you try running the tests from the parity-crypto crate from here (clone the repo, go into parity-crypto/ and run cargo test)?

test_result.log

works without error

Looks like you ran cargo test in the repository root. Can you try it inside the parity-crypto/ subfolder, and I was mistaken, it should be cargo test --features=publickey – this should compile the C-library used for some crypto operations and it uses aes-ni.

@makuro
Copy link

makuro commented Dec 11, 2019

can you try running the tests from the parity-crypto crate from here (clone the repo, go into parity-crypto/ and run cargo test)?
test_result.log
works without error

Looks like you ran cargo test in the repository root. Can you try it inside the parity-crypto/ subfolder, and I was mistaken, it should be cargo test --features=publickey – this should compile the C-library used for some crypto operations and it uses aes-ni.

it was run within the parity-crypto folder.

I did rerun with the features:

cargo test --features=publickey
Downloaded primitive-types v0.6.1
Downloaded ethbloom v0.8.1
Downloaded impl-rlp v0.2.1
Downloaded fixed-hash v0.5.1
Downloaded impl-serde v0.2.3
Downloaded impl-codec v0.4.2
Compiling arrayvec v0.5.1
Compiling cc v1.0.48
Compiling rlp v0.4.4
Compiling impl-serde v0.2.3
Compiling uint v0.8.2
Compiling fixed-hash v0.5.1
Compiling impl-rlp v0.2.1
Compiling ethbloom v0.8.1
Compiling parity-secp256k1 v0.7.0
Compiling parity-scale-codec v1.1.0
Compiling impl-codec v0.4.2
Compiling primitive-types v0.6.1
Compiling ethereum-types v0.8.0
Compiling parity-crypto v0.4.2 (/home/leondrino/parity-common/parity-crypto)
Finished dev [unoptimized + debuginfo] target(s) in 11.32s
Running /home/leondrino/parity-common/target/debug/deps/parity_crypto-1c0a1514e4e7384f

running 31 tests
test hmac::test::secrets_are_zeroed_on_drop ... ok
test pbkdf2::test::basic_test ... ok
test hmac::test::simple_mac_and_verify ... ok
test aes::tests::test_aes_short ... ok
test hmac::test::ietf_test_vectors ... ok
test publickey::ec_math_utils::tests::generation_point_expected ... ok
test publickey::ec_math_utils::tests::known_public_is_valid ... ok
test publickey::ec_math_utils::tests::public_multiplication_verification ... ok
test publickey::ec_math_utils::tests::public_negation_is_involutory ... ok
test publickey::ec_math_utils::tests::public_addition_is_commutative ... ok
test publickey::extended_keys::tests::h256_hard ... ok
test publickey::ec_math_utils::tests::public_addition_is_reversible_with_subtraction ... ok
test publickey::ecdsa_signature::tests::vrs_conversion ... ok
test publickey::ecdsa_signature::tests::signature_to_and_from_str ... ok
test publickey::extended_keys::tests::test_seeds ... ok
test publickey::extended_keys::tests::test_vector_1 ... ok
test publickey::ecdsa_signature::tests::sign_and_verify_public ... ok
test publickey::keypair::tests::from_secret ... ok
test publickey::keypair::tests::keypair_display ... ok
test publickey::ecdsa_signature::tests::sign_and_recover_public ... ok
test test::can_test_for_equality ... ok
test publickey::secret_key::tests::multiplicating_secret_inversion_with_secret_gives_one ... ok
test publickey::extended_keys::tests::test_vector_2 ... ok
test publickey::secret_key::tests::secret_pow ... ok
test publickey::ecdsa_signature::tests::sign_and_verify_address ... ok
test publickey::extended_keys::tests::match_ ... ok
test publickey::secret_key::tests::secret_inversion_is_reversible_with_inversion ... ok
test publickey::extended_keys::tests::h256_soft_match ... ok
test publickey::ecies::tests::ecies_shared ... ok
test publickey::extended_keys::tests::smoky ... ok
test scrypt::test_derive ... ok

test result: ok. 31 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

Doc-tests parity-crypto

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 11, 2019

While your hardware does support aes it does not show up in the /proc/cpuinfo output. Could it be that the BIOS of your machine has disabled it somehow? Is this a cloud server or your own machine? Can you check what BIOS version you have and if there's an option anywhere related to cryptographic CPU extensions? Or if there's an updated version available?

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 pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 11, 2019

@makuro What is the output of sort -u /proc/crypto | grep module on your machine?

Here's what I see on mine:

$ sort -u /proc/crypto | grep module
module       : aesni_intel
module       : aes_x86_64
module       : crc32_pclmul
module       : crct10dif_pclmul
module       : ghash_clmulni_intel
module       : kernel

Do you have the aes related modules loaded?

@niklasad1
Copy link
Collaborator

Please run

rustc --print cfg -C target-cpu=native

If it claims aes then it could be rust just checks your CPU family and not that the aes is enabled by the OS

Another thing you can do it is build with -C target-cpu=native --verbose and then check if the aes feature is enabled for the build

@makuro
Copy link

makuro commented Dec 11, 2019 •
edited
Loading

@makuro What is the output of sort -u /proc/crypto | grep module on your machine?

Here's what I see on mine:

$ sort -u /proc/crypto | grep module
module       : aesni_intel
module       : aes_x86_64
module       : crc32_pclmul
module       : crct10dif_pclmul
module       : ghash_clmulni_intel
module       : kernel

Do you have the aes related modules loaded?

sort -u /proc/crypto | grep module
module       : arc4
module       : crc32_pclmul
module       : crct10dif_pclmul
module       : ecdh_generic
module       : ghash_clmulni_intel
module       : kernel

actually it does not

@makuro
Copy link

makuro commented Dec 11, 2019

Please run

rustc --print cfg -C target-cpu=native

If it claims aes then it could be rust just checks your CPU family and not that the aes is enabled by the OS

output of rustc:

rustc --print cfg -C target-cpu=native
debug_assertions
target_arch="x86_64"
target_endian="little"
target_env="gnu"
target_family="unix"
target_feature="aes"
target_feature="avx"
target_feature="avx2"
target_feature="bmi1"
target_feature="bmi2"
target_feature="fma"
target_feature="fxsr"
target_feature="lzcnt"
target_feature="pclmulqdq"
target_feature="popcnt"
target_feature="rdrand"
target_feature="rdseed"
target_feature="sse"
target_feature="sse2"
target_feature="sse3"
target_feature="sse4.1"
target_feature="sse4.2"
target_feature="ssse3"
target_feature="xsave"
target_feature="xsavec"
target_feature="xsaveopt"
target_feature="xsaves"
target_os="linux"
target_pointer_width="64"
target_vendor="unknown"
unix

it seems like you thought. rust is taking the cpu informations and not the features

@niklasad1

Another thing you can do it is build with -C target-cpu=native --verbose and then check if the aes feature is enabled for the build

where do I put this? because cargo build does not recognize -C

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 11, 2019

where do I put this? because cargo build does not recognize -C

RUSTFLAGS="-C target-cpu=native" cargo build --verbose (very noisy), but yeah I think we know what the problem is now: something, either the OS or the BIOS, has disabled the aes instructions. Rust does not ask the OS for its capabilities so it compiles with aes enabled (as your hardware should support it) and then it traps.

@dvdplm
Copy link
Collaborator

dvdplm commented Dec 11, 2019

Are you using any kind of virtualization on the machine?

@makuro
Copy link

makuro commented Dec 11, 2019

While your hardware does support aes it does not show up in the /proc/cpuinfo output. Could it be that the BIOS of your machine has disabled it somehow? Is this a cloud server or your own machine? Can you check what BIOS version you have and if there's an option anywhere related to cryptographic CPU extensions? Or if there's an updated version available?

it is a local machine, need to get access to the room first then I can check the bios and settings

@makuro
Copy link

makuro commented Dec 11, 2019

Are you using any kind of virtualization on the machine?

nope. it was a blank ubuntu 18.04.3 installation with only main repository activated without any docker, vm or similar installed.

it does use llvm tho to bundle the hard drives

@makuro
Copy link

makuro commented Dec 11, 2019 •
edited
Loading

@dvdplm @niklasad1

I checked the bios and the aes was actually disabled.
newly found output:

sort -u /proc/crypto | grep module
module       : aesni_intel
module       : aes_x86_64
module       : arc4
module       : crc32_pclmul
module       : crct10dif_pclmul
module       : ecdh_generic
module       : ghash_clmulni_intel
module       : kernel
module       : pcbc

will try rebuild from source

@makuro
Copy link

makuro commented Dec 11, 2019

@nikita-fuchs @dvdplm @niklasad1 I did not need to change anything, I just started the node and it works.

So the error was that aes was not activated within the bios.

@dvdplm dvdplm closed this as completed Dec 11, 2019
@stone212
Copy link

stone212 commented Feb 8, 2020

@makuro Was this a regular node or a worker/miner? I'm wondering if all nodes must support this instruction?

@makuro
Copy link

makuro commented Feb 8, 2020

@stone212

This was a regular node.

I think a sentence within the documentations would not hurt.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@dvdplm @makuro @nikita-fuchs @niklasad1 @stone212