rtems_message_queue_receive problem with Multiprocessing

[Sylvain Jouanneau]

Hello,

I'm using RTEMS 4.0.0 in multiprocessing configuration with SPARC/ERC32.
In my Init task I create a global message queue using
rtems_message_queue_create.
A packet (MP_QUEUE_ANNOUNCE_CREATE) has to be sent to other nodes, so my
MPCI layer is called. It is based on an Ethernet driver which has servers to
send and receive packets. 
So when a packet has to be sent, MPCI layer waits for the end of sending and
uses a local message queue.
But when I call rtems_message_queue_receive for this local queue with
RTEMS_WAIT it returns RTEMS_SUCCESSFUL immediately and before the call of
rtems_message_queue_send.
I can't understand why it doesn't work because when I try to send a packet
directly using my MPCI layer it works.
I suspected a problem with task mode but it is the same when it works and
when it doesn't.

I saw that somebody had problems with this directive in multiprocessing
configuration but with RTEMS_NO_WAIT option and no solution is given.

Have you an idea?

Sylvain JOUANNEAU

-------------- next part --------------

Le pr?sent message et ses pi?ces jointes sont confidentiels et exclusivement destin?s ? la personne ou aux personnes vis?e(s) ci-dessus. 
Il peut contenir des informations privil?gi?es, confidentielles ou autres, qui ne peuvent ?tre divulgu?es. 
Si vous avez re?u ce message par erreur, veuillez contacter imm?diatement l'exp?diteur et effacer le message de votre syst?me sans en faire de copie.
Vous n'?tes pas autoris?(s) ? faire un quelconque usage de son contenu, ni le diffuser, ni en prendre aucune copie, ?lectronique ou autre.

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
It may constitute information that is privileged or confidential or otherwise legally exempt from disclose.
If you have received this email in error, please contact the sender and delete the email from your system without copying it.
You are not authorized to read, copy or disseminate this message or any part of it.