Hi, Jan, now, the rtdev of eth1394 can be seen thru "rtifconfig" and an ip address can be given to it. But when I run "rtroute solicit" to add the local ip to the route table, it crashes and prints a message: "Default Trap Handler: Vector 14: Suspend RT task c804f7a0". The RT task here is born durng insmod the rtnet module. But it is not the RT task of stack manager. If I only load rtnet module, from /proc/rtai/scheduler, I will see two RT tasks: the RT task of stack manager which has priority 1 and the unknown RT task which has priority 1073741823. Do you have any idea where the unknown RT task comes from? Is it the low priority task for Linux?
Btw, since the rtos_tasklet_scheduler is also a RT task and it has a higher priority than stack manager, I give the rtos_tasklet_scheduler priority 1 and lower the stack manager to priority 2. Then I am still confused by the semaphore problem: when the rtos_tasklet_scheduler signals the semaphore, will it be preempted by stack manager? And, since the interrupt handler is preemptable by the RT task, which means when the RT task is running, the interrupt handler hasnt _return_ yet, then will it make no difference if I directly run the stack manager task in the interrupt handler? Best regards, Zhang Yuchen MSc Student Control Engineering Group University of Twente The Netherlands ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ RTnet-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/rtnet-developers
