emc crashes after 2.4.7 update

More
19 Oct 2011 17:23 #14059 by lumberjack_jeff
This is a new problem. EMC2 splash screen comes up, then this debug screen.

I updated emc2 to 2.4.7 this AM.

Print file information:
RUN_IN_PLACE=no
EMC2_DIR=
EMC2_BIN_DIR=/usr/bin
EMC2_TCL_DIR=/usr/share/emc/tcl
EMC2_SCRIPT_DIR=
EMC2_RTLIB_DIR=/usr/realtime-2.6.32-122-rtai/modules/emc2
EMC2_CONFIG_DIR=
EMC2_LANG_DIR=/usr/share/emc/tcl/msgs
INIVAR=inivar
HALCMD=halcmd
EMC2_EMCSH=/usr/bin/wish8.5
EMC2 - 2.4.6
Machine configuration directory is '/home/jeff/emc2/configs/improv'
Machine configuration file is 'improv.ini'
INIFILE=/home/jeff/emc2/configs/improv/improv.ini
PARAMETER_FILE=emc.var
EMCMOT=motmod
EMCIO=io
TASK=milltask
HALUI=halui
DISPLAY=axis
NML_FILE=
Starting EMC2...
Starting EMC2 server program: emcsvr
Loading Real Time OS, RTAPI, and HAL_LIB modules
Starting EMC2 IO program: io
Starting HAL User Interface program: halui
Starting EMC2 TASK program: milltask
Starting EMC2 DISPLAY program: axis
Shutting down and cleaning up EMC2...
Killing task emcsvr, PID=1337
Killing task milltask, PID=1383
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments
Cleanup done

Debug file information:
Unrecognized line skipped: POC FMS LEN DIAM COMMENT
X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 153 (GLX)
Minor opcode of failed request: 17 (X_GLXVendorPrivateWithReply)
Serial number of failed request: 544
Current serial number in output stream: 544
1337
PID TTY STAT TIME COMMAND
1383
PID TTY STAT TIME COMMAND
Stopping realtime threads
Unloading hal components

Kernel message information:
[ 44.182310] I-pipe: Domain RTAI registered.
[ 44.182337] RTAI[hal]: <3.8.1> mounted over IPIPE-NOTHREADS 2.6-03.
[ 44.182343] RTAI[hal]: compiled with gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) .
[ 44.182357] RTAI[hal]: mounted (IPIPE-NOTHREADS, IMMEDIATE (INTERNAL IRQs DISPATCHED), ISOL_CPUS_MASK: 0).
[ 44.182362] PIPELINE layers:
[ 44.182369] dca40e20 9ac15d93 RTAI 200
[ 44.182374] c085cb20 0 Linux 100
[ 44.265724] RTAI[malloc]: global heap size = 2097152 bytes, <BSD>.
[ 44.266305] RTAI[sched]: IMMEDIATE, MP, USER/KERNEL SPACE: <with RTAI OWN KTASKs>, kstacks pool size = 524288 bytes.
[ 44.266319] RTAI[sched]: hard timer type/freq = APIC/6228910(Hz); default timing: periodic; linear timed lists.
[ 44.266327] RTAI[sched]: Linux timer freq = 250 (Hz), TimeBase freq = 1295573000 hz.
[ 44.266333] RTAI[sched]: timer setup = 999 ns, resched latency = 2943 ns.
[ 44.266618] RTAI[usi]: enabled.
[ 44.507618] RTAI[math]: loaded.
[ 44.891918] config string '0x378 out '
[ 50.493251] RTAI[math]: unloaded.
[ 50.660342] SCHED releases registered named ALIEN RTGLBH
[ 50.679368] RTAI[malloc]: unloaded.
[ 50.776026] RTAI[sched]: unloaded (forced hard/soft/hard transitions: traps 0, syscalls 0).
[ 50.787965] I-pipe: Domain RTAI unregistered.
[ 50.787987] RTAI[hal]: unmounted.

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

More
19 Oct 2011 18:03 #14063 by BigJohnT
lumberjack_jeff wrote:

Unrecognized line skipped: POC FMS LEN DIAM COMMENT


Check to see if you have a tool.tbl file in your config directory.

John

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

More
19 Oct 2011 18:40 - 19 Oct 2011 18:51 #14064 by lumberjack_jeff
I do, in jeff/emc2/configs/<machinename>

although I don't use it.


POC FMS LEN DIAM COMMENT

1 1 0.0 0.125 first tool
2 2 0.0 0.25
3 3 0.0 0.119 for use when inlaying
4 4 0.0 1.0
5 5 0 0.5
32 32 0.0 0.0 last tool

is it wrong?

Based on advice I got from IRC, I downgraded the x server, now it works.

(JT is that you?)
Last edit: 19 Oct 2011 18:51 by lumberjack_jeff.

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

More
19 Oct 2011 20:12 - 19 Oct 2011 20:14 #14065 by BigJohnT
Yes, it is me :)

I had a problem with my plasma where I had an entry for a tool table but no file. I just removed the TOOL_TABLE= line from the ini file.

I think I had the same error as you

Unrecognized line skipped: POC FMS LEN DIAM COMMENT


John
Last edit: 19 Oct 2011 20:14 by BigJohnT.

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

More
19 Oct 2011 21:33 #14066 by skunkworks
Run the update manager in Ubuntu again. There just happened to be an update from Ubuntu that broke X today (or yesterday). There should be a fix now in the Ubuntu update manager.

sam

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

Time to create page: 0.088 seconds
Powered by Kunena Forum