Skip to content
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

gemini-1b-2022-jun-18 silently exists on Windows without doing anything #611

Closed
nazar-pc opened this issue Jun 18, 2022 · 9 comments · Fixed by #637
Closed

gemini-1b-2022-jun-18 silently exists on Windows without doing anything #611

nazar-pc opened this issue Jun 18, 2022 · 9 comments · Fixed by #637
Assignees
Labels
bug Something isn't working

Comments

@nazar-pc
Copy link
Member

Seems to be Windows-specific.

Two threads on Discord:
https://discord.com/channels/864285291518361610/864285291518361613/987704674838782062
https://discord.com/channels/864285291518361610/864285291518361613/987596219658436678

@nazar-pc nazar-pc added the bug Something isn't working label Jun 18, 2022
@i1i1
Copy link
Contributor

i1i1 commented Jun 20, 2022

Hmm, fail to reproduce this issue. Node starts for me:

.\subspace-node-windows-x86_64-gemini-1b-2022-jun-18.exe --chain gemini-1 `
>> --execution wasm `
>> --pruning 1024 `
>> --keep-blocks 1024 `
>> --validator
←[2m2022-06-20 14:35:04←[0m Subspace
←[2m2022-06-20 14:35:04←[0m ✌️  version 0.1.0-de3dfb1c8ad
←[2m2022-06-20 14:35:04←[0m ❤️  by Subspace Labs <https://subspace.network>, 2021-2022
←[2m2022-06-20 14:35:04←[0m 📋 Chain specification: Subspace Gemini 1
←[2m2022-06-20 14:35:04←[0m 🏷  Node name: awesome-offer-2222
←[2m2022-06-20 14:35:04←[0m 👤 Role: AUTHORITY
←[2m2022-06-20 14:35:04←[0m 💾 Database: ParityDb at C:\Users\Ivan\AppData\Local\subspace-node\data\chains\subspace_gemini_1b\paritydb\full
←[2m2022-06-20 14:35:04←[0m ⛓  Native runtime: subspace-3 (subspace-0.tx0.au0)
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] Starting archiving from genesis
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] Archiving already produced blocks 0..=0
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] 🏷  Local node identity is: 12D3KooWMTnTuVau1U6y9qAfJdffG imztyni3s3REZkgK1Hh9VZi
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] 🧑‍🌾 Starting Subspace Authorship worker
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] 💻 Operating system: windows
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] 💻 CPU architecture: x86_64
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] 💻 Target environment: msvc
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] 📦 Highest known block at #0
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] 〽️ Prometheus exporter started at 127.0.0.1:9615
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] Running JSON-RPC HTTP server: addr=127.0.0.1:9933, allowed origins=Some(["http://localhost:*", "http://127.0.0.1:*", "https://localhost:*", "https://127.0.0.1:*", "https://polkadot.js.org"])
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] Running JSON-RPC WS server: addr=127.0.0.1:9944, allowed origins=Some(["http://localhost:*", "http://127.0.0.1:*", "https://localhost:*", "https://127.0.0.1:*", "https://polkadot.js.org"])
←[2m2022-06-20 14:35:05←[0m [PrimaryChain] creating instance on iface 192.168.88.250
←[2m2022-06-20 14:35:06←[0m [PrimaryChain] 🔍 Discovered new external address for our node: /ip4/178.206.249.121/tcp/30333/p2p/12D3KooWMTnTuVau1U6y9qAfJdffGimztyni3s3REZkgK1Hh9VZi
←[2m2022-06-20 14:35:10←[0m [PrimaryChain] Waiting for farmer to receive and acknowledge archived segment
←[2m2022-06-20 14:35:10←[0m [PrimaryChain] ⚙️  Syncing, target=#287790 (24 peers), best: #0 (0x9ee8…ccf0), finalized #0 (0x9ee8…ccf0), ⬇ 2.3MiB/s ⬆ 22.3kiB/s
←[2m2022-06-20 14:35:15←[0m Accepting new connection, 1/100
←[2m2022-06-20 14:35:15←[0m Accepting new connection, 2/100
←[2m2022-06-20 14:35:15←[0m [PrimaryChain] Waiting for farmer to receive and acknowledge archived segment
←[2m2022-06-20 14:35:15←[0m [PrimaryChain] ⚙️  Syncing  0.0 bps, target=#219344 (39 peers), best: #0 (0x9ee8…ccf0), finalized #0 (0x9ee8…ccf0), ⬇ 8.4MiB/s ⬆ 14.1kiB/s
←[2m2022-06-20 14:35:20←[0m [PrimaryChain] Waiting for farmer to receive and acknowledge archived segment
←[2m2022-06-20 14:35:20←[0m [PrimaryChain] ⚙️  Syncing  0.0 bps, target=#287790 (42 peers), best: #0 (0x9ee8…ccf0), finalized #0 (0x9ee8…ccf0), ⬇ 10.5MiB/s ⬆ 10.6kiB/s
←[2m2022-06-20 14:35:25←[0m [PrimaryChain] ⚙️  Syncing  0.0 bps, target=#287790 (50 peers), best: #0 (0x9ee8…ccf0), finalized #0 (0x9ee8…ccf0), ⬇ 7.5MiB/s ⬆ 32.5kiB/s
←[2m2022-06-20 14:35:25←[0m [PrimaryChain] ❌ Error while dialing /dns/telemetry.polkadot.io/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Timeout }
←[2m2022-06-20 14:35:25←[0m [PrimaryChain] ❌ Error while dialing /dns/telemetry.subspace.network/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Timeout }
←[2m2022-06-20 14:35:30←[0m [PrimaryChain] ⚙️  Syncing  0.0 bps, target=#287791 (50 peers), best: #0 (0x9ee8…ccf0), finalized #0 (0x9ee8…ccf0), ⬇ 7.6MiB/s ⬆ 21.5kiB/s
←[2m2022-06-20 14:35:35←[0m [PrimaryChain] ⚙️  Syncing  0.0 bps, target=#287791 (50 peers), best: #0 (0x9ee8…ccf0), finalized #0 (0x9ee8…ccf0), ⬇ 10.9MiB/s ⬆ 9.3kiB/s
←[2m2022-06-20 14:35:40←[0m [PrimaryChain] ⚙️  Syncing  0.0 bps, target=#287791 (50 peers), best: #0 (0x9ee8…ccf0), finalized #0 (0x9ee8…ccf0), ⬇ 11.1MiB/s ⬆ 13.1kiB/s
←[2m2022-06-20 14:35:45←[0m [PrimaryChain] ⚙️  Syncing  0.0 bps, target=#287791 (50 peers), best: #0 (0x9ee8…ccf0), finalized #0 (0x9ee8…ccf0), ⬇ 11.1MiB/s ⬆ 6.7kiB/s
←[2m2022-06-20 14:35:50←[0m [PrimaryChain] ⚙️  Syncing  0.0 bps, target=#287791 (42 peers), best: #0 (0x9ee8…ccf0), finalized #0 (0x9ee8…ccf0), ⬇ 10.1MiB/s ⬆ 6.1kiB/s

@shuralemain
Copy link

shuralemain commented Jun 22, 2022

HI! after launching the version from June 18 on Windows, I see a recurring error:

PS C:\subspace> .\subspace-node-windows-x86_64-gemini-1b-2022-jun-18.exe --chain gemini-1 ` --execution wasm ` --pruning 1024 ` --keep-blocks 1024 ` --validator ` --name Shuralemain
←[2m2022-06-22 13:21:34←[0m Subspace
←[2m2022-06-22 13:21:34←[0m ✌️  version 0.1.0-de3dfb1c8ad
←[2m2022-06-22 13:21:34←[0m ❤️  by Subspace Labs <https://subspace.network>, 2021-2022
←[2m2022-06-22 13:21:34←[0m 📋 Chain specification: Subspace Gemini 1
←[2m2022-06-22 13:21:34←[0m 🏷  Node name: Shuralemain
←[2m2022-06-22 13:21:34←[0m 👤 Role: AUTHORITY
←[2m2022-06-22 13:21:34←[0m 💾 Database: ParityDb at C:\Users\vyaly\AppData\Local\subspace-node\data\chains\subspace_gemini_1b\paritydb\full
←[2m2022-06-22 13:21:34←[0m ⛓  Native runtime: subspace-3 (subspace-0.tx0.au0)
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] Last archived block 315534
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] Archiving already produced blocks 315535..=315537
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] 🏷  Local node identity is: 12D3KooWMLYf4LhUhyifnmYfBjDNf ULNwrf9LcpNCEYQp9xNawvf
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] 🧑‍🌾 Starting Subspace Authorship worker
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] 💻 Operating system: windows
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] 💻 CPU architecture: x86_64
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] 💻 Target environment: msvc
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] 📦 Highest known block at #315637
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] 〽️ Prometheus exporter started at 127.0.0.1:9615
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] Running JSON-RPC HTTP server: addr=127.0.0.1:9933, allowed origins=Some(["http://localhost:*", "http://127.0.0.1:*", "https://localhost:*", "https://127.0.0.1:*", "https://polkadot.js.org"])
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] Running JSON-RPC WS server: addr=127.0.0.1:9944, allowed origins=Some(["http://localhost:*", "http://127.0.0.1:*", "https://localhost:*", "https://127.0.0.1:*", "https://polkadot.js.org"])
←[2m2022-06-22 13:21:37←[0m [PrimaryChain] creating instance on iface 192.168.0.144
←[2m2022-06-22 13:21:37←[0m Accepting new connection, 1/100
←[2m2022-06-22 13:21:38←[0m [PrimaryChain] 🔍 Discovered new external address for our node: /ip4/77.40.48.234/tcp/30333/p2p/12D3KooWMLYf4LhUhyifnmYfBjDNfULNwrf9LcpNCEYQp9xNawvf

Error while building OpenCL program:
C:\Users\vyaly\AppData\Local\Temp\\OCL1668T1.cl:153:5: error: implicit declaration of function '__asm__' is invalid in C99
    __asm__("v_mul_lo_u32 %0, %1, %2"
    ^
C:\Users\vyaly\AppData\Local\Temp\\OCL1668T1.cl:154:18: error: expected ')'
                 : "=v"(z.w[0]) : "v"(x), "v"(y));
                 ^
C:\Users\vyaly\AppData\Local\Temp\\OCL1668T1.cl:153:12: note: to match this '('
    __asm__("v_mul_lo_u32 %0, %1, %2"
           ^
C:\Users\vyaly\AppData\Local\Temp\\OCL1668T1.cl:156:18: error: expected ')'
                 : "=v"(z.w[1]) : "v"(x), "v"(y));
                 ^
C:\Users\vyaly\AppData\Local\Temp\\OCL1668T1.cl:155:12: note: to match this '('
    __asm__("v_mul_hi_u32 %0, %1, %2"
           ^
C:\Users\vyaly\AppData\Local\Temp\\OCL1668T1.cl:160:12: error: overloaded function 'mad' must have the 'overloadable' attribute
inline u64 mad(u64 z, u32 x, u32 y)
           ^
c:\constructicon\builds\gfx\seven\21.30\stream\opencl\compiler\clc2\ocl-headers\build\wNow64a\B_rel\opencl12_builtins.h:11680:49: note: previous overload of function is here
half16 const_func __attribute__((overloadable)) mad(half16 a, half16 b, half16 c);
                                                ^
C:\Users\vyaly\AppData\Local\Temp\\OCL1668T1.cl:165:18: error: expected ')'
                 : "+v" (z), "=s" (junk) : "v" (x), "v" (y));
                 ^
C:\Users\vyaly\AppData\Local\Temp\\OCL1668T1.cl:164:12: note: to match this '('
    __asm__("v_mad_u64_u32 %0, %1, %2, %3, %0"
           ^
C:\Users\vyaly\AppData\Local\Temp\\OCL1668T1.cl:520:21: warning: initializing '__global uchar *' (aka '__global unsigned char *') with an expression of type 'const __global uchar *' (aka 'const __global unsigned char *') discards qualifiers
    __global uchar* iv = _iv + x * 32;
                    ^    ~~~~~~~~~~~~
1 warning and 5 errors generated.

error: Clang front-end compilation failed!
Frontend phase failed compilation.
Error: Compiling CL to IR

@i1i1
Copy link
Contributor

i1i1 commented Jun 22, 2022

@shuralemain this is a different issue, and it was fixed here autonomys/sloth256-189#29. It will land in the next snapshot.

Use our forum next time. Github is used for bug tracking.

@shuralemain
Copy link

@shuralemain this is a different issue, and it was fixed here subspace/sloth256-189#29. It will land in the next snapshot

Thanks!

@centrd
Copy link

centrd commented Jun 26, 2022

image
No CLI output on a Windows system with no OCL runtime installed. When trying to run via Explorer, OCL error shows.

@centrd
Copy link

centrd commented Jun 26, 2022

Gave it a runtime by installing Intel® CPU Runtime for OpenCL™ Applications for Windows* OS as a workaround. Seems to run now.
OpenCL should have been listed as a requirement on the release page.

@nazar-pc
Copy link
Member Author

@centrd that error seems unrelated to this issue, but it is useful anyway, we'll add it to docs.
We'll handle it either with code updates or with documentation changes, thanks!

@centrd
Copy link

centrd commented Jun 26, 2022

@centrd that error seems unrelated to this issue, but it is useful anyway, we'll add it to docs. We'll handle it either with code updates or with documentation changes, thanks!

Thanks. I wasn't sure and wanted to avoid a dup. The node seems to be running fine with the non-GPU OCL runtime that I installed, so that's good.

@nazar-pc
Copy link
Member Author

It ignores non-GPU runtimes, it seems like the issue is that OpenCL.dll needs to be present, doesn't matter how exactly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
4 participants