You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Intel Xeon E5-2690 v3 & Intel Xeon E5-2698 v3 & Intel Core Processor (Haswell, no TSX) : getting Platform errors during update to Platform v1.8.0
These errors clear when switching Drive ABCI to v1.7.1 (tested on my Intel Xeon E5-2698 v3)
dashmate config set platform.drive.abci.docker.image dashpay/drive:1.7.1
dashmate restart --platform
These errors also clear when using Platform v1.8.1 dev debug build, successfully tested by Discord user CoinRider on his Intel Xeon E5-2690 v3 and user pmbf on Intel Core Processor (Haswell, no TSX) / Intel® Core™ i5-4460 Processor.
dashmate config set platform.drive.abci.docker.image dashpay/drive:1.8.1-dev.1-debug
dashmate restart --platform
Expected my cpu Intel Xeon E5-2698 v3 with Instruction Set Extension Intel® AVX2 to not form a problem updating to Platform v1.8.0 because :
https://github.com/dashpay/platform/releases/tag/v1.8.0 does not state any cpu hardware requirement changes that Evonodes need to comply to (only upcoming change will be a conformity to x86-64-v3 in Platform v1.9.0 which Intel Xeon E5-2690 v3 & Intel Xeon E5-2698 v3 fully support)
So i can only conclude this is an unexpected bug, that needs to be further investigated.
I already did some extensive investigation into this bug with Ivan Shumkov, who received my logs that were produced by dashmate doctor report. My VPS provider switched me from Intel Xeon E5-2698 v3 (AVX2) to an Intel Xeon Gold 6138 (AVX-512), before i could test the Platform 1.8.1 dev build with him. I later switched my VPS to Intel Xeon Gold 6150 that has even more Instruction Set Extensions then the Intel Xeon Gold 6138.
To consider
Either DCG inform Evonode operators that cpu's having just Instruction Set Extension Intel® AVX2 are no longer compatible with Platform update 1.8.0 and beyond, that Platform require Intel® AVX-512 and that they will need to use a dev build from now on that strips Instruction Set Extension Intel® AVX2 completely, possibly degrading their Evonode performance .. or this is a bug that needs to be confirmed and fixed by Platform team.
qwizzie
changed the title
[BUG] CPU's with just Instruction Set Extension Intel® AVX2 incompatible with Platform v1.8.0, needs Intel® AVX512
[BUG] CPU's with just Instruction Set Extension Intel® AVX2 incompatible with Platform v1.8.0, needs Intel® AVX512 it seems
Jan 26, 2025
qwizzie
changed the title
[BUG] CPU's with just Instruction Set Extension Intel® AVX2 incompatible with Platform v1.8.0, needs Intel® AVX512 it seems
[BUG] CPU's with just Instruction Set Extension Intel® AVX2 incompatible with Platform v1.8.0, require Intel® AVX512 ?
Jan 26, 2025
Intel Xeon E5-2690 v3 & Intel Xeon E5-2698 v3 & Intel Core Processor (Haswell, no TSX) : getting Platform errors during update to Platform v1.8.0
These errors clear when switching Drive ABCI to v1.7.1 (tested on my Intel Xeon E5-2698 v3)
dashmate config set platform.drive.abci.docker.image dashpay/drive:1.7.1
dashmate restart --platform
These errors also clear when using Platform v1.8.1 dev debug build, successfully tested by Discord user CoinRider on his Intel Xeon E5-2690 v3 and user pmbf on Intel Core Processor (Haswell, no TSX) / Intel® Core™ i5-4460 Processor.
dashmate config set platform.drive.abci.docker.image dashpay/drive:1.8.1-dev.1-debug
dashmate restart --platform
Intel Xeon E5-2690 v3 (Discord user CoinRider)
According Intel info (https://www.intel.com/content/www/us/en/products/sku/81713/intel-xeon-processor-e52690-v3-30m-cache-2-60-ghz/specifications.html) this cpu has Instruction Set Extension Intel® AVX2 only !
Intel Xeon E5-2698 v3 (Discord user qwizzie)
According Intel info (https://www.intel.com/content/www/us/en/products/sku/81060/intel-xeon-processor-e52698-v3-40m-cache-2-30-ghz/specifications.html) this cpu has Instruction Set Extension Intel® AVX2 only !
Intel Core Processor (Haswell, no TSX - Discord user pmbf) : according ChatGPT this is most likely the Intel® Core™ i5-4460 Processor
According Intel info (https://www.intel.com/content/www/us/en/products/sku/80817/intel-core-i54460-processor-6m-cache-up-to-3-40-ghz/specifications.html) this cpu has Instruction Set Extensions Intel® SSE4.1, Intel® SSE4.2, Intel® AVX2
I then tested Platform v1.8.0 on two other cpu models that my VPS provider switched me to :
Intel Xeon Gold 6138 : no issue running Platform v1.8.0
According Intel info (https://www.intel.com/content/www/us/en/products/sku/120476/intel-xeon-gold-6138-processor-27-5m-cache-2-00-ghz/specifications.html) this cpu has Instruction Set Extension Intel® AVX-512 only !
Intel Xeon Gold 6150 : no issue running Platform v1.8.0
According Intel info (https://www.intel.com/content/www/us/en/products/sku/120490/intel-xeon-gold-6150-processor-24-75m-cache-2-70-ghz/specifications.html) this cpu has Instruction Set Extensions Intel® SSE4.2, Intel® AVX, Intel® AVX2, Intel® AVX-512
Expected Behavior
Expected my cpu Intel Xeon E5-2698 v3 with Instruction Set Extension Intel® AVX2 to not form a problem updating to Platform v1.8.0 because :
https://github.com/dashpay/platform/releases/tag/v1.8.0 does not state any cpu hardware requirement changes that Evonodes need to comply to (only upcoming change will be a conformity to x86-64-v3 in Platform v1.9.0 which Intel Xeon E5-2690 v3 & Intel Xeon E5-2698 v3 fully support)
So i can only conclude this is an unexpected bug, that needs to be further investigated.
I already did some extensive investigation into this bug with Ivan Shumkov, who received my logs that were produced by dashmate doctor report. My VPS provider switched me from Intel Xeon E5-2698 v3 (AVX2) to an Intel Xeon Gold 6138 (AVX-512), before i could test the Platform 1.8.1 dev build with him. I later switched my VPS to Intel Xeon Gold 6150 that has even more Instruction Set Extensions then the Intel Xeon Gold 6138.
To consider
Either DCG inform Evonode operators that cpu's having just Instruction Set Extension Intel® AVX2 are no longer compatible with Platform update 1.8.0 and beyond, that Platform require Intel® AVX-512 and that they will need to use a dev build from now on that strips Instruction Set Extension Intel® AVX2 completely, possibly degrading their Evonode performance .. or this is a bug that needs to be confirmed and fixed by Platform team.
Your Environment
The text was updated successfully, but these errors were encountered: