Gentle persons: I've been experimenting with the results of the hard work of Charles Steinkuehler, John Morris (and others whose names I confess I've forgotten at the moment) to get LinuxCNC running over the preempt_rt kernel.
I seem to be able to create a zombie hal configuration. System: ASUS AT5NM10-I motherboard, 2-cpu Atom, 2 GB ram, Debian Wheezy, 3.2.0-3-rt-686-pae kernel, LinuxCNC 2.6.0~pae, gdm (and X-server) killed, running headless to a remote X-server. Symptom: Start up latency-test; kill it rudely 1) by a ctrl-c at an some inopportune moment, after which it may die gracefully or it may become a zombie or 2) by closing the terminal window I invoked it from, after which it seems reliably to become a zombie What do I mean zombie? Well, a "halcmd show" shows that the hal configuration didn't get cleaned up. All the components are still loaded and wired up and the two threads still exist. Trying to invoke "latency-test" a second time gets me a string of error messages all to the point that I'm trying to duplicate stuff already loaded and also introducing a new message that comes from the preempt_rt work: "could not find cpusetfs mount point." I can't seem to kill this hal configuration by the usual methods as an ordinary user even though I started latency-test as myself. The only method I got to work was to invoke halrun as root: "sudo scripts/halrun -U". Any comments???? Regards, Kent ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
