Hi Norbert:
	While pidin is the preferred mechanism for getting system
information, sin certainly shouldn't cause a crash.  It's possible that your
program isn't correctly handling one of the messages that sin sends out and
that's what's causing the crash.  That should be pretty easy to debug.

There certainly appears to be some sort of driver problem on nto2.  I can
see one nicinfo output (which I'm assuming is from nto1?) but not the other.
Have you started up io-net manually or is this through the enumeration
process done at start up?

The nto2 logs show that packets have been sent to the driver to be
transmitted but are not being transmitted and the packet that was requested
to be sent is still "owned" by the driver (hence the "in progress" log...
This typically means that the packet has been placed in the transmit
descriptor ring but hasn't been transmitted).  At this point, qnet sends a
flush request to the driver in order to free up the packet but that doesn't
appear to be having any effect.

If we can have the nicinfo information from nto2 and (if you have them) the
command lines used to start io-net that would help us see if there's a
driver problem.


If you're sending a 1000 requests in short order, another possibility is
that you are running out of buffers. 

You can slay io-net and re-start it as follows to provide more buffers to
the driver

sloginfo -c 
io-net -di82544 receive=2048,transmit=2048,verbose -pqnet

(you may also have to add the -ptcpip option if you need IP connectivity as
well)

Run through your tests and then do another "sloginfo" on both nodes and see
if there are any driver error messages printed out.


	Robert.


-----Original Message-----
From: Norbert Wassmer [mailto:norbert.wassmer@de.bosch.com] 
Sent: Monday, December 17, 2007 6:19 AM
To: technology-networking
Subject: qnet delays

Hi,

I hope this is the right forum for my question.....

I'm using QNX4 to control many of our testbenches on 25 Node network.
Now I plan to switch over to Neutrino.
To test some things (especially qnet), I have connected 2 Neutrino computers
called nto1 and nto2 (using a crossover connection)

I started qnet (with no options) and I can access nto2  from  nto1.

So far everything is ok, but

- when I call  sin -n nto2 from nto1 the program crashes with a core dump

- when I call  pidin -n nto2   I get the list but sometimes (often) the
output stops for about 10 seconds and continues 
after that delay. 

- I have started a small server prog on nto2. Then I connect a client, which
runs on nto1, to the server. The client 
sends 1000 requests to the server (message length 4 byte). To see what
happens the server prints out the number of the 
current request.  The output stops after a certain number of request  (again
for about 10 secs) continues, stops again, 
continues....

What is the reason for that delays?

In the attachment you find some info about my configuration.

Thanks 

Norbert

_______________________________________________
Technology
http://community.qnx.com/sf/go/post3815

I would suggest use a hub/switch instead of cross-cable first, see if that helps.