Ah!
I didn’t get that you were running a Phindows screen. I thought from
your original post that you had an IP application running under windows
that was connecting to a QNX server with all of these sockets.
The first question is to determine which computer is hanging, QNX or
Windows. Is anything running on the Windows system besides the
Phindows session?
Johannes <Jsukamtoh@infolink.co.id> wrote:
J > It’s Phindows mouse, running on XP. I haven’t tried to move the mouse on the
J > Neutrino machine yet, but one thing I am sure of is the system stops
J > running.
J > I am not sure about the interrupt. When I install the O/S, it doesn’t ask
J > for which interrupt to use for the mouse and network, and I used all the
J > default setting. BTW, how can I check which interrupt used by the mouse and
J > network card? Any tools?
J > However, I don’t think it is the interrupt that causes the problem because I
J > notice the problem appears only when the number of opened files (shown by
J > spin) is approaching 4096. I have tried to create a small program which
J > keeps on spawning new processes and it worked just fine (over 5000 opened
J > FDs). So my assumption is that the problem is not due to spawning child
J > process itself, but it is due to the combination of opening file, sockets,
J > spawning child process, and timer, that my application uses quite a lot
J > here.
J > I am still not getting the answer from QNX regarding the limitation of
J > Neutrino in term of number of processes, file opened, sockets, timers, etc.
J > etc. which is not documented anywhere. Why is it so hard to get their answer
J > on this matter?
J > “Bill Caroselli” <qtps@earthlink.net> wrote in message
J > news:bj7dg6$n8e$2@inn.qnx.com…
Johannes <> Jsukamtoh@infolink.co.id> > wrote:
J > I have a device simulator running on Windows which connect via socket
J > to my
J > application running on Neutrino 6.2.1B. The simulator has successfully
J > connected up to 81 socket connection (same address but different port
J > on
J > each connection). Everything works fine until it connects the 82nd
J > connection where the whole system in Neutrino got lock up. And
J > strangely it
J > continues working when I move the mouse and lock up again if I stop
J > the
J > moving the mouse. I have run spin that shows the following
J > information:
J > Mem free: 61%
J > Net en0: < 1 %
J > Threads = 529
J > Total processes = 473
J > Memory = 132m
J > Total FDs = 4296
J > CPU% procnto > 90, spin 4
J > I have to move the mouse cotinuously to get the spin running, and when
J > I
J > stop the mouse, spin also stops.
J > Looks like we have some interrupt problem here. My processes open a
J > lot of
J > sockets, and I have timer running in almost all processes.
J > Can anyone help me with this problem? Have I reached some system
J > limitation?
J > I have set -F10000 to my procnto.
Sounds like you need one of those wheels to let your mouse keep running
without stopping. ;~}
Just to confirm, you are taking about moving the QNX mouse, right?
Is your mouse sharing an interrupt with something else? Like your
network card?
If so, try putting it or the network on a different interrupt.