James Kilts wrote:
> 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.
I suspect the driver has some bug in its RX path, and the RTmac layer is
the first consumer suffering from it, generating an exception.
>
> 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.
Resolve the address given along with the suspension error, check the
disassembly or instrument the RTmac code to find out what it tries to
access (I bet some rtskb field that is corrupted).
Jan
|