-
Notifications
You must be signed in to change notification settings - Fork 144
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
Realm: gex CRC MISMATCH #1779
Comments
Could you please get a backtrace? |
I cant seem to get backtraces with a debug build and |
Could you please try |
Here is a stacktrace in debug: http://sapling2.stanford.edu/~seshu/xcsl1028423/backtrace.txt |
It says 404 Forbidden for me. Can I get access? |
Try it now. |
This is probably the relevant stack trace:
|
worked! thanks Seshu |
The backtrace doesn't look like it is from a CRC check. Looks like is coming from this error message: That's probably a bug in Realm where it is trying to send a medium active mssage where it needs to switch to sending a long active message. It probably also explains the CRC check failure on the far side because only some of the payload makes it across in release mode. |
I think it is the gasnet version of issue #1769. I am surprised that the limit is only 8K
|
I agree that is a likely cause of the problem. |
The medium AM size can be set with Don't even need to rebuild, it's just an environment variable. We've seen this issue before: #1449 and #1229 are both variations on this same issue. |
The CRC error goes away in release by setting I just see gasnet abnormal exit. Here is a stack trace:
Will try to get a stacktrace in debug. |
I'm seeing the following error at shutdown when running cunumeric on Perlmutter:
The text was updated successfully, but these errors were encountered: