LinuxCNC started in error mode

More
19 Jul 2026 02:44 #347831 by DMoneyAllstar
LinuxCNC started in error mode was created by DMoneyAllstar
Running CommandCNC on Linux. I've had this system since 2017, but the mini PC is 3-4yr newer. Everything worked fine 3wk ago. Machine is in an air-conditioned shop.

Was setting up a run, zero'd my XYZ, loaded my file, and pressed Run. The torch made the first pierce but sat there without any XY motion. Air flow shut off a few seconds later. Recreated the .tap file a couple times with same result when running. When I rebooted and restarted CommandCNC, I got an error message for LinuxCNC. No matter what I do, I can't get out of this loop.

I saved the error message ZIP file. What do I do with it?

I pasted the error message in AI and it told me there's a idle-wait setting that I need to delete. Does this sound normal?

Can I boot with my factory files on the original USB and get around it?

Thanks,
Dan


PS: here is what AI is telling me to do based on the error message:

Your log output reveals a specific configuration issue right at the start of your boot line.
text
[ 0.000000] Malformed early option 'idle'
Use code with caution.

The Cause
Your Linux kernel parameters are fighting with each other. Look closely at your GRUB command line options from the log:
... isolcpus=1 idle=mwait intel_idle.max_cstate=1 ...
The argument idle=mwait is invalid (malformed) for this kernel architecture. Furthermore, explicitly forcing idle=mwait overrides and conflicts with intel_idle.max_cstate=1, which is the crucial setting LinuxCNC needs to stop the Intel CPU from falling into deep power-saving sleep states (which ruin real-time latency).

How to Fix It
You need to edit your GRUB boot configuration to remove the bad option and fix the kernel parameters.
Step 1: Temporarily edit GRUB to test the fix
Reboot your PC.
As it turns on, hold or tap the Shift key (or Esc) to bring up the GRUB boot menu.
Use the arrow keys to highlight your normal PREEMPT-RT kernel option and press e to edit it.
Locate the line starting with linux /boot/vmlinuz...
Move your cursor and completely delete idle=mwait from that line.
Press Ctrl+X or F10 to boot.

Please Log in or Create an account to join the conversation.

More
19 Jul 2026 02:53 #347832 by tommylight
Replied by tommylight on topic LinuxCNC started in error mode


Was setting up a run, zero'd my XYZ, loaded my file, and pressed Run. The torch made the first pierce but sat there without any XY motion. Air flow shut off a few seconds later. Recreated the .tap file a couple times with same result when running. When I rebooted and restarted CommandCNC, I got an error message for LinuxCNC. No matter what I do, I can't get out of this loop.

LinuxCNC does not use .tap files, so what gives?

Please Log in or Create an account to join the conversation.

More
19 Jul 2026 04:47 - 19 Jul 2026 04:50 #347833 by NWE
Replied by NWE on topic LinuxCNC started in error mode

Running CommandCNC on Linux.

 

I believe you might want to contact CandCNC tech support.
Last edit: 19 Jul 2026 04:50 by NWE. Reason: editor

Please Log in or Create an account to join the conversation.

More
19 Jul 2026 08:21 #347837 by rodw
Replied by rodw on topic LinuxCNC started in error mode
Most people on this forum in your position have ditched CommandCNC and moved to QTplasmac with a Mesa THCAD to measure torch voltage and let Linuxcnc manage the THC function internally.

Please Log in or Create an account to join the conversation.

Time to create page: 0.355 seconds
Powered by Kunena Forum