-
Notifications
You must be signed in to change notification settings - Fork 138
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
It seems that minstant triggered panic #1777
Comments
|
Executing any command will trigger this log |
Ok... And this is linux? |
Hm. So, it looks like setting the CPU affinity isn't working and minstant is panicing. What kernel version is this? |
And have you configured any limits on scheduling, CPU affinity, etc.? |
If you haven't explicitly configured any, the answer is likely no. It would likely be configured inside the systemd service file (if any). The other interesting part is that you have two numa nodes. But that shouldn't matter either. Given the EINVAL error, the relevant errors should be one of:
|
The text was updated successfully, but these errors were encountered: