Re: [RTnet-developers] ETH_P_ALL feature

[Jorge A. <j-a...@cr...>]

Hello Jan.

Regarding the problem we discuss some time ago, it still remains.

I have until now found the origin of the problem.

Theres no RX interruption handled in any of the boards that should receive the messages.

Thats why the stack_mgr_task never wakes up from the event.

I'm using the rt_8139too driver that cames with rtnet.

I've done some roll back in rtnet and RTAI and nothing:
Rtnet until version 1069
RTAI magma until RTAI-3.4-test1

Maybe can be anything related with RTDM and the interrupt handling.

Jorge



Em Segunda, 9 de Outubro de 2006 13:59, o Jan Kiszka escreveu:
> Jan Kiszka wrote:
> > Jorge Almeida wrote:
> >> I putthe following rtdm_printk functions in this function and the 
> >>
> >> rtdm_printk("\tEvent occured\n");
> >>
> >> never is doner when a send messages to the receiveing network.
> > 
> > Is rtdm_event_signal called appropriately?
> > 
> >> I don't know why.
> >>
> >> static void rt_stack_mgr_task(void *arg)
> >> {
> >>     rtdm_event_t            *mgr_event = &((struct rtnet_mgr *)arg)->event;
> >>     struct rtskb            *rtskb;
> >>
> >>     rtdm_printk("\tArrive to the rt_stack_mgr_task function\n");
> >>     while (rtdm_event_wait(mgr_event) == 0) {
> >>         /* we are the only reader => no locking required */
> >>         rtdm_printk("\tEvent occured\n");
> >>         while ((rtskb = __rtskb_fifo_remove(&rx.fifo)))
> >>         {
> >>             rtdm_printk("\trtskb removed from fifo\n");
> >>             rt_stack_deliver(rtskb);
> >>             rtdm_printk("\trtskb delivered\n");
> >>         }
> >>     }
> >>     rtdm_printk("\tGoing out from rt_stack_mgr_task function\n");
> >> }
> >>
> >> The first 
> >>
> >> rtdm_printk("\tArrive to the rt_stack_mgr_task function\n");
> >>
> >> and the last
> >>  rtdm_printk("\tGoing out from rt_stack_mgr_task function\n");
> >>
> >> are done in the starting and at the end of rtnet.
> > 
> > ...but there is no entry in the RTAI task list under /proc like it used to?
> > 
> >> Any clues??
> > 
> > Back to my other suggestion: try older versions of RTnet SVN and RTAI
> > until you find a working combination. Then try to narrow down the change
> > that causes this.
> > 
> 
> Any news on this? I would like to nail down remaining issues in order to
> roll out a new release within, say, a week.
> 
> Jan
> 
> 

-- 
Jorge Almeida
j-a...@cr...
DISCLAIMER: This message may contain confidential information or privileged material and is intended only for the individual(s) named. If you are not a named addressee and mistakenly received this message you should not copy or otherwise disseminate it: please delete this e-mail from your system and notify the sender immediately. E-mail transmissions are not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete or contain viruses. Therefore, the sender does not accept liability for any errors or omissions in the contents of this message that arise as a result of e-mail transmissions. Please request a hard copy version if verification is required. Critical Software, SA.