It seems that minstant triggered panic

[phantom-rabbit]

[Stebalien]

• What CPU?
• Does this happen immediately, frequently?

[phantom-rabbit]

[phantom-rabbit]

Executing any command will trigger this log

[Stebalien]

Ok... And this is linux?

[Stebalien]

Hm. So, it looks like setting the CPU affinity isn't working and minstant is panicing. What kernel version is this?

[Stebalien]

And have you configured any limits on scheduling, CPU affinity, etc.?

[phantom-rabbit]

And have you configured any limits on scheduling, CPU affinity, etc.?

I'm not sure, what commands can I check?

[Stebalien]

I'm not sure, what commands can I check?

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:

   EINVAL The  affinity bit mask mask contains no processors that are cur‐
          rently physically on the system and permitted to the thread  ac‐
          cording  to  any  restrictions  that  may  be  imposed by cpuset
          cgroups or the "cpuset" mechanism described in cpuset(7).

   EINVAL (sched_getaffinity() and, before  Linux  2.6.9,  sched_setaffin‐
          ity())  cpusetsize is smaller than the size of the affinity mask
          used by the kernel.