-
Notifications
You must be signed in to change notification settings - Fork 736
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
panics on darwin arm #803
Comments
I wonder if Tendermint makes some running architecture assumptions... What Go version are you compiling with? Could you post the complete stack trace? |
I do not have an M1 yet but have run a bunch of chains on arm64 Linux. Arm64 Linux works quite well and so I bet that it is an issue with macos. If you sent me a DM on twitter, I would be super happy to do a google meet + screenshare. I've never seen anything like that segfault before. Interesting. |
I have a m1, I run Tendermint all the time on my machine for testing. Will test gaia shortly |
I used two separate config files. One that was previously generated and one that was newly generated the old one works and the new comes with the same errors. @shahankhatch was there any sort of change that could cause this? |
@marbar3778 could you post the files? I'm specifically interested in the database backend and possibly the indexer. |
It works when I compile with the command below and set the database to badgerdb: This is the default command generated by
This is off tag v4.2.0. |
@marbar3778 Aside from sdk/tm version bumps, and some Makefile, doc and Docker updates, Gaia itself hasn't had changes that seem to impact building on an M1. |
@shahankhatch correct. It builds just fine, but well, I wanted to confirm and I love toys so I picked up one of these M1 MBP's. Can fully confirm @mangas issue.
|
@mangas I don't know the "why" of this, but build it with the badgerdb flag and it should run fine. PS: Actually it runs fine for about 5 minutes, and then it crashes in a different way. |
Thank you, it's helpful to know that we now have three confirmed. Rpi works great... So now I'm very curious why the Jetson does not work. |
@litvintech Do you have a raspberry pie model 4? I think you would find that works on the RPI but not M1 ...which is weird... |
@faddat I think that RPi is too slow compared to others and that's why the chain is not halted. On M1 chain stop sync in less than 30 seconds, on Xavier it stops in around 1 min and a couple of minutes on Nano. (approx time as I remembered as tested 2 months ago) Anyway, I cannot understand is it a general problem cause there is not enough reports. Does nobody run gaia and their chains on ARMs? |
I have successfully run the latest gaia on ARM (raspi) but I moved my office and don't have one up on the latest version. Trying on my AWS graviton node now. |
It doesn't work on my graviton either. As soon as I have a raspberry pie up I will test that but I believe that we are dealing with an ecosystem wide regression that prevents us from running on ARM CPUs |
4.1.0 may resolve it, I know I've run the most recent gaia on pi ✔️ 4.1.0 works on arm64, bet it also works on M1. @litvintech random thought: move your libs back to the cosmos-sdk version in 4.1.0, bet that works. |
@faddat I tested with the current dev branch of cyber that was upgraded to cosmos-sdk v42 (same as gaia 4.1.0). Will check again soon as will finish the upgrade to cosmos-sdk v43 |
That's interesting, thank you. I'll track what other libraries and stuff changed as I do so enjoy running my chains on arm. |
fixed the issue here cosmos/cosmos-sdk#9345 |
this is fixed with https://github.com/cosmos/cosmos-sdk/releases/tag/v0.42.5. Gaia needs a release to fix it |
Resolved and safe to close. |
bump re: safe to close. |
Summary of Bug
Following the docs on mac arm (apple m1) causes a panic. The same instructions work on amd64.
I'm happy to help look into it if anyone is available to pair on it, I'll have a look in meantime but some guidance would appreciated.
Version
v4.2.0
Steps to Reproduce
For Admin Use
The text was updated successfully, but these errors were encountered: