Hello everyone,
We’ve got a serious brouting problem here; maybe anybody could give a
hint?
We are trying to set up a brouter node on an Octagon 5066 machine
using
two Octagon 5500 Ethernet cards (SMC91C96-based). The problem is that
any time a
packet is to be brouted, Net SIGSEGVs on the brouter node.
Net and Net.ether9000 are from Patch D, so, QSSL states, they should
work properly with
SMC91C96 chip, yet they don’t.
I’ve uploaded the problem report (netmaps, various sin outputs, Net’s
postmortem dump and some
other stuff) to our home dir on QUICS (/u/s/swdstp), it’s called
report.tar.F. The test network on which we reproduced the error
contains three nodes, the report describes each of them. NID 4 is the
brouter.
Any help would be greatly appreciated.
Thanks a lot in advance.
Nikolai Gorbunov,
SWD Real-Time Systems
St. Petersburg
Previously, Nikolai Gorbunov wrote in qdn.public.qnx4:
Hello everyone,
We’ve got a serious brouting problem here; maybe anybody could give a
hint?
We are trying to set up a brouter node on an Octagon 5066 machine
using
two Octagon 5500 Ethernet cards (SMC91C96-based). The problem is that
any time a
packet is to be brouted, Net SIGSEGVs on the brouter node.
Net and Net.ether9000 are from Patch D, so, QSSL states, they should
work properly with
SMC91C96 chip, yet they don’t.
I’ve uploaded the problem report (netmaps, various sin outputs, Net’s
postmortem dump and some
other stuff) to our home dir on QUICS (/u/s/swdstp), it’s called
report.tar.F. The test network on which we reproduced the error
contains three nodes, the report describes each of them. NID 4 is the
brouter.
Any help would be greatly appreciated.
Thanks a lot in advance.
I will take a look at this and get back to you.
Hugh.
Nikolai Gorbunov,
SWD Real-Time Systems
St. Petersburg
\
–
Hugh Brown (613) 591-0931 ext. 209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
Previously, Nikolai Gorbunov wrote in qdn.public.qnx4:
Hello everyone,
We’ve got a serious brouting problem here; maybe anybody could give a
hint?
We are trying to set up a brouter node on an Octagon 5066 machine
using
two Octagon 5500 Ethernet cards (SMC91C96-based). The problem is that
any time a
packet is to be brouted, Net SIGSEGVs on the brouter node.
Have you tried this with any other adapters?
Net and Net.ether9000 are from Patch D, so, QSSL states, they should
work properly with
SMC91C96 chip, yet they don’t.
I’ve uploaded the problem report (netmaps, various sin outputs, Net’s
postmortem dump and some
other stuff) to our home dir on QUICS (/u/s/swdstp), it’s called
report.tar.F. The test network on which we reproduced the error
contains three nodes, the report describes each of them. NID 4 is the
brouter.
Any help would be greatly appreciated.
Thanks a lot in advance.
Nikolai Gorbunov,
SWD Real-Time Systems
St. Petersburg
\
–
Hugh Brown (613) 591-0931 ext. 209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
Hugh Brown <hsbrown@qnx.com> ïèøåò â
ñîîáùåíèè:Voyager.001208121608.32495I@qnx.com…
Previously, Nikolai Gorbunov wrote in qdn.public.qnx4:
We are trying to set up a brouter node on an Octagon 5066 machine
using
two Octagon 5500 Ethernet cards (SMC91C96-based). The problem is
that
any time a
packet is to be brouted, Net SIGSEGVs on the brouter node.
Net and Net.ether9000 are from Patch D, so, QSSL states, they
should
work properly with
SMC91C96 chip, yet they don’t.
Have you tried this with any other adapters?
Yep, NE2000’s with Net.ether1000 work just fine.
Previous revisions of Octagon 5500 were based on the 91C94 chip, but
this is a new revision, and this is where problems began.
Previously, Nikolai Gorbunov wrote in qdn.public.qnx4:
Hugh Brown <> hsbrown@qnx.com> > ïèøåò â
ñîîáùåíèè:> Voyager.001208121608.32495I@qnx.com> …
Previously, Nikolai Gorbunov wrote in qdn.public.qnx4:
We are trying to set up a brouter node on an Octagon 5066 machine
using
two Octagon 5500 Ethernet cards (SMC91C96-based). The problem is
that
any time a
packet is to be brouted, Net SIGSEGVs on the brouter node.
Net and Net.ether9000 are from Patch D, so, QSSL states, they
should
work properly with
SMC91C96 chip, yet they don’t.
Have you tried this with any other adapters?
Yep, NE2000’s with Net.ether1000 work just fine.
Previous revisions of Octagon 5500 were based on the 91C94 chip, but
this is a new revision, and this is where problems began.
Can you please describe your system to me, so that I can try to get
similar hardware from Octagon? I need to know what CPU you are using as
well as disk controller etc. We do not have this hardware here, so will
have to try and lay our hands on some.
BTW, I tried to reply via e-mail, but I received an unknown host error
message.
Hugh.
–
Hugh Brown (613) 591-0931 ext. 209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
We also had no luck getting an Ampro PC/104 Ethernet card with an SMC91C96
chip to work. Integrys had us send the card to QNX in California but that
was 4 months or more ago and still no news 
. I’ve just received the
latest product CD so I’ll try again with the driver that is on the CD.
Hopefully it might work better.
“Nikolai Gorbunov” <n.gorbunov@swd.ru> wrote in message
news:90smqj$glr$1@inn.qnx.com…
Hugh Brown <> hsbrown@qnx.com> > ïèøåò â
ñîîáùåíèè:> Voyager.001208121608.32495I@qnx.com> …
Previously, Nikolai Gorbunov wrote in qdn.public.qnx4:
We are trying to set up a brouter node on an Octagon 5066 machine
using
two Octagon 5500 Ethernet cards (SMC91C96-based). The problem is
that
any time a
packet is to be brouted, Net SIGSEGVs on the brouter node.
Net and Net.ether9000 are from Patch D, so, QSSL states, they
should
work properly with
SMC91C96 chip, yet they don’t.
Have you tried this with any other adapters?
Yep, NE2000’s with Net.ether1000 work just fine.
Previous revisions of Octagon 5500 were based on the 91C94 chip, but
this is a new revision, and this is where problems began.
Hugh Brown <hsbrown@qnx.com> ïèøåò â
ñîîáùåíèè:Voyager.001211061128.4881E@qnx.com…
Previously, Nikolai Gorbunov wrote in qdn.public.qnx4:
Previous revisions of Octagon 5500 were based on the 91C94 chip,
but
this is a new revision, and this is where problems began.
Can you please describe your system to me, so that I can try to get
similar hardware from Octagon? I need to know what CPU you are using
as
well as disk controller etc. We do not have this hardware here, so
will
have to try and lay our hands on some.
The CPU is 5066-586 rev. 2 or higher, network card is 5500, rev.
definitely higher than 1.3 (1.3 used a 91C94) - I’ll check this more
thoroughly and get back to you.
There is no disk controller in the system - everything is flash-based.
BTW, I tried to reply via e-mail, but I received an unknown host
error
message.
Yes, unfortunately, we’ve got a DNS problem here… I’ve got my prvate
e-mail account at caiaphas@priest.com, we could use it while problem
persists.
Thank you.
Hugh Brown <hsbrown@qnx.com> ïèøåò â
ñîîáùåíèè:Voyager.001211061128.4881E@qnx.com…
Previously, Nikolai Gorbunov wrote in qdn.public.qnx4:
Can you please describe your system to me, so that I can try to get
similar hardware from Octagon? I need to know what CPU you are using
as
well as disk controller etc. We do not have this hardware here, so
will
have to try and lay our hands on some.
Got it.
CPU is Octagon 5066-586, revision 2.5
NIC is Octagon 5500, revision 1.31, SMC91C96
If anything else needed, please let me know.
Previously, Nikolai Gorbunov wrote in qdn.public.qnx4:
Hugh Brown <> hsbrown@qnx.com> > ïèøåò â
ñîîáùåíèè:> Voyager.001211061128.4881E@qnx.com> …
Previously, Nikolai Gorbunov wrote in qdn.public.qnx4:
Can you please describe your system to me, so that I can try to get
similar hardware from Octagon? I need to know what CPU you are using
as
well as disk controller etc. We do not have this hardware here, so
will
have to try and lay our hands on some.
Got it.
CPU is Octagon 5066-586, revision 2.5
NIC is Octagon 5500, revision 1.31, SMC91C96
If anything else needed, please let me know.
Thanks, I’ll try and organise the hardware and get back to you.
–
Hugh Brown (613) 591-0931 ext. 209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8