Slobodan Matic wrote:
> On Sat, Nov 8, 2008 at 1:30 PM, Jan Kiszka <[EMAIL PROTECTED]> wrote:
> 
>> Please generate pcap files (tcpdump -w). They can be read by Wireshark -
>> and even interpreted (Wireshark has RTnet support). You can try the
>> same, of course.
> 
> 
> Hi Jan,
> Ok, I generated the files with the -w option (attached MndMS from master and
> SndMS from slave). I also tried to analyze the files with Wireshark.

Analysis can be easier if you only trace on rteth0, not on all
interfaces. That excludes unrelated noise and avoids duplications due to
rtmac capturing interfaces.

> The files show that, as expected, the following messages are sent/received:
> Stage 1 Config, New Announce, Stage 2 Config, Acknowledge, Ready (M), Ready
> (S).
> The master then just continues with a sequence of Synchronisation messages
> and, after some time, it also sends a Dead Station message.
> Then the entire cycle of messages is repeated. The files show two such
> cycles.

OK, so the slave does not see any packets, not even sync frames after
the final rtcfg ready message. But the master tries to send out those
frames. Strange. Though I have a vague feeling that I've faced such an
effect long time ago as well - but it's only a feeling, no idea what
might have been the reason.

> The similar traces are generated if a hub is used instead of a switch.
> Any hint? Thanks.

I think you now have to look into what happens on the master after the
ready, but before out-of-rtskb is detected. Is the driver code that
issues the packet actually executed? Are interrupts still coming in from
the NIC?

You may use good old printk for it, or (less messy) the ipipe tracer.
See http://www.xenomai.org/index.php/I-pipe:Tracer for more details. A
possible trace pattern could be to trigger on a function that is only
executed after the final ready (=>/proc/ipipe/trace/trigger) and set
appropriately large post_trace_points. Such trace can also nicely be
discussed here (the storm of information may not immediately be
interpretable).

Jan

Attachment: signature.asc
Description: OpenPGP digital signature

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to