SMC 9432 ethernet issues

Hi everyone,

I just discovered that the newer rev of the SMC 9432 board is not reliable with QNX drivers. The chip part number on the newest boards starts with a 83C172. At 100 Mbits, these boards occassionally lose connection and sometimes corrupt all network communication until a reboot. Boards with parts 83C171 work at 100 Mbits forever ( or at least the few days I tested). SMC told me there have beem complains from other UNIX users, but none from windows users who are using SMC written drivers.

IF ANYONE FROM QNX IS READING, SMC IS WILLING TO WORK WITH YOU ON THIS but have not been successful (and really don’t know how to) contacting you. I’d hate to have to change network boards mid-stream in a product, so hopefully, QNX & SMC can resolve this. Could it be I have an out of date QNX driver???

Thanks in advance


=====>from sin ver<=======
PROGRAM NAME VERSION DATE
/boot/sys/Proc32 Proc 4.25I Nov 25 1998
/boot/sys/Proc32 Slib16 4.23G Oct 04 1996
/boot/sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24S Jul 16 1998
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.aha7scsi scsi 4.24M Mar 23 1998
//1/bin/Dev Dev32 4.23G Oct 04 1996
//1/bin/Pipe Pipe 4.23A Feb 26 1996
//1/bin/Dev.ser Dev32.ser 4.23I Jun 27 1997
//1/bin/Dev.ser Dev32.ser 4.23I Jun 27 1997
//1/bin/Dev.ansi Dev32.ansi 4.23H Nov 21 1996
//1/bin/Dev.par Dev32.par 4.23G Oct 04 1996
//1/bin/Dev.pty Dev32.pty 4.23G Oct 04 1996
//1/bin/Fsys.eide eide 4.24N Nov 18 1998
//1/bin/Iso9660fsys Iso9660fsys 4.23B Jun 10 1998
//1/bin/Net Net 4.25B Jul 27 1998
//1/bin/Net.ether1000 Net.ether100 4.24B Jul 24 1998
//1/bin/Net.epic Net.epic 4.24C Dec 04 1998
//1/bin/Net.epic Net.epic 4.24C Dec 04 1998
//1/bin/Net.epic Net.epic 4.24C Dec 04 1998
//1/usr/ucb/Socket Socket 4.25G Mar 29 1999
//1/bin/Mqueue mqueue 4.24B Jan 12 1999
//1//photon/bin/Photon Photon 1.13D Sep 03 1998
//1/
/bin/phfontpfr Photon Font 1.13A Jul 07 1998


======> from sysinit <===========
/bin/Net -d 4 &
/bin/Net.ether1000 -l1 -p320 -i15 &
/bin/Net.epic -I1 -l2 -s 100 -r 100000000 &
/bin/Net.epic -I2 -l3 -s 100 -r 100000000 &
/bin/Net.epic -I0 -l4 -s 100 -r 100000000 &

\


Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: jrosenbloom@vertisinc.com

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:

Hi everyone,

I just discovered that the newer rev of the SMC 9432 board is not reliable with QNX drivers. The chip part number on the newest boards starts with a 83C172. At 100 Mbits, these boards occassionally lose connection and sometimes corrupt all network communication until a reboot. Boards with parts 83C171 work at 100 Mbits forever ( or at least the few days I tested). SMC told me there have beem complains from other UNIX users, but none from windows users who are using SMC written drivers.

IF ANYONE FROM QNX IS READING, SMC IS WILLING TO WORK WITH YOU ON THIS but have not been successful (and really don’t know how to) contacting you. I’d hate to have to change network boards mid-stream in a product, so hopefully, QNX & SMC can resolve this. Could it be I have an out of date QNX driver???

Who did you contact at SMC? If you could let me know, I will get in touch with
them.

Hugh.

Thanks in advance


=====>from sin ver<=======
PROGRAM NAME VERSION DATE
/boot/sys/Proc32 Proc 4.25I Nov 25 1998
/boot/sys/Proc32 Slib16 4.23G Oct 04 1996
/boot/sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24S Jul 16 1998
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.aha7scsi scsi 4.24M Mar 23 1998
//1/bin/Dev Dev32 4.23G Oct 04 1996
//1/bin/Pipe Pipe 4.23A Feb 26 1996
//1/bin/Dev.ser Dev32.ser 4.23I Jun 27 1997
//1/bin/Dev.ser Dev32.ser 4.23I Jun 27 1997
//1/bin/Dev.ansi Dev32.ansi 4.23H Nov 21 1996
//1/bin/Dev.par Dev32.par 4.23G Oct 04 1996
//1/bin/Dev.pty Dev32.pty 4.23G Oct 04 1996
//1/bin/Fsys.eide eide 4.24N Nov 18 1998
//1/bin/Iso9660fsys Iso9660fsys 4.23B Jun 10 1998
//1/bin/Net Net 4.25B Jul 27 1998
//1/bin/Net.ether1000 Net.ether100 4.24B Jul 24 1998
//1/bin/Net.epic Net.epic 4.24C Dec 04 1998
//1/bin/Net.epic Net.epic 4.24C Dec 04 1998
//1/bin/Net.epic Net.epic 4.24C Dec 04 1998
//1/usr/ucb/Socket Socket 4.25G Mar 29 1999
//1/bin/Mqueue mqueue 4.24B Jan 12 1999
//1//photon/bin/Photon Photon 1.13D Sep 03 1998
//1/
/bin/phfontpfr Photon Font 1.13A Jul 07 1998


======> from sysinit <===========
/bin/Net -d 4 &
/bin/Net.ether1000 -l1 -p320 -i15 &
/bin/Net.epic -I1 -l2 -s 100 -r 100000000 &
/bin/Net.epic -I2 -l3 -s 100 -r 100000000 &
/bin/Net.epic -I0 -l4 -s 100 -r 100000000 &

\


Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com

Just to add my 0.02 $ CDN.

We had trouble with 170, replaced them with 171 and still had trouble.
Eventually we selected a hardware manufacturer that supports QNX, that being
Corman Technologies and we have not looked back since.

It would be nice if other hardware manufacturers got on board and started
developing their own drivers for the QNX platforms. I’m sure the development
toolkits of RTP will attract a few.


“Hugh Brown” <hsbrown@qnx.com> wrote in message
news:Voyager.010704084507.12945C@node90.ott.qnx.com

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:
Hi everyone,

I just discovered that the newer rev of the SMC 9432 board is not
reliable with QNX drivers. The chip part number on the newest boards starts

with a 83C172. At 100 Mbits, these boards occassionally lose connection and
sometimes corrupt all network communication until a reboot. Boards with
parts 83C171 work at 100 Mbits forever ( or at least the few days I tested).
SMC told me there have beem complains from other UNIX users, but none from
windows users who are using SMC written drivers.

IF ANYONE FROM QNX IS READING, SMC IS WILLING TO WORK WITH YOU ON THIS
but have not been successful (and really don’t know how to) contacting you.

I’d hate to have to change network boards mid-stream in a product, so
hopefully, QNX & SMC can resolve this. Could it be I have an out of date
QNX driver???

Who did you contact at SMC? If you could let me know, I will get in touch
with
them.

Hugh.

Thanks in advance


=====>from sin ver<=======
PROGRAM NAME VERSION DATE
/boot/sys/Proc32 Proc 4.25I Nov 25 1998
/boot/sys/Proc32 Slib16 4.23G Oct 04 1996
/boot/sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24S Jul 16 1998
/bin/Fsys Floppy 4.24B Aug 19 1997
/bin/Fsys.aha7scsi scsi 4.24M Mar 23 1998
file://1/bin/Dev Dev32 4.23G Oct 04 1996
file://1/bin/Pipe Pipe 4.23A Feb 26 1996
file://1/bin/Dev.ser Dev32.ser 4.23I Jun 27 1997
file://1/bin/Dev.ser Dev32.ser 4.23I Jun 27 1997
file://1/bin/Dev.ansi Dev32.ansi 4.23H Nov 21 1996
file://1/bin/Dev.par Dev32.par 4.23G Oct 04 1996
file://1/bin/Dev.pty Dev32.pty 4.23G Oct 04 1996
file://1/bin/Fsys.eide eide 4.24N Nov 18 1998
file://1/bin/Iso9660fsys Iso9660fsys 4.23B Jun 10 1998
file://1/bin/Net Net 4.25B Jul 27 1998
file://1/bin/Net.ether1000 Net.ether100 4.24B Jul 24 1998
file://1/bin/Net.epic Net.epic 4.24C Dec 04 1998
file://1/bin/Net.epic Net.epic 4.24C Dec 04 1998
file://1/bin/Net.epic Net.epic 4.24C Dec 04 1998
file://1/usr/ucb/Socket Socket 4.25G Mar 29 1999
file://1/bin/Mqueue mqueue 4.24B Jan 12 1999
file://1//photon/bin/Photon Photon 1.13D Sep 03 1998
file://1/
/bin/phfontpfr Photon Font 1.13A Jul 07 1998


======> from sysinit <===========
/bin/Net -d 4 &
/bin/Net.ether1000 -l1 -p320 -i15 &
/bin/Net.epic -I1 -l2 -s 100 -r 100000000 &
/bin/Net.epic -I2 -l3 -s 100 -r 100000000 &
/bin/Net.epic -I0 -l4 -s 100 -r 100000000 &

\


Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com

Thanks for the response Hugh,

SMC said to contact their general tech support (800-762-4968). However, I have been talking to David Cook at the same number, extension 4831. If possible, please keep me in the loop so I know the status of things.

Thanks
Jack

Who did you contact at SMC? If you could let me know, I will get in touch with
them.

Hugh.

Thanks in advance

Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: jrosenbloom@vertisinc.com

Hi Richard,

We also had problems with the 170 chips, but the 171 chips are working great for us. I agree, it would be much better to use boards which the manufacture provides the QNX drivers.

Jack

I have just had a look at your initial posting again and have seen that you
are using a rather old version of the Epic driver. The latest version of the
Epic driver is 4.25H. Is it possible for you to upgrade to the latest release
and see if the problem still exists?

Thanks, Hugh.

Jack Rosenbloom <jrosenbloom@webcraft.com> wrote:

Thanks for the response Hugh,

SMC said to contact their general tech support (800-762-4968). However, I have been talking to David Cook at the same number, extension 4831. If possible, please keep me in the loop so I know the status of things.

Thanks
Jack


Who did you contact at SMC? If you could let me know, I will get in touch with
them.

Hugh.

Thanks in advance

\


Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com

Hi Hugh,

I’d love to try that. The only way I know of updating requires a complete upgrade to 4.25E. I’m concerned about doing that. We operate at the current revision level because of other problems (passwords not working, NFS crashing, licences regularly being lost to name a few) we have seen with all versions since the one we are using. Could you give me instructions to get just the needed network driver.

Thanks,
Jack

Hugh Brown wrote:

I have just had a look at your initial posting again and have seen that you
are using a rather old version of the Epic driver. The latest version of the
Epic driver is 4.25H. Is it possible for you to upgrade to the latest release
and see if the problem still exists?

Thanks, Hugh.

Jack Rosenbloom <> jrosenbloom@webcraft.com> > wrote:
Thanks for the response Hugh,

SMC said to contact their general tech support (800-762-4968). However, I have been talking to David Cook at the same number, extension 4831. If possible, please keep me in the loop so I know the status of things.

Thanks
Jack


Who did you contact at SMC? If you could let me know, I will get in touch with
them.

Hugh.

Thanks in advance

\


Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com

Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: jrosenbloom@vertisinc.com

Hi Hugh,

Thanks for sending the SW update. However, I needed the Net.epic driver, not the Net.ether82557 driver. I tried responding to your email but your server rejected my email as spam.

Thanks,
Jack

Hugh Brown wrote:

I have just had a look at your initial posting again and have seen that you
are using a rather old version of the Epic driver. The latest version of the
Epic driver is 4.25H. Is it possible for you to upgrade to the latest release
and see if the problem still exists?

Thanks, Hugh.

Jack Rosenbloom <> jrosenbloom@webcraft.com> > wrote:
Thanks for the response Hugh,

SMC said to contact their general tech support (800-762-4968). However, I have been talking to David Cook at the same number, extension 4831. If possible, please keep me in the loop so I know the status of things.

Thanks
Jack


Who did you contact at SMC? If you could let me know, I will get in touch with
them.

Hugh.

Thanks in advance

\


Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com

Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: jrosenbloom@vertisinc.com

Replied via e-mail.

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:

Hi Hugh,

Thanks for sending the SW update. However, I needed the Net.epic driver, not the Net.ether82557 driver. I tried responding to your email but your server rejected my email as spam.

Thanks,
Jack

Hugh Brown wrote:

I have just had a look at your initial posting again and have seen that you
are using a rather old version of the Epic driver. The latest version of the
Epic driver is 4.25H. Is it possible for you to upgrade to the latest release
and see if the problem still exists?

Thanks, Hugh.

Jack Rosenbloom <> jrosenbloom@webcraft.com> > wrote:
Thanks for the response Hugh,

SMC said to contact their general tech support (800-762-4968). However, I have been talking to David Cook at the same number, extension 4831. If possible, please keep me in the loop so I know the status of things.

Thanks
Jack


Who did you contact at SMC? If you could let me know, I will get in touch with
them.

Hugh.

Thanks in advance

\


Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com

Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com

Hi Hugh,

Thanks for the new driver. The new driver yields more consisent and somewhat faster through put with the older 171 based boards. Unfortanuately, It still does not work with the newer 172 based boards. Now what?

Jack



Hugh Brown wrote:

Replied via e-mail.

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:
Hi Hugh,

Thanks for sending the SW update. However, I needed the Net.epic driver, not the Net.ether82557 driver. I tried responding to your email but your server rejected my email as spam.

Thanks,
Jack

Hugh Brown wrote:

I have just had a look at your initial posting again and have seen that you
are using a rather old version of the Epic driver. The latest version of the
Epic driver is 4.25H. Is it possible for you to upgrade to the latest release
and see if the problem still exists?

Thanks, Hugh.

Jack Rosenbloom <> jrosenbloom@webcraft.com> > wrote:
Thanks for the response Hugh,

SMC said to contact their general tech support (800-762-4968). However, I have been talking to David Cook at the same number, extension 4831. If possible, please keep me in the loop so I know the status of things.

Thanks
Jack


Who did you contact at SMC? If you could let me know, I will get in touch with
them.

Hugh.

Thanks in advance

\


Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com

Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com

Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: jrosenbloom@vertisinc.com

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:

Hi Hugh,

Thanks for the new driver. The new driver yields more consisent and somewhat faster through put with the older 171 based boards. Unfortanuately, It still does not work with the newer 172 based boards. Now what?

I’ll have to a) get hold of the hardware and b) contact SMC and get the latest
documentation on the chip.

Hugh.

Jack



Hugh Brown wrote:

Replied via e-mail.

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:
Hi Hugh,

Thanks for sending the SW update. However, I needed the Net.epic driver, not the Net.ether82557 driver. I tried responding to your email but your server rejected my email as spam.

Thanks,
Jack

Hugh Brown wrote:

I have just had a look at your initial posting again and have seen that you
are using a rather old version of the Epic driver. The latest version of the
Epic driver is 4.25H. Is it possible for you to upgrade to the latest release
and see if the problem still exists?

Thanks, Hugh.

Jack Rosenbloom <> jrosenbloom@webcraft.com> > wrote:
Thanks for the response Hugh,

SMC said to contact their general tech support (800-762-4968). However, I have been talking to David Cook at the same number, extension 4831. If possible, please keep me in the loop so I know the status of things.

Thanks
Jack


Who did you contact at SMC? If you could let me know, I will get in touch with
them.

Hugh.

Thanks in advance

\


Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com

Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com


\


Jack Rosenbloom
Vertis, Inc - DMS
Manager, Advanced Process Control Engineering
4371 County Line Road
Chalfont PA. 18914
Phone: (215) 997-5269
FAX: (215) 997-5455
E-Mail: > jrosenbloom@vertisinc.com

Thanks again Hugh,

Let me know if I can help in any way, testing, etc.

Jack


Hugh Brown wrote:

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:
Hi Hugh,

Thanks for the new driver. The new driver yields more consisent and somewhat faster through put with the older 171 based boards. Unfortanuately, It still does not work with the newer 172 based boards. Now what?


I’ll have to a) get hold of the hardware and b) contact SMC and get the latest
documentation on the chip.

Hugh.

I have tested Net.epic with the new 172 chip and I don’t see any problems.
How are you testing this? Also the output from netinfo would be helpful.
When you say that it doesn’t work, do you mean “at all” or “intermittently”
or “after a while”? I have been copying large files using both QNX networking
and ftp, with no problems.

Hugh.

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:

Thanks again Hugh,

Let me know if I can help in any way, testing, etc.

Jack


Hugh Brown wrote:

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:
Hi Hugh,

Thanks for the new driver. The new driver yields more consisent and somewhat faster through put with the older 171 based boards. Unfortanuately, It still does not work with the newer 172 based boards. Now what?


I’ll have to a) get hold of the hardware and b) contact SMC and get the latest
documentation on the chip.

Hugh.

My application has two uses for the network boards. In both cases, I run at 100MBits/sec (no issues at 10Mbits).

test #1
My application opens a TCP socket and moves about 100MB of data from a SCSI disk to a printer made by Scitex. This is a private network with just QNX and the printer. There is a second socket connection for control to this printer with very minor polling travel once a second. Data transfers average about 1.7Mbytes/sec. This test fails 75% of the time on all 172 boards. 171 boards have been consistently running this application on multiple systems for over a year. Much of the 233Mhz Pentium CPU is consumed.

test #2
FTP’ing 50 MB files from an IBM390 to QNX. With a T1 line in the middle, transfers average 150 - 180 Kbytes/sec. This tests fails about 25% of the time with certain 172 boards, but not all boards.

171 boards always work consisently and reliably.


FAILURE MODES
==> intermitten poor performance

Virtually all transfers stop for a while and then continue (my appl under test #1 times out after 5 seconds, test #2 after 15 seconds. These application time outs are sometimes occurring). In both test cases, you see a large variability in performance. It doesn’t take long for this to occur in test #1. netstat -Ien4 -w1 shows no activity during these periods.

==> Lost of connectivity

After the system is in a “poor performance” mode for a while (5 or 10 minutes), all network boards stop working (I have 3 9432 boards and 1 ISA board running Net.ether1000). Reboot is the only option.

Hope this helps
Jack

Please can you provide me with the following information:

Output from ‘show_pci -v’
output from netinfo when the problem occurs.
output from sin

Thanks, Hugh.

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:

My application has two uses for the network boards. In both cases, I run at 100MBits/sec (no issues at 10Mbits).

test #1
My application opens a TCP socket and moves about 100MB of data from a SCSI disk to a printer made by Scitex. This is a private network with just QNX and the printer. There is a second socket connection for control to this printer with very minor polling travel once a second. Data transfers average about 1.7Mbytes/sec. This test fails 75% of the time on all 172 boards. 171 boards have been consistently running this application on multiple systems for over a year. Much of the 233Mhz Pentium CPU is consumed.

test #2
FTP’ing 50 MB files from an IBM390 to QNX. With a T1 line in the middle, transfers average 150 - 180 Kbytes/sec. This tests fails about 25% of the time with certain 172 boards, but not all boards.

171 boards always work consisently and reliably.


FAILURE MODES
==> intermitten poor performance

Virtually all transfers stop for a while and then continue (my appl under test #1 times out after 5 seconds, test #2 after 15 seconds. These application time outs are sometimes occurring). In both test cases, you see a large variability in performance. It doesn’t take long for this to occur in test #1. netstat -Ien4 -w1 shows no activity during these periods.

==> Lost of connectivity

After the system is in a “poor performance” mode for a while (5 or 10 minutes), all network boards stop working (I have 3 9432 boards and 1 ISA board running Net.ether1000). Reboot is the only option.

Hope this helps
Jack

This should be what you as for. Thanks again for the great response. I added comments on which board is which.

Jack

PCI version = 2.10

Vendor ID = 10b9h, Acer Labs
Device ID = 1541h
PCI index = 0h
Class Code = 60000h Bridge (Host/PCI) ProgIF=0
Revision ID = 4h
Bus number = 0
Device number = 0
Function num = 0
Status Reg = 2410h
Command Reg = 6h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Base Address = MEM@e0000000h,32bit length 67108864
Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0
PCI Int Pin = NC
Interrupt line = 0

Vendor ID = 10b9h, Acer Labs
Device ID = 5243h
PCI index = 0h
Class Code = 60400h Bridge (PCI/PCI) ProgIF=0
Revision ID = 4h
Bus number = 0
Device number = 1
Function num = 0
Status Reg = 400h
Command Reg = 107h
Header type = 1h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Unknown header type

Vendor ID = 10b9h, Acer Labs
Device ID = 1533h
PCI index = 0h
Class Code = 60100h Bridge (PCI/ISA) ProgIF=0
Revision ID = c3h
Bus number = 0
Device number = 7
Function num = 0
Status Reg = 3200h
Command Reg = fh
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 0h
Cache Line Size= 0h

Max Lat = 0ns
Min Gnt = 0ns
PCI Int Pin = 0
PCI Int Pin = NC
Interrupt line = 0

Vendor ID = 10b9h, Acer Labs
Device ID = 5229h
PCI index = 0h
Class Code = 101eah Mass Storage (IDE) ProgIF=234
Revision ID = c1h
Bus number = 0
Device number = 15
Function num = 0
Status Reg = 280h
Command Reg = 5h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 20h
Cache Line Size= 0h
IO@ffa0h length 16 bytes
Max Lat = 4ns
Min Gnt = 2ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 0

============== COMMENT ADDED BY JACK =========================
This is the 172 based board
============== END OF ADDED BY JACK =========================

Vendor ID = 10b8h
Device ID = 5h
PCI index = 0h
Class Code = 8020000h Network (Ethernet) ProgIF=0
Revision ID = 9h
Bus number = 0
Device number = 17
Function num = 0
Status Reg = 90h
Command Reg = 117h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
Base Address = IO@dc00h length 256 bytes MEM@dffff000h,32bit length 4096
Expansion ROM = 1bffc0h length 65536 disabled
Max Lat = 28ns
Min Gnt = 8ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 11

============= COMMENT ADDED BY JACK =========================
These next 2 are 171 based boards
============= END OF ADDED BY JACK =========================


Vendor ID = 10b8h
Device ID = 5h
PCI index = 1h
Class Code = 20000h Network (Ethernet) ProgIF=0
Revision ID = 8h
Bus number = 0
Device number = 18
Function num = 0
Status Reg = 90h
Command Reg = 107h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Base Address = IO@d800h length 256 bytes MEM@dfffe000h,32bit length 4096
Expansion ROM = 1bffa0h length 65536 disabled
Max Lat = 28ns
Min Gnt = 8ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 10

Vendor ID = 10b8h
Device ID = 5h
PCI index = 2h
Class Code = 20000h Network (Ethernet) ProgIF=0
Revision ID = 8h
Bus number = 0
Device number = 19
Function num = 0
Status Reg = 90h
Command Reg = 107h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Base Address = IO@d400h length 256 bytes MEM@dfffd000h,32bit length 4096
Expansion ROM = 1bff80h length 65536 disabled
Max Lat = 28ns
Min Gnt = 8ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 9

Vendor ID = 9004h, Adaptec Inc.
Device ID = 8178h, AHA-2940 Ultra SCSI controller
PCI index = 0h
Class Code = 8010000h Mass Storage (SCSI) ProgIF=0
Revision ID = 1h
Bus number = 0
Device number = 20
Function num = 0
Status Reg = 290h
Command Reg = 117h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
Base Address = IO@d000h length 256 bytes MEM@dfffb000h,32bit length 4096
Expansion ROM = 1bff60h length 65536 disabled
Max Lat = 8ns
Min Gnt = 8ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 5

Vendor ID = 1002h, ATI TECHNOLOGIES INC
Device ID = 4742h
PCI index = 0h
Class Code = 8030000h Display (VGA) ProgIF=0
Revision ID = 5ch
Bus number = 1
Device number = 0
Function num = 0
Status Reg = 290h
Command Reg = 83h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
Base Address = MEM@ce000000h,32bit length 16777216 IO@cc00h length 256 bytes MEM@cfeff000h,32bit length 4096
Expansion ROM = 19fd80h length 131072 disabled
Max Lat = 0ns
Min Gnt = 8ns
PCI Int Pin = 0
PCI Int Pin = NC
Interrupt line = no connection

IRQ Routing = bus=0 slot=1 device=20
Vendor ID = 9004h, Adaptec Inc.
Device ID = 8178h, AHA-2940 Ultra SCSI controller
INTA=3,4,5,6,7,9,10,11,12,14,15 Slot2:INTD Slot3:INTC Slot4:INTB Motherboard:INTB
INTB=3,4,5,6,7,9,10,11,12,14,15 Slot2:INTA Slot3:INTD Slot4:INTC
INTC=3,4,5,6,7,9,10,11,12,14,15 Slot2:INTB Slot3:INTA Slot4:INTD
INTD=3,4,5,6,7,9,10,11,12,14,15 Slot2:INTC Slot3:INTB Slot4:INTA Motherboard:INTA

IRQ Routing = bus=0 slot=2 device=19
Vendor ID = 10b8h
Device ID = 5h
INTA=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTB Slot3:INTD Slot4:INTC
INTB=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTC Slot3:INTA Slot4:INTD
INTC=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTD Slot3:INTB Slot4:INTA Motherboard:INTA
INTD=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTA Slot3:INTC Slot4:INTB Motherboard:INTB

IRQ Routing = bus=0 slot=3 device=18
Vendor ID = 10b8h
Device ID = 5h
INTA=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTC Slot2:INTB Slot4:INTD
INTB=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTD Slot2:INTC Slot4:INTA Motherboard:INTA
INTC=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTA Slot2:INTD Slot4:INTB Motherboard:INTB
INTD=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTB Slot2:INTA Slot4:INTC

IRQ Routing = bus=0 slot=4 device=17
Vendor ID = 10b8h
Device ID = 5h
INTA=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTD Slot2:INTC Slot3:INTB Motherboard:INTA
INTB=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTA Slot2:INTD Slot3:INTC Motherboard:INTB
INTC=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTB Slot2:INTA Slot3:INTD
INTD=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTC Slot2:INTB Slot3:INTA

IRQ Routing = bus=1 motherboard device=0
Vendor ID = 1002h, ATI TECHNOLOGIES INC
Device ID = 4742h
INTA=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTD Slot2:INTC Slot3:INTB Slot4:INTA
INTB=3,4,5,6,7,9,10,11,12,14,15 Slot1:INTA Slot2:INTD Slot3:INTC Slot4:INTB

IRQ Routing = bus=0 motherboard device=2
No card configured in slot
INTA=3,4,5,6,7,9,10,11,12,14,15


SID PID PROGRAM PRI STATE BLK CODE DATA
– – Microkernel — ----- — 12976 0
0 1 /boot/sys/Proc32 30f READY — 122k 22122k
0 2 /boot/sys/Slib32 10r RECV 0 53k 4096
0 4 /bin/Fsys 10r RECV 0 77k 10375k
0 5 /bin/Fsys.aha7scsi 22r RECV 0 57k 196k
0 8 idle 0r READY — 0 65k
0 16 //1/bin/Dev 24f RECV 0 32k 225k
0 21 //1/bin/Pipe 10r RECV 0 16k 77k
0 23 //1/bin/Dev.ser 20r RECV 0 16k 24k
0 24 //1/bin/Dev.ser 20r RECV 0 16k 24k
0 25 //1/bin/Dev.ansi 20r RECV 0 40k 122k
0 29 //1/bin/Dev.par 9o RECV 0 8192 12k
0 30 //1/bin/Dev.pty 20r RECV 0 12k 57k
0 34 //1/bin/Fsys.eide 22r RECV 0 61k 114k
0 37 //1/bin/Iso9660fsys 10o RECV 0 28k 61k
0 39 //1/bin/Fsys.floppy 10o RECV 0 20k 40k
0 42 //1/bin/Net 23r RECV 0 32k 126k
0 44 //1/bin/Net.ether1000 20r RECV 0 28k 49k
0 45 //1/bin/Net.epic 20r RECV 0 36k 122k
0 47 //1/bin/Net.epic 20r RECV 0 36k 122k
0 49 //1/bin/Net.epic 20r RECV 0 36k 122k
0 51 //1/bin/nameloc 20o RECV 0 6144 20k
0 52 //1/bin/nameloc 20o REPLY 0 6144 20k
0 149 //1/usr/bin/syslogd 10o RECV 0 36k 32k
0 173 //1/bin/Mqueue 9o RECV 0 20k 4706k
0 174 //1/bin/tinit 10o WAIT -1 8192 28k
0 175 //1/bin/tinit 10o RECV 0 8192 20k
1 180 //1//photon/bin/Photon 12r RECV 0 57k 77k
0 184 //1/
/bin/phfontpfr 12r RECV 0 106k 380k
0 191 //1//ragebios.ms 10o RECV 0 40k 28k
0 193 //1/
/drivers/Pg.rage 12r REPLY 180 122k 159k
2 197 //1/bin/login 10o REPLY 16 24k 20k
0 210 //1/bin/Input 12o RECV 0 30k 28k
0 213 //1/bin/Input 10o RECV 0 30k 4096
3 424 //1//photon/bin/pwm 10o RECV 0 81k 73k
4 700 //1/usr/ucb/Socket 23r RECV 0 225k 344k
4 718 //1/usr/ucb/portmap 10o RECV 723 45k 40k
4 725 //1/usr/ucb/mountd 10o RECV 730 40k 36k
5 727 //1/usr/ucb/pcnfsd 10o RECV 732 61k 45k
4 728 //1/usr/ucb/nfsd 10o REPLY 700 40k 28k
4 731 //1/usr/ucb/inetd 10o RECV 737 36k 32k
3 2194 //1/
/photon/bin/pterm 10o RECV 0 24k 102k
6 2198 //1/bin/sh 10o REPLY 16 31k 45k
6 2516 //1/bin/dumper 29o RECV 0 16k 20k
6 2517 //1//watchdog/watchdog 18o RECV 0 12k 20k
6 2518 //1/
/arcnet/net_ser 17o RECV 0 14k 20k
6 2519 //1//history/history 2o RECV 0 8192 20k
6 2520 //1/
/job_name/job_name 2o RECV 0 16k 20k
6 2521 //1//job_info/job_info 2o RECV 0 24k 28k
6 2522 //1/
/password/password 10o RECV 0 16k 16k
6 2523 //1//jaz/jaz_server 10o RECV 0 8192 12k
6 2524 //1/
/notify/notify 3o REPLY 173 61k 57k
6 2525 //1//casper/log/log 5o REPLY 173 10k 20k
6 2526 //1/
/src/default/spre 10o RECV 0 389k 512k
6 2529 //1//2_rip_dim 13o REPLY 173 47k 106k
6 2530 //1/
/casper/log/log 5o REPLY 173 10k 20k
6 2531 //1//retrievespre 9o REPLY 173 36k 1073k
6 2532 //1/
/imager/imager 9o REPLY 173 13k 122k
6 2533 //1//mach/machspre 14o REPLY 173 15k 45k
6 2534 //1/
/casper/qc/sync 8o REPLY 173 16k 28k
6 2535 //1//sync_bcr/sync_rdr 8o REPLY 173 8192 20k
6 2536 //1/
/super/super 18o REPLY 173 28k 32k
6 2541 //1//sync_bcr/sync_rdr 8o REPLY 16 8192 20k
6 2543 //1/
/arcnet/net_ser 14o RECV 0 14k 20k
6 2546 //1//2_rip_dim 13o REPLY 0 47k 106k
6 2547 //1/
/mach/machspre 5o REPLY 173 15k 45k
6 2548 //1//mach/machspre 6o REPLY 173 15k 45k
6 2549 //1/
/imager/imager 9o REPLY 0 13k 122k
6 2555 //1//casper/qc/sync 8o REPLY 0 16k 28k
6 2817 //1/
/imager/imager 16o REPLY 173 13k 122k
6 2822 //1//imager/imager 16o REPLY 700 13k 122k
6 2823 //1/
/imager/imager 16o REPLY 173 13k 122k
3 3555 //1/*/photon/bin/pterm 10o RECV 0 24k 102k
7 3558 //1/bin/sh 10o WAIT -1 31k 36k
7 3570 //1/bin/sh 10o WAIT -1 31k 36k
7 3907 //1/bin/sin 10o REPLY 1 45k 81k


Date Net (Nid|Status) Code Description
16:03:27 0 Status 9 ( 35) NET logical node not in node map
16:03:27 0 Status 9 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:28 0 Status 10 ( 35) NET logical node not in node map
16:03:28 0 Status 10 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:28 0 Status 11 ( 35) NET logical node not in node map
16:03:28 0 Status 11 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:28 0 Status 12 ( 35) NET logical node not in node map
16:03:28 0 Status 12 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:29 0 Status 2 ( 35) NET logical node not in node map
16:03:29 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:29 0 Status 3 ( 35) NET logical node not in node map
16:03:29 0 Status 3 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:29 0 Status 4 ( 35) NET logical node not in node map
16:03:29 0 Status 4 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:29 0 Status 5 ( 35) NET logical node not in node map
16:03:29 0 Status 5 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:29 0 Status 6 ( 35) NET logical node not in node map
16:03:29 0 Status 6 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:29 0 Status 7 ( 35) NET logical node not in node map
16:03:29 0 Status 7 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:29 0 Status 8 ( 35) NET logical node not in node map
16:03:29 0 Status 8 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:29 0 Status 9 ( 35) NET logical node not in node map
16:03:29 0 Status 9 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:30 0 Status 10 ( 35) NET logical node not in node map
16:03:30 0 Status 10 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:30 0 Status 11 ( 35) NET logical node not in node map
16:03:30 0 Status 11 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:30 0 Status 12 ( 35) NET logical node not in node map
16:03:30 0 Status 12 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:31 0 Status 2 ( 35) NET logical node not in node map
16:03:31 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:31 0 Status 3 ( 35) NET logical node not in node map
16:03:31 0 Status 3 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:31 0 Status 4 ( 35) NET logical node not in node map
16:03:31 0 Status 4 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:31 0 Status 5 ( 35) NET logical node not in node map
16:03:31 0 Status 5 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:31 0 Status 6 ( 35) NET logical node not in node map
16:03:31 0 Status 6 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:31 0 Status 7 ( 35) NET logical node not in node map
16:03:31 0 Status 7 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:31 0 Status 8 ( 35) NET logical node not in node map
16:03:31 0 Status 8 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:31 0 Status 9 ( 35) NET logical node not in node map
16:03:31 0 Status 9 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:32 0 Status 10 ( 35) NET logical node not in node map
16:03:32 0 Status 10 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:32 0 Status 11 ( 35) NET logical node not in node map
16:03:32 0 Status 11 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:32 0 Status 12 ( 35) NET logical node not in node map
16:03:32 0 Status 12 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:33 0 Status 2 ( 35) NET logical node not in node map
16:03:33 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:33 0 Status 3 ( 35) NET logical node not in node map
16:03:33 0 Status 3 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:33 0 Status 4 ( 35) NET logical node not in node map
16:03:33 0 Status 4 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:33 0 Status 5 ( 35) NET logical node not in node map
16:03:33 0 Status 5 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:33 0 Status 6 ( 35) NET logical node not in node map
16:03:33 0 Status 6 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:33 0 Status 7 ( 35) NET logical node not in node map
16:03:33 0 Status 7 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:33 0 Status 8 ( 35) NET logical node not in node map
16:03:33 0 Status 8 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:33 0 Status 9 ( 35) NET logical node not in node map
16:03:33 0 Status 9 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:34 0 Status 10 ( 35) NET logical node not in node map
16:03:34 0 Status 10 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:34 0 Status 11 ( 35) NET logical node not in node map
16:03:34 0 Status 11 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:34 0 Status 12 ( 35) NET logical node not in node map
16:03:34 0 Status 12 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:35 0 Status 2 ( 35) NET logical node not in node map
16:03:35 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:35 0 Status 3 ( 35) NET logical node not in node map
16:03:35 0 Status 3 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:35 0 Status 4 ( 35) NET logical node not in node map
16:03:35 0 Status 4 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:35 0 Status 5 ( 35) NET logical node not in node map
16:03:35 0 Status 5 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:35 0 Status 6 ( 35) NET logical node not in node map
16:03:35 0 Status 6 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:35 0 Status 7 ( 35) NET logical node not in node map
16:03:35 0 Status 7 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:35 0 Status 8 ( 35) NET logical node not in node map
16:03:35 0 Status 8 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:35 0 Status 9 ( 35) NET logical node not in node map
16:03:35 0 Status 9 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:36 0 Status 10 ( 35) NET logical node not in node map
16:03:36 0 Status 10 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:36 0 Status 11 ( 35) NET logical node not in node map
16:03:36 0 Status 11 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:36 0 Status 12 ( 35) NET logical node not in node map
16:03:36 0 Status 12 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:37 0 Status 2 ( 35) NET logical node not in node map
16:03:37 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:37 0 Status 3 ( 35) NET logical node not in node map
16:03:37 0 Status 3 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:37 0 Status 4 ( 35) NET logical node not in node map
16:03:37 0 Status 4 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:37 0 Status 5 ( 35) NET logical node not in node map
16:03:37 0 Status 5 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:37 0 Status 6 ( 35) NET logical node not in node map
16:03:37 0 Status 6 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:37 0 Status 7 ( 35) NET logical node not in node map
16:03:37 0 Status 7 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:37 0 Status 8 ( 35) NET logical node not in node map
16:03:37 0 Status 8 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:37 0 Status 9 ( 35) NET logical node not in node map
16:03:37 0 Status 9 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:38 0 Status 10 ( 35) NET logical node not in node map
16:03:38 0 Status 10 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:38 0 Status 11 ( 35) NET logical node not in node map
16:03:38 0 Status 11 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:38 0 Status 12 ( 35) NET logical node not in node map
16:03:38 0 Status 12 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:39 0 Status 2 ( 35) NET logical node not in node map
16:03:39 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:39 0 Status 3 ( 35) NET logical node not in node map
16:03:39 0 Status 3 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:39 0 Status 4 ( 35) NET logical node not in node map
16:03:39 0 Status 4 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:39 0 Status 5 ( 35) NET logical node not in node map
16:03:39 0 Status 5 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:39 0 Status 6 ( 35) NET logical node not in node map
16:03:39 0 Status 6 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:39 0 Status 7 ( 35) NET logical node not in node map
16:03:39 0 Status 7 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:39 0 Status 8 ( 35) NET logical node not in node map
16:03:39 0 Status 8 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:39 0 Status 9 ( 35) NET logical node not in node map
16:03:39 0 Status 9 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:40 0 Status 10 ( 35) NET logical node not in node map
16:03:40 0 Status 10 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:40 0 Status 11 ( 35) NET logical node not in node map
16:03:40 0 Status 11 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:40 0 Status 12 ( 35) NET logical node not in node map
16:03:40 0 Status 12 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:41 0 Status 2 ( 35) NET logical node not in node map
16:03:41 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:41 0 Status 3 ( 35) NET logical node not in node map
16:03:41 0 Status 3 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:41 0 Status 4 ( 35) NET logical node not in node map
16:03:41 0 Status 4 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:41 0 Status 5 ( 35) NET logical node not in node map
16:03:41 0 Status 5 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:41 0 Status 6 ( 35) NET logical node not in node map
16:03:41 0 Status 6 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:41 0 Status 7 ( 35) NET logical node not in node map
16:03:41 0 Status 7 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:41 0 Status 8 ( 35) NET logical node not in node map
16:03:41 0 Status 8 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:41 0 Status 9 ( 35) NET logical node not in node map
16:03:41 0 Status 9 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:42 0 Status 10 ( 35) NET logical node not in node map
16:03:42 0 Status 10 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:42 0 Status 11 ( 35) NET logical node not in node map
16:03:42 0 Status 11 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:42 0 Status 12 ( 35) NET logical node not in node map
16:03:42 0 Status 12 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:43 0 Status 2 ( 35) NET logical node not in node map
16:03:43 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:43 0 Status 3 ( 35) NET logical node not in node map
16:03:43 0 Status 3 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:43 0 Status 4 ( 35) NET logical node not in node map
16:03:43 0 Status 4 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:43 0 Status 5 ( 35) NET logical node not in node map
16:03:43 0 Status 5 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:43 0 Status 6 ( 35) NET logical node not in node map
16:03:43 0 Status 6 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:43 0 Status 7 ( 35) NET logical node not in node map
16:03:43 0 Status 7 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:43 0 Status 8 ( 35) NET logical node not in node map
16:03:43 0 Status 8 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:43 0 Status 9 ( 35) NET logical node not in node map
16:03:43 0 Status 9 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:44 0 Status 10 ( 35) NET logical node not in node map
16:03:44 0 Status 10 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:44 0 Status 11 ( 35) NET logical node not in node map
16:03:44 0 Status 11 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:44 0 Status 12 ( 35) NET logical node not in node map
16:03:44 0 Status 12 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:45 0 Status 2 ( 35) NET logical node not in node map
16:03:45 0 Status 2 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:45 0 Status 3 ( 35) NET logical node not in node map
16:03:45 0 Status 3 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:45 0 Status 4 ( 35) NET logical node not in node map
16:03:45 0 Status 4 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:45 0 Status 5 ( 35) NET logical node not in node map
16:03:45 0 Status 5 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:45 0 Status 6 ( 35) NET logical node not in node map
16:03:45 0 Status 6 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:45 0 Status 7 ( 35) NET logical node not in node map
16:03:45 0 Status 7 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:45 0 Status 8 ( 35) NET logical node not in node map
16:03:45 0 Status 8 ( 7) NET ( tx) failed (vc_attach ctrl pkt)
16:03:45 0 Status 9 ( 35) NET logical node not in node map
16:03:45 0 Status 9 ( 7) NET ( tx) failed (vc_attach ctrl pkt)

Hugh Brown wrote:

Please can you provide me with the following information:

Output from ‘show_pci -v’
output from netinfo when the problem occurs.
output from sin

Thanks, Hugh.

If you run with just one Epic adapter (172 chipset) do you still have the
problem? I have the same revision Epic adapter here, but I’m only testing
with one adapter and I don’t see any problems. This could be a power supply
problem with 3 adapters installed.

Hugh.

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:

This should be what you as for. Thanks again for the great response. I added comments on which board is which.

Jack

PCI version = 2.10


============== COMMENT ADDED BY JACK =========================
This is the 172 based board
============== END OF ADDED BY JACK =========================

Vendor ID = 10b8h
Device ID = 5h
PCI index = 0h
Class Code = 8020000h Network (Ethernet) ProgIF=0
Revision ID = 9h
Bus number = 0
Device number = 17
Function num = 0
Status Reg = 90h
Command Reg = 117h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 8h un-cacheable
Base Address = IO@dc00h length 256 bytes MEM@dffff000h,32bit length 4096
Expansion ROM = 1bffc0h length 65536 disabled
Max Lat = 28ns
Min Gnt = 8ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 11

============= COMMENT ADDED BY JACK =========================
These next 2 are 171 based boards
============= END OF ADDED BY JACK =========================


Vendor ID = 10b8h
Device ID = 5h
PCI index = 1h
Class Code = 20000h Network (Ethernet) ProgIF=0
Revision ID = 8h
Bus number = 0
Device number = 18
Function num = 0
Status Reg = 90h
Command Reg = 107h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Base Address = IO@d800h length 256 bytes MEM@dfffe000h,32bit length 4096
Expansion ROM = 1bffa0h length 65536 disabled
Max Lat = 28ns
Min Gnt = 8ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 10

Vendor ID = 10b8h
Device ID = 5h
PCI index = 2h
Class Code = 20000h Network (Ethernet) ProgIF=0
Revision ID = 8h
Bus number = 0
Device number = 19
Function num = 0
Status Reg = 90h
Command Reg = 107h
Header type = 0h Single-function
BIST = 0h Build-in-self-test not supported
Latency Timer = 40h
Cache Line Size= 0h
Base Address = IO@d400h length 256 bytes MEM@dfffd000h,32bit length 4096
Expansion ROM = 1bff80h length 65536 disabled
Max Lat = 28ns
Min Gnt = 8ns
PCI Int Pin = 1
PCI Int Pin = INT A
Interrupt line = 9


SID PID PROGRAM PRI STATE BLK CODE DATA
– – Microkernel — ----- — 12976 0
0 1 /boot/sys/Proc32 30f READY — 122k 22122k
0 2 /boot/sys/Slib32 10r RECV 0 53k 4096
0 4 /bin/Fsys 10r RECV 0 77k 10375k
0 5 /bin/Fsys.aha7scsi 22r RECV 0 57k 196k
0 8 idle 0r READY — 0 65k
0 16 //1/bin/Dev 24f RECV 0 32k 225k
0 21 //1/bin/Pipe 10r RECV 0 16k 77k
0 23 //1/bin/Dev.ser 20r RECV 0 16k 24k
0 24 //1/bin/Dev.ser 20r RECV 0 16k 24k
0 25 //1/bin/Dev.ansi 20r RECV 0 40k 122k
0 29 //1/bin/Dev.par 9o RECV 0 8192 12k
0 30 //1/bin/Dev.pty 20r RECV 0 12k 57k
0 34 //1/bin/Fsys.eide 22r RECV 0 61k 114k
0 37 //1/bin/Iso9660fsys 10o RECV 0 28k 61k
0 39 //1/bin/Fsys.floppy 10o RECV 0 20k 40k
0 42 //1/bin/Net 23r RECV 0 32k 126k
0 44 //1/bin/Net.ether1000 20r RECV 0 28k 49k
0 45 //1/bin/Net.epic 20r RECV 0 36k 122k
0 47 //1/bin/Net.epic 20r RECV 0 36k 122k
0 49 //1/bin/Net.epic 20r RECV 0 36k 122k
0 51 //1/bin/nameloc 20o RECV 0 6144 20k
0 52 //1/bin/nameloc 20o REPLY 0 6144 20k
0 149 //1/usr/bin/syslogd 10o RECV 0 36k 32k
0 173 //1/bin/Mqueue 9o RECV 0 20k 4706k
0 174 //1/bin/tinit 10o WAIT -1 8192 28k
0 175 //1/bin/tinit 10o RECV 0 8192 20k
1 180 //1//photon/bin/Photon 12r RECV 0 57k 77k
0 184 //1/
/bin/phfontpfr 12r RECV 0 106k 380k
0 191 //1//ragebios.ms 10o RECV 0 40k 28k
0 193 //1/
/drivers/Pg.rage 12r REPLY 180 122k 159k
2 197 //1/bin/login 10o REPLY 16 24k 20k
0 210 //1/bin/Input 12o RECV 0 30k 28k
0 213 //1/bin/Input 10o RECV 0 30k 4096
3 424 //1//photon/bin/pwm 10o RECV 0 81k 73k
4 700 //1/usr/ucb/Socket 23r RECV 0 225k 344k
4 718 //1/usr/ucb/portmap 10o RECV 723 45k 40k
4 725 //1/usr/ucb/mountd 10o RECV 730 40k 36k
5 727 //1/usr/ucb/pcnfsd 10o RECV 732 61k 45k
4 728 //1/usr/ucb/nfsd 10o REPLY 700 40k 28k
4 731 //1/usr/ucb/inetd 10o RECV 737 36k 32k
3 2194 //1/
/photon/bin/pterm 10o RECV 0 24k 102k
6 2198 //1/bin/sh 10o REPLY 16 31k 45k
6 2516 //1/bin/dumper 29o RECV 0 16k 20k
6 2517 //1//watchdog/watchdog 18o RECV 0 12k 20k
6 2518 //1/
/arcnet/net_ser 17o RECV 0 14k 20k
6 2519 //1//history/history 2o RECV 0 8192 20k
6 2520 //1/
/job_name/job_name 2o RECV 0 16k 20k
6 2521 //1//job_info/job_info 2o RECV 0 24k 28k
6 2522 //1/
/password/password 10o RECV 0 16k 16k
6 2523 //1//jaz/jaz_server 10o RECV 0 8192 12k
6 2524 //1/
/notify/notify 3o REPLY 173 61k 57k
6 2525 //1//casper/log/log 5o REPLY 173 10k 20k
6 2526 //1/
/src/default/spre 10o RECV 0 389k 512k
6 2529 //1//2_rip_dim 13o REPLY 173 47k 106k
6 2530 //1/
/casper/log/log 5o REPLY 173 10k 20k
6 2531 //1//retrievespre 9o REPLY 173 36k 1073k
6 2532 //1/
/imager/imager 9o REPLY 173 13k 122k
6 2533 //1//mach/machspre 14o REPLY 173 15k 45k
6 2534 //1/
/casper/qc/sync 8o REPLY 173 16k 28k
6 2535 //1//sync_bcr/sync_rdr 8o REPLY 173 8192 20k
6 2536 //1/
/super/super 18o REPLY 173 28k 32k
6 2541 //1//sync_bcr/sync_rdr 8o REPLY 16 8192 20k
6 2543 //1/
/arcnet/net_ser 14o RECV 0 14k 20k
6 2546 //1//2_rip_dim 13o REPLY 0 47k 106k
6 2547 //1/
/mach/machspre 5o REPLY 173 15k 45k
6 2548 //1//mach/machspre 6o REPLY 173 15k 45k
6 2549 //1/
/imager/imager 9o REPLY 0 13k 122k
6 2555 //1//casper/qc/sync 8o REPLY 0 16k 28k
6 2817 //1/
/imager/imager 16o REPLY 173 13k 122k
6 2822 //1//imager/imager 16o REPLY 700 13k 122k
6 2823 //1/
/imager/imager 16o REPLY 173 13k 122k
3 3555 //1/*/photon/bin/pterm 10o RECV 0 24k 102k
7 3558 //1/bin/sh 10o WAIT -1 31k 36k
7 3570 //1/bin/sh 10o WAIT -1 31k 36k
7 3907 //1/bin/sin 10o REPLY 1 45k 81k


Hugh Brown wrote:

Please can you provide me with the following information:

Output from ‘show_pci -v’
output from netinfo when the problem occurs.
output from sin

Thanks, Hugh.

I removed two boards and tried testing with a 171 or 172 as the only board using the newer driver you recently provided.


While the newer driver does work better than the older driver with both boards, the 172 is still a problem. Performance is less consisent and sometimes communication completely stops for a while.


I listed the result of "Netstat -Ien4 -w1 " below, although I doubt it helps.


I don’t suspect the system HW as the problem. All HW is purchased (no custom boards), each system has 6 empty slots, and I have 17 identical systems with the same behavior.

Jack

==============================================================
172 Board New Driver, No Comm Failure occurred but performance
degrades over time

input (en4) output input (Total) output
packets errs packets errs colls packets errs packets errs colls
12207 0 18376 0 0 13264 3 18551 1 0
867 0 1302 0 0 869 0 1302 0 0
1 0 2 0 0 2 0 2 0 0
620 0 927 0 0 621 0 927 0 0
847 0 1268 0 0 851 0 1268 0 0
2 0 3 0 0 3 0 3 0 0
812 0 1213 0 0 816 0 1213 0 0
914 0 1370 0 0 917 0 1370 0 0
860 0 1290 0 0 863 0 1290 0 0
914 0 1368 0 0 918 0 1368 0 0
909 0 1361 0 0 913 0 1361 0 0
872 0 1305 0 0 876 0 1305 0 0
911 0 1363 0 0 913 0 1363 0 0
902 0 1349 0 0 902 0 1349 0 0
881 0 1318 0 0 884 0 1318 0 0
906 0 1358 0 0 914 0 1358 0 0
897 0 1341 0 0 902 0 1341 0 0
883 0 1322 0 0 886 0 1322 0 0
877 0 1337 0 0 879 0 1337 0 0
654 0 1002 0 0 656 0 1002 0 0
1 0 2 0 0 4 0 2 0 0
input (en4) output input (Total) output
packets errs packets errs colls packets errs packets errs colls
27570 0 41419 0 0 28686 3 41594 1 0
907 0 1361 0 0 912 0 1361 0 0
875 0 1312 0 0 879 0 1312 0 0
884 0 1322 0 0 887 0 1322 0 0
914 0 1367 0 0 916 0 1367 0 0
890 0 1333 0 0 892 0 1333 0 0
885 0 1326 0 0 887 0 1326 0 0
627 0 939 0 0 644 0 953 0 0
2 0 3 0 0 25 0 18 0 0
694 0 1033 0 0 717 1 1042 0 0
902 0 1351 0 0 904 0 1351 0 0
883 0 1325 0 0 885 0 1326 0 0
878 0 1315 0 0 882 0 1316 0 0
903 0 1353 0 0 906 0 1354 0 0
907 0 1357 0 0 911 0 1358 0 0
881 0 1318 0 0 883 0 1318 0 0
573 0 857 0 0 588 1 864 0 0
141 0 211 0 0 192 0 236 0 0
899 0 1344 0 0 902 0 1345 0 0
540 0 808 0 0 545 0 811 0 0
1 0 2 0 0 23 0 16 0 0
input (en4) output input (Total) output
packets errs packets errs colls packets errs packets errs colls
42394 0 63608 0 0 43722 5 63881 1 0
913 0 1367 0 0 916 0 1367 0 0
893 0 1337 0 0 897 0 1339 0 0
886 0 1328 0 0 889 0 1328 0 0
485 0 725 0 0 580 0 753 0 0
1 0 2 0 0 2 0 2 0 0
862 0 1287 0 0 864 0 1287 0 0
459 0 685 0 0 460 0 685 0 0
90 0 132 0 0 91 0 132 0 0
910 0 1363 0 0 914 0 1363 0 0
417 0 622 0 0 419 0 622 0 0
204 0 303 0 0 207 0 303 0 0
907 0 1358 0 0 910 0 1358 0 0
392 0 585 0 0 395 0 585 0 0
1 0 2 0 0 8 0 2 0 0
1 0 2 0 0 12 0 11 0 0
34 0 49 0 0 38 0 49 0 0
1 0 2 0 0 3 0 2 0 0
809 0 1209 0 0 810 0 1209 0 0
868 0 1298 0 0 870 0 1298 0 0
891 0 1332 0 0 894 0 1332 0 0

\

172 Board New Driver Failed 8 sec’s after start
Failure in my application means that there was no response to a 1 sec
polling message over the control socket 3 or 4 consecutive times

input (en4) output input (Total) output
packets errs packets errs colls packets errs packets errs colls
54542 0 81794 0 0 56136 5 82108 1 0
1 0 2 0 0 4 0 2 0 0
3 0 5 0 0 6 0 5 0 0
409 0 609 0 0 420 0 609 0 0
349 0 562 0 0 350 0 562 0 0
739 0 1120 0 0 740 0 1120 0 0
875 0 1309 0 0 879 0 1309 0 0
826 0 1236 0 0 831 0 1236 0 0
911 0 1362 0 0 915 0 1362 0 0
895 0 1338 0 0 897 0 1338 0 0
645 0 995 0 0 647 0 995 0 0
2 0 2 0 0 5 0 2 0 0
3 0 2 0 0 4 0 2 0 0
0 0 0 0 0 1 0 0 0 0
2 0 1 0 0 2 0 1 0 0
4 0 5 0 0 5 0 5 0 0
0 0 0 0 0 2 0 0 0 0
7 0 8 0 0 13 0 8 0 0
2 0 2 0 0 5 0 2 0 0
12 0 16 0 0 13 0 16 0 0
0 0 0 0 0 2 0 0 0 0

\

171 Board New Driver, this is extremely repeatable. There are
never any time slots under 1200 packets/sec

input (en4) output input (Total) output
packets errs packets errs colls packets errs packets errs colls
54080 1 82410 0 0 54194 1 82529 1 0
1 0 2 0 0 1 0 2 0 0
1 0 2 0 0 1 0 2 0 0
3 0 4 0 0 3 0 4 0 0
211 0 314 0 0 211 0 314 0 0
263 0 406 0 0 271 0 415 0 0
498 0 794 0 0 498 0 794 0 0
917 0 1374 0 0 917 0 1374 0 0
879 0 1318 0 0 879 0 1318 0 0
885 0 1331 0 0 885 0 1331 0 0
824 0 1269 0 0 824 0 1269 0 0
850 0 1316 0 0 850 0 1317 0 0
823 0 1301 0 0 823 0 1301 0 0
839 0 1287 0 0 839 0 1287 0 0
810 0 1291 0 0 810 0 1291 0 0
847 0 1294 0 0 847 0 1294 0 0
871 0 1314 0 0 871 0 1314 0 0
872 0 1324 0 0 872 0 1324 0 0
864 0 1312 0 0 864 0 1312 0 0
850 0 1275 0 0 850 0 1275 0 0
870 0 1302 0 0 870 0 1302 0 0
input (en4) output input (Total) output
packets errs packets errs colls packets errs packets errs colls
67956 1 103583 0 0 68078 1 103712 1 0
853 0 1278 0 0 853 0 1278 0 0
899 0 1344 0 0 899 0 1344 0 0
845 0 1277 0 0 845 0 1277 0 0
833 0 1256 0 0 833 0 1256 0 0
865 0 1329 0 0 865 0 1329 0 0
844 0 1293 0 0 844 0 1293 0 0
847 0 1268 0 0 847 0 1268 0 0
884 0 1321 0 0 884 0 1321 0 0
888 0 1328 0 0 888 0 1328 0 0
878 0 1315 0 0 878 0 1315 0 0
859 0 1302 0 0 859 0 1302 0 0
867 0 1299 0 0 867 0 1299 0 0
899 0 1345 0 0 899 0 1345 0 0
848 0 1271 0 0 848 0 1271 0 0
880 0 1329 0 0 880 0 1329 0 0
836 0 1267 0 0 836 0 1267 0 0
832 0 1289 0 0 832 0 1289 0 0
866 0 1328 0 0 866 0 1329 0 0
849 0 1304 0 0 849 0 1304 0 0
827 0 1262 0 0 827 0 1262 0 0
input (en4) output input (Total) output
packets errs packets errs colls packets errs packets errs colls
85998 1 130910 0 0 86120 1 131040 1 0
849 0 1294 0 0 849 0 1294 0 0
831 0 1277 0 0 831 0 1277 0 0
829 0 1290 0 0 829 0 1290 0 0
804 0 1235 0 0 804 0 1235 0 0
829 0 1241 0 0 829 0 1241 0 0
860 0 1288 0 0 860 0 1288 0 0
843 0 1260 0 0 843 0 1260 0 0
823 0 1230 0 0 823 0 1230 0 0
819 0 1225 0 0 819 0 1225 0 0
830 0 1242 0 0 830 0 1242 0 0
801 0 1202 0 0 801 0 1202 0 0
824 0 1232 0 0 824 0 1232 0 0
855 0 1278 0 0 855 0 1278 0 0
863 0 1291 0 0 863 0 1291 0 0
894 0 1339 0 0 894 0 1339 0 0
910 0 1360 0 0 910 0 1360 0 0
894 0 1335 0 0 894 0 1335 0 0
887 0 1325 0 0 887 0 1325 0 0
905 0 1357 0 0 905 0 1357 0 0
886 0 1324 0 0 886 0 1324 0 0

Can we try and narrow this problem down a bit? As I don’t have your application
to test the driver, can you get the problem to occur with either QNX
networking or TCP/IP and FTP? What version of the TCP/IP stack are you
running (sin ver)? If you can give me a reproducable case that I can test
here, I will be able to resolve your problem, but in all the testing that I
have done, I am unable to reproduce your specific problem.

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:

I removed two boards and tried testing with a 171 or 172 as the only board using the newer driver you recently provided.


While the newer driver does work better than the older driver with both boards, the 172 is still a problem. Performance is less consisent and sometimes communication completely stops for a while.


I listed the result of "Netstat -Ien4 -w1 " below, although I doubt it helps.


I don’t suspect the system HW as the problem. All HW is purchased (no custom boards), each system has 6 empty slots, and I have 17 identical systems with the same behavior.

Jack

I should be able to produce a tiny application which is like my real application. That will take a few days to get to it. I’ll forward you some code then if I can re-produce symptoms.

Jack

Hugh Brown wrote:

Can we try and narrow this problem down a bit? As I don’t have your application
to test the driver, can you get the problem to occur with either QNX
networking or TCP/IP and FTP? What version of the TCP/IP stack are you
running (sin ver)? If you can give me a reproducable case that I can test
here, I will be able to resolve your problem, but in all the testing that I
have done, I am unable to reproduce your specific problem.

Previously, Jack Rosenbloom wrote in qdn.public.qnx4:
I removed two boards and tried testing with a 171 or 172 as the only board using the newer driver you recently provided.


While the newer driver does work better than the older driver with both boards, the 172 is still a problem. Performance is less consisent and sometimes communication completely stops for a while.


I listed the result of "Netstat -Ien4 -w1 " below, although I doubt it helps.


I don’t suspect the system HW as the problem. All HW is purchased (no custom boards), each system has 6 empty slots, and I have 17 identical systems with the same behavior.

Jack