I can not get 6 ethernet cards to work with QNX6.2.1. 5 cards
work fine, but when I try to mount the sixth card
(mount -Tio-net -opci=5 /lib/dll/devc-speedo.so), the system
freezes.
The hardware is a PC-104+ mainboard (Ampro) with 2 on-board
82559ER and 2 PC-104+ adapters with dual 82559ER on board.
The BIOS recognizes and assigns all 6 82559s fine, and “pci -v”
looks as it should. Starting procnto with “-vvv” and then
manually running enum-devices shows five mounts succeeding
and then the system freezes (as when I manually mount the
sixth driver).
Any ideas whats up here ? At one point I got a blown stack
on io-net, so I modified /etc/system/enum/include/net to
start the tcpip stack (I have tried both the v4 and v6
stack) with stacksize=16384.
Rennie
Rennie Allen wrote:
I can not get 6 ethernet cards to work with QNX6.2.1. 5 cards
OMG! Trying to compete with Cisco are we? 
Evan Hillas <blarg@blarg.blarg> wrote:
EH > Rennie Allen wrote:
I can not get 6 ethernet cards to work with QNX6.2.1. 5 cards
EH > OMG! Trying to compete with Cisco are we?
He’s pushing for that 92 Terabit throughput.
Bill Caroselli wrote:
Evan Hillas <> blarg@blarg.blarg> > wrote:
EH > Rennie Allen wrote:
I can not get 6 ethernet cards to work with QNX6.2.1. 5 cards
EH > OMG! Trying to compete with Cisco are we? >
He’s pushing for that 92 Terabit throughput.
How terribly informative…
Rennie Allen wrote:
Bill Caroselli wrote:
Evan Hillas <> blarg@blarg.blarg> > wrote:
EH > Rennie Allen wrote:
I can not get 6 ethernet cards to work with QNX6.2.1. 5 cards
Think retro. Try older models from 3-5 years ago.
QNX drivers tend to be a bit behind the times.
John Nagle
Team Overbot
John Nagle wrote:
Think retro. Try older models from 3-5 years ago.
QNX drivers tend to be a bit behind the times.
Thanks
All 6 cards are the same model (Intel 82559ERs).
5 instances of the driver work perfectly. Only the sixth
instance of the driver causes problems. This does not
appear to be a driver issue, but rather some sort of limit
inherent in io-net…
Rennie
“Rennie Allen” <rallen@csical.com> wrote in message
news:4158A8ED.3050807@csical.com…
John Nagle wrote:
Think retro. Try older models from 3-5 years ago.
QNX drivers tend to be a bit behind the times.
Thanks
All 6 cards are the same model (Intel 82559ERs).
5 instances of the driver work perfectly. Only the sixth
instance of the driver causes problems. This does not
appear to be a driver issue, but rather some sort of limit
inherent in io-net…
How about starting two instances of io-net in the mean time.
Rennie
Rennie Allen <rallen@csical.com> wrote:
John Nagle wrote:
Think retro. Try older models from 3-5 years ago.
QNX drivers tend to be a bit behind the times.
Thanks
All 6 cards are the same model (Intel 82559ERs).
5 instances of the driver work perfectly. Only the sixth
instance of the driver causes problems. This does not
appear to be a driver issue, but rather some sort of limit
inherent in io-net…
There’s no such limit that I’m aware of. Why do
you suspect io-net?
-seanb
/home/seanb >uname -a
QNX seanb 6.3.0 2004/04/29-21:23:19UTC x86pc x86
/home/seanb >ifconfig -a
lo0: flags=8009<UP,LOOPBACK,MULTICAST> mtu 33212
capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
enabled=0<>
inet 127.0.0.1 netmask 0xff000000
en0: flags=8c42<BROADCAST,RUNNING,OACTIVE,SIMPLEX,MULTICAST> mtu 1500
address: 00:e0:29:1e:46:d1
en1: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
enabled=0<>
address: 00:01:02:49:65:ff
en2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:a0:c9:77:e9:25
inet 10.0.0.25 netmask 0xff000000 broadcast 10.255.255.255
en3: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
enabled=0<>
address: 00:02:b3:89:66:7e
en4: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
enabled=0<>
address: 00:0e:0c:34:36:88
en5: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
address: 00:e0:29:44:38:5a
Sean Boudreau wrote:
Rennie Allen <> rallen@csical.com> > wrote:
John Nagle wrote:
Think retro. Try older models from 3-5 years ago.
QNX drivers tend to be a bit behind the times.
Thanks
All 6 cards are the same model (Intel 82559ERs).
5 instances of the driver work perfectly. Only the sixth
instance of the driver causes problems. This does not
appear to be a driver issue, but rather some sort of limit
inherent in io-net…
There’s no such limit that I’m aware of. Why do
you suspect io-net?
Actually I don’t suspect anything in particular. It’s just
that I don’t suspect the driver, since the driver works
fine for up to 5 nics, but the system freezes when the 6th
nic is started. Please bear in mind that the actual 6th
nic works ok, if run alone or with others in an amount
totalling 5 or less.
Rennie
Rennie Allen <rallen@csical.com> wrote:
RA > Sean Boudreau wrote:
Rennie Allen <> rallen@csical.com> > wrote:
John Nagle wrote:
Think retro. Try older models from 3-5 years ago.
QNX drivers tend to be a bit behind the times.
Thanks
All 6 cards are the same model (Intel 82559ERs).
5 instances of the driver work perfectly. Only the sixth
instance of the driver causes problems. This does not
appear to be a driver issue, but rather some sort of limit
inherent in io-net…
There’s no such limit that I’m aware of. Why do
you suspect io-net?
RA > Actually I don’t suspect anything in particular. It’s just
RA > that I don’t suspect the driver, since the driver works
RA > fine for up to 5 nics, but the system freezes when the 6th
RA > nic is started. Please bear in mind that the actual 6th
RA > nic works ok, if run alone or with others in an amount
RA > totalling 5 or less.
RA > Rennie
Sure sounds like a limit somewhere. Either a limit of 5 instances or
some resource like memory for some kind of buffers.
Good luck!
Nick C. wrote:
what mobo you using?
It’s an Ampro.
The good news is that it appears to be a hardware problem. We had a windoze dweeb try to install windoze on this same platform, and
voila ! identical symptoms. I love it when that happens !
Thanks for all the responses.
Rennie