I'm porting the ns9xxx-eth.c network driver to RTnet, but I'm getting a
"Xenomai: suspending kernel thread" exception in RTcfg in slave mode. In
Master mode, the driver appears to load fine and it floods the network with
healthy dose of TDMA messages (about 200 packets per second). I have yet to
verify that another machine can connect to it, but that may be due to issues
with the test PC.
However, while running in Slave mode the driver appears to fail while
connecting to the master (or possibly while looking for it). The output is
listed below. I searched the mailing lists but I haven't found this type of
exception happening within one of the RTnet modules.
This seems like a configuration issue since the wireshark output shows what
appear to be bash script variables not being populated: $IPADDR, $TDMACFG,
etc. The strange thing is that I'm also seeing the same output from my test
PC running rt_8139too. I've posted wireshark captures from an impartial
third-party PC.
Any help would be greatly appreciated.
Thanks,
- James
-------------
RTnet: 0.9.11
Xenomai: 2.4.10
I-Pipe: 1.12-05
Linux: 2.6.28.10 (a patched variant thereof)
Platform: ns9xxx (yes, that arm9)
-------------
# ./rtnet start
*** RTnet 0.9.11 - built on Dec 2 2009 11:59:51 ***
RTnet: initialising real-time networking
ns9xxx-eth-mii: probed
RTnet: registered rteth0
ns9xxx-eth ns9xxx-eth: rteth0 at MMIO c28a0000
Digi NS9XXX RTnet Ethernet driver
initializing loopback...
RTnet: registered rtlo
RTcfg: init real-time configuration distribution protocol
RTmac: init realtime media access control
RTmac/TDMA: init time division multiple access control mechanism
Stage 1: searching for master...link up (100/full)
Xenomai: suspending kernel thread bf035be8 ('rtcfg-rx') at 0xc00269f8 after
exception #0
RTnet: no one cared for packet with layer 3 protocol type 0x0004
RTnet: no one cared for packet with layer 3 protocol type 0x0004
RTnet: no one cared for packet with layer 3 protocol type 0x0004
RTnet: no one cared for packet with layer 3 protocol type 0x0004
RTnet: no one cared for packet with layer 3 protocol type 0x0004
...
[ctrl+c still exits to the console, but the device stops trying to connect]
---------------
rt_ns9xxx-eth - TDMA Sync packet (captured with Wireshark):
0000 ff ff ff ff ff ff 00 04 f3 ff ff fa 90 21 00 01 ........ .....!..
0010 02 00 02 01 00 00 00 00 0a 95 00 00 00 00 00 00 ........ ........
0020 00 00 00 00 00 06 ac 1d 2d 6b 00 00 00 00 00 00 ........ -k......
0030 00 00 00 00 00 00 00 00 00 00 00 00 ........ ....
rt_ns9xxx-eth - RTcfg Stage 1 Config packet (captured with Wireshark):
0000 ff ff ff ff ff ff 00 04 f3 ff ff fa 90 22 00 01 ........ ....."..
0010 0a 65 01 ea 0a 65 01 7e 04 00 42 24 54 44 4d 41 .e...e.~ ..B$TDMA
0020 43 46 47 20 72 74 65 74 68 30 20 73 6c 6f 74 20 CFG rtet h0 slot
0030 30 20 32 30 30 3b 69 66 63 6f 6e 66 69 67 20 76 0 200;if config v
0040 6e 69 63 30 20 75 70 20 24 49 50 41 44 44 52 20 nic0 up $IPADDR
0050 24 4e 45 54 4d 41 53 4b 5f 4f 50 54 0a $NETMASK _OPT.
---------------
PC with rt_8139too - TDMA Sync packet (captured with Wireshark):
0000 ff ff ff ff ff ff 00 30 ab 02 87 df 90 21 00 01 .......0 .....!..
0010 02 00 02 01 00 00 00 01 bb bd 11 7b 84 7d 52 76 ........ ...{.}Rv
0020 e6 db 11 7b 84 7d 52 76 e3 b1 20 73 6c 6f 74 20 ...{.}Rv .. slot
0030 30 20 32 30 30 3b 69 66 63 6f 6e 66 0 200;if conf
PC with rt_8139too - RTcfg Stage 1 Config packet (captured with Wireshark):
0000 ff ff ff ff ff ff 00 30 ab 02 87 df 90 22 00 01 .......0 ....."..
0010 0a 65 01 7e 0a 65 01 7f 04 00 42 24 54 44 4d 41 .e.~.e.. ..B$TDMA
0020 43 46 47 20 72 74 65 74 68 30 20 73 6c 6f 74 20 CFG rtet h0 slot
0030 30 20 32 30 30 3b 69 66 63 6f 6e 66 69 67 20 76 0 200;if config v
0040 6e 69 63 30 20 75 70 20 24 49 50 41 44 44 52 20 nic0 up $IPADDR
0050 24 4e 45 54 4d 41 53 4b 5f 4f 50 54 0a $NETMASK _OPT.
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
RTnet-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rtnet-developers
