Closed eliasbakken closed 2 years ago
Running stress --cpu 4
does not seem to affect the issue, so it might be misleading regarding the message that it is the host computer that is at fault.
Running the print at 1000% did not really affect the issue either. It seems more likely to be a bug in the code somewhere. Possibly due to the optimizations that have been committed lately.
It seems that the 2K dynpool might be the cause of the error. The standard implementation has 20 K. The dynpool is used for reserving memory for path segments, so a small dynpool will cause the number of path segments ready to use to be very small.
There was not really any room to expand the dynpool and also fit bl31 in the SRAM A2, so instead now the ar100/klipper binary is allowed to use 48 KB and then bl31 is written back in SRAM A2 when klipper is shut down. This should allow a graceful shutdown and reboot. This is a big change that allows more freedom in future firmware changes.
With the latest PR this seems to be solved. I'm running and print and marking it as solved if the print is OK. We can reopen if the problem persists.
Sometimes the print stops with the following message:
Here is an extraction from a typical settings:
I need help decifering what the issue could be. Nothing looks excessive at first glance.