Adam Mallory wrote:
Per Akesson <> Per.Akesson@carmenta.se> > wrote in message
news:> 3F8E9B47.3077F461@carmenta.se> …
Adam Mallory wrote:
Have you had a chance to look into it yet ?
BTW, I did a fresh install on a new harddisk from
the QNX Upgrade, July 2003 CD, but the problem
persists.
I still cannot seem to reproduce this over an NFS mount (I’ve even tried
larger number of concurrent sessions). Seeing that you can see the issue
but only via NFS - have you tried eliminating/replacing your network card -
seems to me the only thing left.
-Adam
Yes, I thought of that too and
switched to a NE2000 card, but still, Proc32
crashes.
I did some further investigations and tried:
35894 Jul 27 1998 Net/Net.patchA*
32456 Sep 27 1999 Net/Net.patchC*
32456 Sep 27 1999 Net/Net.patchD*
32456 Sep 27 1999 Net/Net.patchE*
133827 Oct 15 1998 Proc32/Proc32.patchA?*
134772 Nov 25 1998 Proc32/Proc32.patchB*
130615 Sep 09 1999 Proc32/Proc32.patchC*
130615 Sep 09 1999 Proc32/Proc32.patchD*
281318 Feb 15 2001 Proc32/Proc32.patchE*
230337 Aug 12 1997 Socket/Socket.424*
228688 Aug 19 1998 Socket/Socket.nopatch*
361420 Dec 08 1998 Socket/Socket.patchB*
228455 Jul 30 1999 Socket/Socket.patchC*
Not all combinations, but going from newer to older of
each process. No change.
I even experience the crash only with one wd and
then a ps listing could trigger the crash.
thanks anyway looking into it.
PS
I don’t recall that I had this problem with
QNX 4.25 when released (i.e. unpatched).
I’ll try to find the disks and do a fresh install
and see if the crash disappear, (when I have the time).
\
Per Åkesson
Carmenta AB
SWEDEN
Adam Mallory wrote:
Per Akesson <> Per.Akesson@carmenta.se> > wrote in message
news:> 3F8E9B47.3077F461@carmenta.se> …
Adam Mallory wrote:
Have you had a chance to look into it yet ?
BTW, I did a fresh install on a new harddisk from
the QNX Upgrade, July 2003 CD, but the problem
persists.
I still cannot seem to reproduce this over an NFS mount (I’ve even tried
larger number of concurrent sessions). Seeing that you can see the issue
but only via NFS - have you tried eliminating/replacing your network card -
seems to me the only thing left.
-Adam
I just thought of something, could it have anything
to do with the NFS server ?
FYI, our NFS server is:
uname -a
SunOS sunny 5.7 Generic_106541-04 sun4u sparc SUNW,Ultra-1
regards
–
Per Åkesson
Carmenta AB
SWEDEN
Per Akesson <Per.Akesson@carmenta.se> wrote:
PA > Even further investigation shows that it is not NFS-related.
PA > I unmounted all NFS-partitions and mounted them as
PA > Samba-share, still Proc32 crashes.
PA > OK I have to develop on local hard disk, I thought, but …
PA > Proc32 crashes, so my previous observation was wrong.
PA > OK new fresh install from QNX 4.23 … no crash.
PA > Upgraded patch for patch and it seems (no crash so far)
PA > that the latest Proc32 I can use is 4.24G.
PA > So thats my current situation.
PA > Any comments ?
Hi Per
So it sounds like your saying that 4.24G works and whatever you try
after that doesn’t work. There are many versions after 4.24G. There
is the whole 4.25. You might consider skipping the whole 4.24 and go
to the latest 4.25.
Per Akesson wrote:
Adam Mallory wrote:
Per Akesson <> Per.Akesson@carmenta.se> > wrote in message
news:> 3F8E9B47.3077F461@carmenta.se> …
Adam Mallory wrote:
Have you had a chance to look into it yet ?
BTW, I did a fresh install on a new harddisk from
the QNX Upgrade, July 2003 CD, but the problem
persists.
I still cannot seem to reproduce this over an NFS mount (I’ve even tried
larger number of concurrent sessions). Seeing that you can see the issue
but only via NFS - have you tried eliminating/replacing your network card -
seems to me the only thing left.
-Adam
Even further investigation shows that it is not NFS-related.
I unmounted all NFS-partitions and mounted them as
Samba-share, still Proc32 crashes.
OK I have to develop on local hard disk, I thought, but …
Proc32 crashes, so my previous observation was wrong.
OK new fresh install from QNX 4.23 … no crash.
Upgraded patch for patch and it seems (no crash so far)
that the latest Proc32 I can use is 4.24G.
So thats my current situation.
Any comments ?
\
Per Åkesson
Carmenta AB
SWEDEN
Bill Caroselli wrote:
Hi Per
So it sounds like your saying that 4.24G works and whatever you try
after that doesn’t work. There are many versions after 4.24G. There
is the whole 4.25. You might consider skipping the whole 4.24 and go
to the latest 4.25.
Thanks for your suggestion Bill, but
this all started when Proc32 4.25J started to crash.
I tried Proc32 4.25O (latest) but it also crashes.
So I have worked my way back and the last one that
works is Proc32 4.24G.
thanks anyway
–
Per Åkesson
Carmenta AB
SWEDEN
Per Akesson <Per.Akesson@carmenta.se> wrote:
PA > Thanks for your suggestion Bill, but
PA > this all started when Proc32 4.25J started to crash.
PA > I tried Proc32 4.25O (latest) but it also crashes.
PA > So I have worked my way back and the last one that
PA > works is Proc32 4.24G.
PA > thanks anyway
PA > –
PA > Per ?kesson
PA > Carmenta AB
PA > SWEDEN
I’m sorry. I missed that part.
If there is a demonstratable bug in the current(latest) version of
the OS then QSSL should fix it.
Bill Caroselli <qtps@earthlink.net> wrote in message
news:bnj5l8$cbp$1@inn.qnx.com…
I’m sorry. I missed that part.
If there is a demonstratable bug in the current(latest) version of
the OS then QSSL should fix it.
Except for the fact it isn’t reproducable on my end at all (and the shutdown
info doesn’t make sense,
which leads me to believe something else is rotten in Denmark).
Thanks for the input.
-Adam