Hi
I have QNX 6.2.0 running on a fast x86 platform. I have an application that
uses TCP/IP that runs on it and communicates with a server. After starting
the run at night, the system crashes after approximately 12 hours.
This is what happens:
After about 12 hours of normal run, the application log (my program’s log)
says that it timed out on the communication and so shuts down normally. No
problem there. But then the machine goes into a crashed state. Trying to
connect to it (like ftp or telnet) remotely fails. But pinging it works.
Also the machine stops responding locally too…
I tried the run with and without photon (my app doesn’t need photon). It
crashes both times. So I guess photon is ruled out.
Also since my app shuts down normally, I guess the app isn’t to blame either
Without photon running, typing anything at the shell prompt after the crash
shows a simple “Memory Fault” error.
Then on only way to recover is to cycle power.
Any help would be appreciated…
Thanks,
Santosh
Answered in qdn.public.qnxrtp.os
Kris
“Santosh Patil” <Santosh.Patil@gehh.ge.com> wrote in message
news:alndcg$73u$1@inn.qnx.com…
Hi
I have QNX 6.2.0 running on a fast x86 platform. I have an application
that
uses TCP/IP that runs on it and communicates with a server. After starting
the run at night, the system crashes after approximately 12 hours.
This is what happens:
After about 12 hours of normal run, the application log (my program’s log)
says that it timed out on the communication and so shuts down normally. No
problem there. But then the machine goes into a crashed state. Trying to
connect to it (like ftp or telnet) remotely fails. But pinging it works.
Also the machine stops responding locally too…
I tried the run with and without photon (my app doesn’t need photon). It
crashes both times. So I guess photon is ruled out.
Also since my app shuts down normally, I guess the app isn’t to blame
either
Without photon running, typing anything at the shell prompt after the
crash
shows a simple “Memory Fault” error.
Then on only way to recover is to cycle power.
Any help would be appreciated…
Thanks,
Santosh
I have similar problem with QNX 6.1.0 on one computer (PentiumII 200Mhz).
After all night of running it crashes without any reason. I tried it
several times and it was always the same. On other comps I don’t have such
a problem.
On Wed, 11 Sep 2002, Santosh Patil wrote:
Hi
I have QNX 6.2.0 running on a fast x86 platform. I have an application that
uses TCP/IP that runs on it and communicates with a server. After starting
the run at night, the system crashes after approximately 12 hours.
This is what happens:
After about 12 hours of normal run, the application log (my program’s log)
says that it timed out on the communication and so shuts down normally. No
problem there. But then the machine goes into a crashed state. Trying to
connect to it (like ftp or telnet) remotely fails. But pinging it works.
Also the machine stops responding locally too…
I tried the run with and without photon (my app doesn’t need photon). It
crashes both times. So I guess photon is ruled out.
Also since my app shuts down normally, I guess the app isn’t to blame either
Without photon running, typing anything at the shell prompt after the crash
shows a simple “Memory Fault” error.
Then on only way to recover is to cycle power.
Any help would be appreciated…
Thanks,
Santosh
\
“Paul Osmialowski” <newchief@b0leknet.ath.cx> wrote in message
news:Pine.LNX.4.44.0209130941140.20921-100000@pc65.bydgoszcz.sdi.tpnet.pl…
I have similar problem with QNX 6.1.0 on one computer (PentiumII 200Mhz).
After all night of running it crashes without any reason. I tried it
several times and it was always the same. On other comps I don’t have such
a problem.
You say that if you repeat the same test on a different computer, it doesn’t
crash? That is, the problem is unique to that particular piece of hardware?
If that’s the case then there is most likely either a) a hardware problem on
that computer or b) an issue with your software and some driver on that
computer that doesn’t exist on the other computers. That could take a while
to narrow down. 
Kris