LinuxCNC / linuxcnc

LinuxCNC controls CNC machines. It can drive milling machines, lathes, 3d printers, laser cutters, plasma cutters, robot arms, hexapods, and more.
http://linuxcnc.org/
GNU General Public License v2.0
1.8k stars 1.15k forks source link

Crash to desktop on hitting cycle start #2589

Closed mdkendall closed 1 year ago

mdkendall commented 1 year ago

LinuxCNC installed on HP Prodesk 800 G2 from LinuxCNC 2.8.4 Debian 10 Buster PREEMPT-RT ISO, controlling a 3040Z-DQ mill via a parallel port card. Installed and configured in May, has been working fine since then.

This morning I opened a .nc file as usual and hit the cycle start button, LinuxCNC closed and dropped me to the desktop, and a crash report was produced. On restarting the program (and re-homing the machine) everything works again without issue.

Here are the steps I follow to reproduce the issue:

This is what I expected to happen:

This is what happened instead:

It worked properly before this:

Information about my hardware and software:

Crash report is attached. linuxcnc.report.txt

andypugh commented 1 year ago

There is nothing in the report that I can interpret as saying what went wrong.

We see: "can't do that (EMC_TRAJ_SET_TELEOP_ENABLE) in auto mode with the interpreter waiting" (which is a little mysterious, and has been seen before, but the cause hasn't been determined as far as I recall)

And also "X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 15 (X_QueryTree) Resource id in failed request: 0x2d216d8 Serial number of failed request: 6297929639 Current serial number in output stream: 6297929639"

Which normally indicates a problem with the windowing system.

Perhaps you could start LinuxCNC from the command line (command "linuxcnc") and compare the output there to what is seen during the crash dump. Anything that is different is suspicious.

mdkendall commented 1 year ago

Thanks for looking at this.

The machine had been up with LinuxCNC running for about two months before the crash, so I'm not sure if any errors in that log were associated with today's issue, or were historic. Since the issue is not reproducible (it has run a few jobs today since the crash with no problems) I'm not sure I can do much to debug.

Feel free to close this issue. I will keep an eye on it and re-open if it happens again.

andypugh commented 1 year ago

Closing pending repeat of issue.