Another system crash

QNX Newsgroups (Archives) qdn.public.qnx4
1

Here is a (hand) copy of the screen (should be taken with a little salt)
after a system crash:

Version 425.J Sep 09, 1999
Proc Fault 1, ldt 100 sys/Proc32; fault e+0
cs:eip 5:892e ss:esp d:f7c0f54 efl:12297 ds=d es=d
fs=0 gs=0
eax/0 ebx/3c1e7a8b ecx/c4e8fcf edx/100 esi/44aa edi/1
ebp/f7c0f5c

Stack (d:f7c0f54)
00000000 00000001 0f7c0fa0 000037f8 0000e3b6 000089b1
000037f8 0000e3b6
00008000 0c4e8fcf 00008b5f 0002e360 3655b9d0 3c1e7a8a
00000000 3c1e7a8b
00000001 00000001 00000001 0f7c0fb8 00000000 0000597d
0002e360 00008f1a
00000015 0f7c0fe8 0000597d 0000000b 000037f8 0f7c0fd0
00005724 000037f8

Process Entry (addr 5aa4)
00000000 00000001 00000000 00000001 00000000 00000000
30020207 00001a1a
00005858 0100000d 00005b5c ffffffff 00000000 00000000
00000000 00000000
00000000 00000000 00000000 00006401 000d0005 00008218
00000000 00000001
00000022 00000000 00000156 000102c0 00000000 00000000
00031e80 00000000
00000000 00000000 00000000 ffff0001 00000000 00000000 00000000

We can reproduce this crash reliably. It seems to be related to Network
activity. We run multiple simulators in the same scenario and they
exchange data via UDP multicast. One, two or three simulators run with
no problem. When we add a fourth, this crash occurs. Any idea what’s
happening? What other information do you need?

2

Can you post a sin ver and a cat /etc/version/qnx

-Adam


“Dean Douthat” <ddouthat@faac.com> wrote in message
news:3C1F789B.A7292546@faac.com…

Here is a (hand) copy of the screen (should be taken with a little salt)
after a system crash:

Version 425.J Sep 09, 1999
Proc Fault 1, ldt 100 sys/Proc32; fault e+0
cs:eip 5:892e ss:esp d:f7c0f54 efl:12297 ds=d es=d
fs=0 gs=0
eax/0 ebx/3c1e7a8b ecx/c4e8fcf edx/100 esi/44aa edi/1
ebp/f7c0f5c

Stack (d:f7c0f54)
00000000 00000001 0f7c0fa0 000037f8 0000e3b6 000089b1
000037f8 0000e3b6
00008000 0c4e8fcf 00008b5f 0002e360 3655b9d0 3c1e7a8a
00000000 3c1e7a8b
00000001 00000001 00000001 0f7c0fb8 00000000 0000597d
0002e360 00008f1a
00000015 0f7c0fe8 0000597d 0000000b 000037f8 0f7c0fd0
00005724 000037f8

Process Entry (addr 5aa4)
00000000 00000001 00000000 00000001 00000000 00000000
30020207 00001a1a
00005858 0100000d 00005b5c ffffffff 00000000 00000000
00000000 00000000
00000000 00000000 00000000 00006401 000d0005 00008218
00000000 00000001
00000022 00000000 00000156 000102c0 00000000 00000000
00031e80 00000000
00000000 00000000 00000000 ffff0001 00000000 00000000 00000000

We can reproduce this crash reliably. It seems to be related to Network
activity. We run multiple simulators in the same scenario and they
exchange data via UDP multicast. One, two or three simulators run with
no problem. When we add a fourth, this crash occurs. Any idea what’s
happening? What other information do you need?

3

Attached.

Operating Systems Group wrote:

Can you post a sin ver and a cat /etc/version/qnx

-Adam

“Dean Douthat” <> ddouthat@faac.com> > wrote in message
news:> 3C1F789B.A7292546@faac.com> …
Here is a (hand) copy of the screen (should be taken with a little salt)
after a system crash:

Version 425.J Sep 09, 1999
Proc Fault 1, ldt 100 sys/Proc32; fault e+0
cs:eip 5:892e ss:esp d:f7c0f54 efl:12297 ds=d es=d
fs=0 gs=0
eax/0 ebx/3c1e7a8b ecx/c4e8fcf edx/100 esi/44aa edi/1
ebp/f7c0f5c

Stack (d:f7c0f54)
00000000 00000001 0f7c0fa0 000037f8 0000e3b6 000089b1
000037f8 0000e3b6
00008000 0c4e8fcf 00008b5f 0002e360 3655b9d0 3c1e7a8a
00000000 3c1e7a8b
00000001 00000001 00000001 0f7c0fb8 00000000 0000597d
0002e360 00008f1a
00000015 0f7c0fe8 0000597d 0000000b 000037f8 0f7c0fd0
00005724 000037f8

Process Entry (addr 5aa4)
00000000 00000001 00000000 00000001 00000000 00000000
30020207 00001a1a
00005858 0100000d 00005b5c ffffffff 00000000 00000000
00000000 00000000
00000000 00000000 00000000 00006401 000d0005 00008218
00000000 00000001
00000022 00000000 00000156 000102c0 00000000 00000000
00031e80 00000000
00000000 00000000 00000000 ffff0001 00000000 00000000 00000000

We can reproduce this crash reliably. It seems to be related to Network
activity. We run multiple simulators in the same scenario and they
exchange data via UDP multicast. One, two or three simulators run with
no problem. When we add a fourth, this crash occurs. Any idea what’s
happening? What other information do you need?

4

“Dean Douthat” <ddouthat@faac.com> wrote in message
news:3C1FA289.DEF93913@faac.com…

Attached.

If you could, can you inline the information as many of us do not use
newsreaders which support attachments. Thanks.

-Adam

5

QNX Software Systems Ltd. QNX 4.24, release date 05-Sept-97
QNX Software Systems Ltd. QNX 4.25, release date 13-Nov-98
QNX Software Systems Ltd. QNX 4.25 Patch D, date 25-Apr-2000
QNX Software Systems Ltd. QNX 4.25 Patch D, date 25-Apr-2000
QNX Software Systems Ltd. QNX 4.25 Patch D, date 25-Apr-2000

PROGRAM NAME VERSION DATE
sys/Proc32 Proc 4.25J Sep 09 1999
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24V Feb 18 2000
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.eide eide 4.25A Feb 09 2000
//1/bin/Dev32 Dev32 4.23G Oct 04 1996
//1/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//1/bin/Dev32.ser Dev32.ser 4.23I Jun 27 1997
//1/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//1/bin/Mouse Mouse 4.24A Aug 22 1997
//1/bin/Pipe Pipe 4.23A Feb 26 1996
//1/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000
//1/bin/Net Net 4.25C Aug 30 1999
//1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000
//1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000
//1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000
//1//usr/ucb/Tcpip Tcpip 5.00X Jul 30 1999
//1/bin/cron cron 4.23B Oct 30 1997
//1/bin/Audio.423 Audio.423 4.23A Apr 17 1997
//1/bin/Audio.423 Audio.423 4.23A Apr 17 1997
//1/project/bin/exec Exec 1.00A Dec 12 2001
//1/bin/SMBfsys SMBfsys 1.30I Dec 07 1999
//1//bin/replay-server Replay 1.00A Dec 12 2001
//1/bin/Dosfsys Dosfsys 4.23E Jan 21 1997

6

file://1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000
file://1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000
file://1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000

I’ve noticed you’re running the CormanTech driver - perhaps it has an issue
with multicast. In QNX4, Net/Net drivers have a very close connection to
the kernel so a bug in the driver could be your issue.

AFAIK, you can use the ne2000 driver and it should work (according to
CormanTech) and see if you have the same problem. I went to their website
to see if there was an update for the driver, but alas, it was down (or I
can’t get to it) www.cormantech.com

-Adam

7

“Operating Systems Group” <os@qnx.com> wrote in message
news:9vvj6u$dfu$1@nntp.qnx.com…

file://1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000
file://1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000
file://1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000


I’ve noticed you’re running the CormanTech driver - perhaps it has an
issue
with multicast. In QNX4, Net/Net drivers have a very close connection to
the kernel so a bug in the driver could be your issue.

The page seems to be up now, and a looking at the driver download page it
seems to indicate the driver is for QNX 4.23/4.24. Did you notice if it was
working without a problem when you where using 4.24?

-Adam

8

We haven’t run 4.24 for a long time and wouldn’t have had multiple systems at
that time to duplucate the conditions under which we now see the crash.

We’ll check with Corman about this possibility.

Operating Systems Group wrote:

“Operating Systems Group” <> os@qnx.com> > wrote in message
news:9vvj6u$dfu$> 1@nntp.qnx.com> …

file://1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000
file://1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000
file://1/bin/Net.ct100tx Net.ct100tx 4.25C Oct 17 2000


I’ve noticed you’re running the CormanTech driver - perhaps it has an
issue
with multicast. In QNX4, Net/Net drivers have a very close connection to
the kernel so a bug in the driver could be your issue.

The page seems to be up now, and a looking at the driver download page it
seems to indicate the driver is for QNX 4.23/4.24. Did you notice if it was
working without a problem when you where using 4.24?

-Adam