I have a question about the code, If I am not mistaken , it binds to a specific cpu ?
I was under the impression that this was counter productive as far as latency for newer preempt TR systems ? I think you mentioned it before, but I am curious, also 'if' we get one of the newer kernels, neetwrking is not bound to a specific processor for a specific interface ... a patch google dropped in the kernel, think it was 2.6.37 or something like that .. It would be interesting to se what you get with a 'default' linux kernel ( 2.6.39 or 3.0-rc3 ) built with realtime enabled ... and without the cpu binding ... Anyhow it wil take a bit of time for me to look through everything. / regards, Lars Segerlund 2011/6/19 Michael Abel <michael.a...@isw.uni-stuttgart.de>: > > Hi Lars, > > I walked a bit trough the code and tried some things out. There is already > cleanup code to avoid this problem, but the cleanup works only when emc is > started as root. It seems just like a problem with permissions. I recommend > to start emc as root to avoid the problems. > > In case of problems it's also possible to remove the shm by hand with these > commands: > > ipcrm -M 0x48414c32 #(hal shm) > ipcrm -M 0x0000cafe #(shm interface) > > Can you please tell me more about the segfaulting shm_tester? I have no > problems with this program here... > Thanks! > > regards Michael > > "Lars Segerlund" <lars.segerl...@gmail.com> schrieb: >> I am seing the same thing, after running emc & your shm_tester a >> couple of times, ipcs gets some cruft, and I can not start emc again >> ... shm_tester segfaults .... >> >> Trying to investigate .... >> >> / regards Lars Segerlund >> >> 2011/6/18 Michael Abel <michael.a...@isw.uni-stuttgart.de>: >>> >>> Hello Guys, >>> >>> I probably found the problem, why you sometimes have to call halcmd as >>> root to get emc started again. But I don't have a bugfix up to now. >>> >>> It seems like the complete hal shared memory is not given back to the os >>> when emc is closed and my shm_tester is still running. For that reason > you >>> can still access the memory when emc has quit. When halcmd is started >>> from the root account, the memory is also still there, but its possible >>> to start emc again. >>> >>> This is printed after emc has quit: >>> >>> $ halcmd -V status >>> HAL: initializing component 'halcmd26165' >>> HAL: component 'halcmd26165' initialized, ID = 26165 >>> HAL locking status: >>> current lock value 0 (00) >>> HAL_LOCK_NONE - nothing is locked >>> HAL memory status >>> used/total shared memory: 48238/262000 >>> active/recycled components: 1/12 >>> active/recycled pins: 0/417 >>> active/recycled parameters: 0/65 >>> active/recycled aliases: 0/0 >>> active/recycled signals: 36/0 >>> active/recycled functions: 0/17 >>> active/recycled threads: 1/0 >>> HAL: removing component 26165 >>> HAL: component 26165 removed, name = 'halcmd26165' >>> >>> >>> One can also see that there is shared memory left with ipcs: >>> >>> ipcs -m -p | grep <old_pid_of_rtapi_app> >>> >>> Does somebody know, how the rtai version of emc is handling hal shared >>> memory? Is it still there after closing emc? >>> >>> Greetings, >>> Michael >>> >>> >>> >>> >>> > ------------------------------------------------------------------------------ >>> EditLive Enterprise is the world's most technically advanced content >>> authoring tool. Experience the power of Track Changes, Inline Image >>> Editing and ensure content is compliant with Accessibility Checking. >>> http://p.sf.net/sfu/ephox-dev2dev >>> _______________________________________________ >>> Emc-developers mailing list >>> Emc-developers@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/emc-developers >>> >> >> > ------------------------------------------------------------------------------ >> EditLive Enterprise is the world's most technically advanced content >> authoring tool. Experience the power of Track Changes, Inline Image >> Editing and ensure content is compliant with Accessibility Checking. >> http://p.sf.net/sfu/ephox-dev2dev >> _______________________________________________ >> Emc-developers mailing list >> Emc-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-developers >> > > > > ------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
