-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 4/26/2012 2:49 AM, John Morris wrote:
> Well, no solution yet, and only narrowed things a little bit:
> 
> Continuing Charles's work, I merged the bitmuster-patched v2.4.4 
> forward.  Whatever changes are causing the problem Charles
> describes were introduced between v2.4.7 and v2.5.0, and also
> between v2.5.0-pre0 and v2.5.0-pre1.
> 

Thanks for digging into this!

Looking at diffs between the versions above, I think the problem may
be related to the changes in the handling of mem_id, lib_mem_id, and
comp->mem_id in hal_init and elsewhere.

No smoking gun yet, but I had previously ignored these changes, as it
looked to me like the comp->mem_id was something added by bitmuster
for their shared memory area tests since it didn't exist in the
linuxcnc 2.5 codebase.  Looking at the linuxcnc diff from 2.5.0-pre0
to 2.5.0-pre1, however, I see that this is a linuxcnc change and did
not come from bitmuster.

I suspect something in the preempt-rt patches needs to be updated or
tweaked to account for this change, but I still don't understand the
code well enough to pinpoint what might need fixing.

- -- 
Charles Steinkuehler
char...@steinkuehler.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+ZfDYACgkQLywbqEHdNFwX9gCeJXuvLLocqO5aBiu0bDjNiRO6
HsIAoPzNwVxCYNyVlGen+5HWXXr9cUzu
=Nsof
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
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
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Reply via email to