Providing an update on Cargo builds cause system lockup

I'm only entering this update as a separate post because for some reason the forum software wants me to; it says so in the instructions at the bottom of the other page.

The suggestion in that thread of turning off incremental compilation seemed to do nothing. I set incremental = false under [profile.dev] in the workspace root Cargo.toml; I assume it propagates through the workspace. The system continued to lock up.

Today I'm here to report another failed attempt: I had a hypothesis that the issue was caused by kcryptd work queues being flooded - for background on this, see Speeding up Linux disk encryption - but even after adding ,no-write-workqueue,no-read-workqueue to the end of the relevant line in /etc/crypttab, updating initramfs, and rebooting, I still observed no change.

Despite both of these attempted fixes, Cargo still freezes the system, requiring me to forcibly power it off by holding the power button, after maybe 5 or 10 compilations of my project. Putting the project on a spinning-metal external drive seems to reduce the frequency and severity of lockups, but doesn't really fix the issue, and causes builds to take significantly longer.

Not much news, but thought I should at least share what didn't work.

1 post - 1 participant

Read full topic