Net.ether82557 large packet size problem

QNX Newsgroups (Archives) qdn.public.qnx4
1

Hello,

We got 2 new system that have an onboard NIC 82558 and we are using the
Net.ether82557 version 4.25G driver with QNX 4.25D and TCPIP 4.25C.

The network card seams to works fine except when we try to transmit large
packet sizes. We can easly reproduce this by using the “ping -s2000
hostname” command. For small packets sizes we can ping the unit no problem,
for large packet sizes of 2000+ there is no response. Same thing, when we
telnet to the unit, it works fine, but when we try to view a console or a
file with too much information the telnet stop responding.

This problem happens on both units and running netinfo do not display errors
or OWC.

We disabled the onbard NIC and installed a 3COM network card and that solved
the problem, so the network is fine, but we will be receiving a lot of these
units and will like to be able to use the onboard NIC.

Any idea? have someone run into something like this?

I have included the output of “show_pci -v” and “netinfo -l”.


begin 666 netinfo.txt
M5&]T86P@3G5M8F5R($]F($YE="!$<FEV97(@4VQO=’,Z(#(-"@T1’)I=F5R
M(%-L;W0@,#H@($1R:79E<B!0:60@,S<@($QO9VEC86P@3F5T(#$@($YE=’=O
M<FL@0V%R9#H@171H97)N970O#0I3<&5E9&@.B X,C4U."!"+5-T97 @171H
M97)N970@0V]N=’)O;&QE<@T(" @(%9E;F1O<B!)1" N+BXN+BXN+BXN+BXN
M+BXN+BXN+BXN+BX@,’@X,#@V#0H@(" @1&5V:6-E($E$(“XN+BXN+BXN+BXN
M+BXN+BXN+BXN+BXN+B P>#$R,CD-“B @(”!3=6)S>7-T96T@240@+BXN+BXN
M+BXN+BXN+BXN+BXN+BXN(#!X,0T*(” @(%-U8G-Y<W1E;2!696YD;W(@240@
M+BXN+BXN+BXN+BXN+BX@,’@X,#@V#0H@(" @4F5V:7-I;VX@+BXN+BXN+BXN
M+BXN+BXN+BXN+BXN+BXN+B P>#4-“B @(”!0:‘ES:6-A;"!.;V1E($E$(“XN
M+BXN+BXN+BXN+BXN+BXN(# P.3!$-B P,# R-38-“B @(”!-961I82!2871E
M(“XN+BXN+BXN+BXN+BXN+BXN+BXN+BXN(#$P36(O<PT*(” @($UT=2 N+BXN
M+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BXN+BX@,34Q- T*(” @($AA<F1W87)E
M($EN=&5R<G5P=" N+BXN+BXN+BXN+BXN+BX@,3$-"@T*(" @(%1O=&%L(%!A
M8VME=’,@5’AD($]+(“XN+BXN+BXN+BXN+BX@,3 R.0T*(” @(%1O=&%L(%!A
M8VME=’,@5’AD($)A9" N+BXN+BXN+BXN+BX@, T*(" @(%1X($-O;&QI<VEO
M;B!%<G)O<G,@+BXN+BXN+BXN+BXN+BX@, T*(" @(%1X($-O;&QI<VEO;B!%
M<G)O<G,@&%B;W)T960I("XN+BX@, T(" @($-A<G)I97(@4V5N<V4@3&]S
M="!O;B!4>" N+BXN+BXN+BX@, T*(" @($9)1D@56YD97)R=6YS($1U<FEN
M9R!4>" N+BXN+BXN+BX@, T*(" @(%1X(&1E9F5R<F5D(“XN+BXN+BXN+BXN
M+BXN+BXN+BXN+BX@, T*(” @($]U="!O9B!7:6YD;W<@0V]L;&ES:6]N<R N
M+BXN+BXN+BX@, T*#0H@(" @5&]T86P@4&%C:V5T<R!2>&0@3TL@+BXN+BXN
M+BXN+BXN+B Q,3<W#0H@(" @5&]T86P@4G@@17)R;W)S(“XN+BXN+BXN+BXN
M+BXN+BXN+B P#0H@(” @1DE&3R!/=F5R<G5N<R!$=7)I;F<@4G@@+BXN+BXN
M+BXN+B P#0H@(" @06QI9VYM96YT(&5R<F]R<R N+BXN+BXN+BXN+BXN+BXN
M+B P#0H@(" @0U)#(&5R<F]R<R N+BXN+BXN+BXN+BXN+BXN+BXN+BXN+B P

#0H-"@T1’)I=F5R(%-L;W0@,3H@(%5N=7-E9 T
`

end

begin 666 show_pci.txt
M#0I00TD@=F5R<VEO;B @(" ](#(N,3 -"@T5F5N9&]R($E$(" @(" @/2 X
M,#@V:“P@24Y414P@0T]24$]2051)3TX-“D1E=FEC92!)1” @(” @(#T@-S$P
M,&@L( T4$-)(&EN9&5X(" @(" @/2 P: T0VQA<W,@0V]D92 @(" @/2 P
M-C P,#!H($)R:61G92 H2&]S="]00TDI(%!R;V=)1CTP#0I2979I<VEO;B!)
M1" @(" ](#%H#0I"=7,@;G5M8F5R(" @(" ](# -"D1E=FEC92!N=6UB97(@
M(#T@, T1G5N8W1I;VX@;G5M(" @/2 P#0I3=&%T=7,@4F5G(" @(" ](#(R
M,#!H#0I#;VUM86YD(%)E9R @(" ](#9H#0I(96%D97(@=‘EP92 @(" ](#!H
M(%-I;F=L92UF=6YC=&EO;@T0DE35" @(" @(" @(" @/2 P:"!"=6EL9"UI
M;BUS96QF+71E<W0@;F]T(’-U<’!O<G1E9 T3&%T96YC>2!4:6UE<B @/2 T
M,&@-“D-A8VAE($QI;F4@4VEZ93T@,&@@#0H-“DUA>”!,870@(” @(" @(#T@
M,&YS#0I-:6X@1VYT(" @(" @(" ](#!N<PT4$-)($EN="!0:6X@(" @/2 P
M#0I00TD@26YT(%!I;B @(" ]($Y##0I);G1E<G)U<'0@;&EN92 ](# -"@T
M5F5N9&]R($E$(" @(" @/2 X,#@V:“P@24Y414P@0T]24$]2051)3TX-“D1E
M=FEC92!)1” @(” @(#T@-S$Q,&@L( T4$-)(&EN9&5X(" @(" @/2 P: T
M0VQA<W,@0V]D92 @(" @/2 P-C Q,#!H($)R:61G92 H4$-)+TE302D@4’)O
M9TE&/3 -“E)E=FES:6]N($E$(” @(#T@,6@-“D)U<R!N=6UB97(@(” @(#T@
M, T1&5V:6-E(&YU;6)E<B @/2 W#0I&=6YC=&EO;B!N=6T@(" ](# -“E-T
M871U<R!296<@(” @(#T@,C@P: T0V]M;6%N9"!296<@(" @/2!F: T2&5A
M9&5R('1Y<&4@(" @/2 P:"!-=6QT:2UF=6YC=&EO;@T0DE35" @(" @(" @
M(" @/2 P:"!"=6EL9"UI;BUS96QF+71E<W0@;F]T(’-U<’!O<G1E9 T3&%T
M96YC>2!4:6UE<B @/2 P: T0V%C:&4@3&EN92!3:7IE/2 P:" -"@T36%X
M($QA=" @(" @(" @/2 P;G,-“DUI;B!’;G0@(” @(" @(#T@,&YS#0I00TD@
M26YT(%!I;B @(" ](# -“E!#22!);G0@4&EN(” @(#T@3D,-“DEN=&5R<G5P
M=”!L:6YE(#T@, T#0I696YD;W(@240@(" @(" ](#@P.#9H+"!)3E1%3"!#
M3U)03U)!5$E/3@T1&5V:6-E($E$(" @(" @/2 W,3$Q:“P@#0I00TD@:6YD
M97@@(” @(" ](#!H#0I#;&%S<R!#;V1E(" @(" ](# Q,#$X,&@@36%S<R!3
M=&]R86=E(“A)1$4I(%!R;V=)1CTQ,C@-“E)E=FES:6]N($E$(” @(#T@,6@-
M"D)U<R!N=6UB97(@(” @(#T@, T1&5V:6-E(&YU;6)E<B @/2 W#0I&=6YC
M=&EO;B!N=6T@(" ](#$-“E-T871U<R!296<@(” @(#T@,C@P: T0V]M;6%N
M9"!296<@(" @/2 U: T2&5A9&5R(‘1Y<&4@(" @/2 P:"!3:6YG;&4M9G5N
M8W1I;VX-“D))4U0@(” @(" @(" @(#T@,&@@0G5I;&0M:6XM<V5L9BUT97-T
M(&YO="!S=7!P;W)T960-“DQA=&5N8WD@5&EM97(@(#T@-#!H#0I#86-H92!,
M:6YE(%-I>F4](#!H( T*($E/0&8P,#!H(&QE;F=T:” Q-B!B>71E<PT36%X
M($QA=" @(" @(" @/2 P;G,-“DUI;B!’;G0@(” @(" @(#T@,&YS#0I00TD@
M26YT(%!I;B @(" ](# -“E!#22!);G0@4&EN(” @(#T@3D,-“DEN=&5R<G5P
M=”!L:6YE(#T@, T#0I696YD;W(@240@(" @(" ](#@P.#9H+"!)3E1%3"!#
M3U)03U)!5$E/3@T1&5V:6-E($E$(" @(" @/2 W,3$R:“P@#0I00TD@:6YD
M97@@(” @(" ](#!H#0I#;&%S<R!#;V1E(" @(" ](#!C,#,P,&@@4V5R:6%L
M($)U<R H56YI=F5R<V%L(%-E<FEA;"!"=7,I(%!R;V=)1CTP#0I2979I<VEO
M;B!)1" @(" ](#%H#0I"=7,@;G5M8F5R(" @(" ](# -"D1E=FEC92!N=6UB
M97(@(#T@-PT1G5N8W1I;VX@;G5M(" @/2 R#0I3=&%T=7,@4F5G(" @(" ]
M(#(X,&@-“D-O;6UA;F0@4F5G(” @(#T@,&@-“DAE861E<B!T>7!E(” @(#T@
M,&@@4VEN9VQE+69U;F-T:6]N#0I"25-4(" @(" @(" @(" ](#!H($)U:6QD
M+6EN+7-E;&8M=&5S="!N;W0@<W5P<&]R=&5D#0I,871E;F-Y(%1I;65R(" ]
M(#0P: T0V%C:&4@3&EN92!3:7IE/2 P:" -“B!)3T!E,# P:”!L96YG=&@@
M,S(@8GET97,-“DUA>”!,870@(" @(" @(#T@,&YS#0I-:6X@1VYT(" @(" @
M(" ](#!N<PT4$-)($EN="!0:6X@(" @/2 T#0I00TD@26YT(%!I;B @(" ]
M($E.5"!$#0I);G1E<G)U<‘0@;&EN92 ](&YO(&-O;FYE8W1I;VX-"@T5F5N
M9&]R($E$(" @(" @/2 X,#@V:“P@24Y414P@0T]24$]2051)3TX-“D1E=FEC
M92!)1” @(” @(#T@-S$Q,V@L( T4$-)(&EN9&5X(" @(" @/2 P: T0VQA
M<W,@0V]D92 @(" @/2 P-C@P,#!H($)R:61G92 H3W1H97(@,3(X2!0<F]G
M248], T4F5V:7-I;VX@240@(" @/2 Q: T0G5S(&YU;6)E<B @(" @/2 P
M#0I$979I8V4@;G5M8F5R(" ](#<-“D9U;F-T:6]N(&YU;2 @(#T@,PT4W1A
M='5S(%)E9R @(" @/2 R.#!H#0I#;VUM86YD(%)E9R @(" ](#-H#0I(96%D
M97(@='EP92 @(" ](#!H(%-I;F=L92UF=6YC=&EO;@T0DE35” @(" @(" @
M(" @/2 P:"!"=6EL9"UI;BUS96QF+71E<W0@;F]T(’-U<’!O<G1E9 T3&%T
M96YC>2!4:6UE<B @/2 P: T0V%C:&4@3&EN92!3:7IE/2 P:" -"@T36%X
M($QA=" @(" @(" @/2 P;G,-“DUI;B!’;G0@(” @(" @(#T@,&YS#0I00TD@
M26YT(%!I;B @(" ](# -“E!#22!);G0@4&EN(” @(#T@3D,-“DEN=&5R<G5P
M=”!L:6YE(#T@, T#0I696YD;W(@240@(" @(" ](#@P.#9H+"!)3E1%3"!#
M3U)03U)!5$E/3@T1&5V:6-E($E$(" @(" @/2 Q,C(Y:“P@.#(U-3<O.”!%
M=&AE<FYE="!!9&%P=&5R#0I00TD@:6YD97@@(" @(" ](#!H#0I#;&%S<R!#
M;V1E(" @(" ](# R,# P,&@@3F5T=V]R:R H171H97)N970I(%!R;V=)1CTP
M#0I2979I<VEO;B!)1" @(" ](#5H#0I"=7,@;G5M8F5R(" @(" ](# -"D1E
M=FEC92!N=6UB97(@(#T@,30-"D9U;F-T:6]N(&YU;2 @(#T@, T4W1A='5S
M(%)E9R @(" @/2 R.#!H#0I#;VUM86YD(%)E9R @(" ](#=H#0I(96%D97(@
M='EP92 @(" ](#!H(%-I;F=L92UF=6YC=&EO;@T0DE35" @(" @(" @(" @
M/2 P:"!"=6EL9"UI;BUS96QF+71E<W0@;F]T(’-U<’!O<G1E9 T3&%T96YC
M>2!4:6UE<B @/2 T,&@-“D-A8VAE($QI;F4@4VEZ93T@,3!H('5N+6-A8VAE
M86)L90T0F%S92!!9&1R97-S(" @/2!-14U 930Q,#$P,#!H+%!R969E=&-H
M86)L92PS,F)I="!L96YG=&@@-# Y-B!)3T!E-# P:"!L96YG=&@@,S(@8GET
M97,@345-0&4T,# P,# P:“PS,F)I=”!L96YG=&@@,3 T.#4W-@T4W5B<WES
M=&5M(%9E;F1O<B!)1” ](#@P.#9H#0I3=6)S>7-T96T@240@(" @(" @(#T@
M,6@-“D5X<&%N<VEO;B!23TT@(#T@93 P,# P,#!H(”!L96YG=&@@,3 T.#4W
M-B!D:7-A8FQE9 T36%X($QA=" @(" @(" @/2 U-FYS#0I-:6X@1VYT(" @
M(" @(" ](#AN<PT4$-)($EN="!0:6X@(" @/2 Q#0I00TD@26YT(%!I;B @
M(" ]($E.5"!!#0I);G1E<G)U<‘0@;&EN92 ](#$Q#0H-“E9E;F1O<B!)1” @
M(" @(#T@.3 P-&@L($%D87!T96,@26YC+@T1&5V:6-E($E$(" @(" @/2 X
M,#<X:“P@04E#+3<X.# @4T-322!C;VYT<F]L;&5R#0I00TD@:6YD97@@(” @
M(" ](#!H#0I#;&%S<R!#;V1E(" @(" ](# Q,# P,&@@36%S<R!3=&]R86=E
M(“A30U-)2!0<F]G248], T4F5V:7-I;VX@240@(” @/2 P: T0G5S(&YU
M;6)E<B @(" @/2 P#0I$979I8V4@;G5M8F5R(" ](#$U#0I&=6YC=&EO;B!N
M=6T@(" ](# -“E-T871U<R!296<@(” @(#T@,C@P: T0V]M;6%N9"!296<@
M(" @/2 P: T2&5A9&5R(‘1Y<&4@(" @/2 P:"!3:6YG;&4M9G5N8W1I;VX-
M"D))4U0@(" @(" @(" @(#T@,&@@0G5I;&0M:6XM<V5L9BUT97-T(&YO="!S
M=7!P;W)T960-“DQA=&5N8WD@5&EM97(@(#T@-#!H#0I#86-H92!,:6YE(%-I
M>F4](#AH('5N+6-A8VAE86)L90T0F%S92!!9&1R97-S(" @/2!)3T!E.# P
M:"!L96YG=&@@,C4V(&)Y=&5S($U%34!E-#$P,# P,&@L,S)B:70@;&5N9W1H
M(#0P.38-“D5X<&%N<VEO;B!23TT@(#T@93$P,# P,#!H(”!L96YG=&@@-C4U
M,S8@9&ES86)L960-“DUA>”!,870@(" @(" @(#T@.&YS#0I-:6X@1VYT(" @
M(" @(" ](#AN<PT4$-)($EN=”!0:6X@(" @/2 Q#0I00TD@26YT(%!I;B @
M(" ]($E.5"!!#0I);G1E<G)U<‘0@;&EN92 ](#$P#0H-“E9E;F1O<B!)1” @
M(" @(#T@,3 R8V@L($-H:7!S(“8@5&5C:&YO;&]G:65S#0I$979I8V4@240@
M(” @(" ](&,P:“P@#0I00TD@:6YD97@@(” @(" ](#!H#0I#;&%S<R!#;V1E
M(" @(" ](# S,# P,&@@1&ES<&QA>2 H5D=!2!0<F]G248], T4F5V:7-I
M;VX@240@(" @/2 V-&@-“D)U<R!N=6UB97(@(” @(#T@, T1&5V:6-E(&YU
M;6)E<B @/2 Q-PT1G5N8W1I;VX@;G5M(" @/2 P#0I3=&%T=7,@4F5G(" @
M(" ](#(X,&@-“D-O;6UA;F0@4F5G(” @(#T@.#-H#0I(96%D97(@=‘EP92 @
M(" ](#!H(%-I;F=L92UF=6YC=&EO;@T0DE35" @(" @(" @(" @/2 P:"!"
M=6EL9"UI;BUS96QF+71E<W0@;F]T(’-U<’!O<G1E9 T3&%T96YC>2!4:6UE
M<B @/2 P: T0V%C:&4@3&EN92!3:7IE/2 P:" -"D)A<V4@061D<F5S<R @
M(#T@345-0&4R,# P,# P:“PS,F)I=”!L96YG=&@@,38W-S<R,38-"E-U8G-Y
M<W1E;2!696YD;W(@240@/2 Q,#)C: T4W5B<WES=&5M($E$(" @(" @(" ]
M(&,P: T36%X($QA=" @(" @(" @/2 P;G,-“DUI;B!’;G0@(” @(" @(#T@
M,&YS#0I00TD@26YT(%!I;B @(" ](#$-“E!#22!);G0@4&EN(” @(#T@24Y4
M($$-“DEN=&5R<G5P=”!L:6YE(#T@;F@8V]N;F5C=&EO;@T#0I)4E$@4F]U
M=&EN9R @(" ](&)U<STP(’-L;W0],2!D979I8V4],C -“B @(” @(" @(" @
M(" @(" @3F@8V%R9"!C;VYF:6=U<F5D(&EN(’-L;W0-“B @(” @(" @(" @
M(" @(" @24Y403TS+#0L-2PW+#DL,3 L,3$L,3(L,30L,34@4VQO=#(Z24Y4
M1"!3;&]T,SI)3E1#(%-L;W0T.DE.5$(@36]T:&5R8F]A<F0Z24Y40R!-;W1H
M97)B;V%R9#I)3E1"#0H@(" @(" @(" @(" @(" @($E.5$(],RPT+#4L-RPY
M+#$P+#$Q+#$R+#$T+#$U(%-L;W0R.DE.5$$@4VQO=#,Z24Y41"!3;&]T-#I)
M3E1#($UO=&AE<F)O87)D.DE.5$(@36]T:&5R8F]A<F0Z24Y40PT*(" @(" @
M(" @(" @(" @("!)3E1#/3,L-“PU+#<L.2PQ,“PQ,2PQ,BPQ-“PQ-2!3;&]T
M,CI)3E1”(%-L;W0S.DE.5$$@4VQO=#0Z24Y41”!-;W1H97)B;V%R9#I)3E1!
M($UO=&AE<F)O87)D.DE.5$0-“B @(” @(” @(" @(" @(" @24Y41#TS+#0L
M-2PW+#DL,3 L,3$L,3(L,30L,34@4VQO=#(Z24Y40R!3;&]T,SI)3E1"(%-L
M;W0T.DE.5$$@36]T:&5R8F]A<F0Z24Y41"!-;W1H97)B;V%R9#I)3E1!#0H-
M"DE242!2;W5T:6YG(" @(#T@8G5S/3 @<VQO=#TR(&1E=FEC93TQ.0T*(" @
M(" @(" @(" @(" @("!.;R!C87)D(&-O;F9I9W5R960@:6X@<VQO= T*(" @
M(" @(" @(" @(" @("!)3E1!/3,L-“PU+#<L.2PQ,“PQ,2PQ,BPQ-“PQ-2!3
M;&]T,3I)3E1”(%-L;W0S.DE.5$0@4VQO=#0Z24Y40R!-;W1H97)B;V%R9#I)
M3E1”($UO=&AE<F)O87)D.DE.5$,-“B @(” @(” @(" @(" @(" @24Y40CTS
M+#0L-2PW+#DL,3 L,3$L,3(L,30L,34@4VQO=#$Z24Y40R!3;&]T,SI)3E1!
M(%-L;W0T.DE.5$0@36]T:&5R8F]A<F0Z24Y402!-;W1H97)B;V%R9#I)3E1$
M#0H@(" @(" @(" @(" @(" @($E.5$,],RPT+#4L-RPY+#$P+#$Q+#$R+#$T
M+#$U(%-L;W0Q.DE.5$0@4VQO=#,Z24Y40B!3;&]T-#I)3E1!($UO=&AE<F)O
M87)D.DE.5$0@36]T:&5R8F]A<F0Z24Y400T*(" @(" @(" @(" @(" @("!)
M3E1$/3,L-“PU+#<L.2PQ,“PQ,2PQ,BPQ-“PQ-2!3;&]T,3I)3E1!(%-L;W0S
M.DE.5$,@4VQO=#0Z24Y40B!-;W1H97)B;V%R9#I)3E1#($UO=&AE<F)O87)D
M.DE.5$(-”@T25)1(%)O=71I;F<@(" @/2!B=7,],"!S;&]T/3,@9&5V:6-E
M/3$X#0H@(" @(" @(" @(" @(" @($YO(&-A<F0@8V]N9FEG=7)E9"!I;B!S
M;&]T#0H@(" @(" @(" @(" @(" @($E.5$$],RPT+#4L-RPY+#$P+#$Q+#$R
M+#$T+#$U(%-L;W0Q.DE.5$,@4VQO=#(Z24Y40B!3;&]T-#I)3E1$($UO=&AE
M<F)O87)D.DE.5$$@36]T:&5R8F]A<F0Z24Y41 T(” @(” @(" @(" @(" @
M("!)3E1"/3,L-“PU+#<L.2PQ,“PQ,2PQ,BPQ-“PQ-2!3;&]T,3I)3E1$(%-L
M;W0R.DE.5$,@4VQO=#0Z24Y402!-;W1H97)B;V%R9#I)3E1$($UO=&AE<F)O
M87)D.DE.5$$-“B @(” @(” @(” @(” @(" @24Y40STS+#0L-2PW+#DL,3 L
M,3$L,3(L,30L,34@4VQO=#$Z24Y402!3;&]T,CI)3E1$(%-L;W0T.DE.5$(@
M36]T:&5R8F]A<F0Z24Y40R!-;W1H97)B;V%R9#I)3E1"#0H@(" @(" @(" @
M(" @(" @($E.5$0],RPT+#4L-RPY+#$P+#$Q+#$R+#$T+#$U(%-L;W0Q.DE.
M5$(@4VQO=#(Z24Y402!3;&]T-#I)3E1#($UO=&AE<F)O87)D.DE.5$(@36]T
M:&5R8F]A<F0Z24Y40PT*#0I)4E$@4F]U=&EN9R @(" ](&)U<STP(’-L;W0]
M-"!D979I8V4],30-“E9E;F1O<B!)1” @(" @(#T@.# X-F@L($E.5$5,($-/
M4E!/4D%424].#0I$979I8V4@240@(" @(" ](#$R,CEH+" X,C4U-R\X($5T
M:&5R;F5T($%D87!T97(-“B @(” @(" @(" @(" @(" @24Y403TS+#0L-2PW
M+#DL,3 L,3$L,3(L,30L,34@4VQO=#$Z24Y41"!3;&]T,CI)3E1#(%-L;W0S
M.DE.5$(@36]T:&5R8F]A<F0Z24Y41"!-;W1H97)B;V%R9#I)3E1!#0H@(" @
M(" @(" @(" @(" @($E.5$(],RPT+#4L-RPY+#$P+#$Q+#$R+#$T+#$U(%-L
M;W0Q.DE.5$$@4VQO=#(Z24Y41"!3;&]T,SI)3E1#($UO=&AE<F)O87)D.DE.
M5$,@36]T:&5R8F]A<F0Z24Y40@T*(" @(" @(" @(" @(" @("!)3E1#/3,L
M-“PU+#<L.2PQ,“PQ,2PQ,BPQ-“PQ-2!3;&]T,3I)3E1”(%-L;W0R.DE.5$$@
M4VQO=#,Z24Y41”!-;W1H97)B;V%R9#I)3E1”($UO=&AE<F)O87)D.DE.5$,-
M"B @(" @(" @(" @(" @(" @24Y41#TS+#0L-2PW+#DL,3 L,3$L,3(L,30L
M,34@4VQO=#$Z24Y40R!3;&]T,CI)3E1"(%-L;W0S.DE.5$$@36]T:&5R8F]A
M<F0Z24Y402!-;W1H97)B;V%R9#I)3E1$#0H-“DE242!2;W5T:6YG(” @(#T@
M8G5S/3 @;6]T:&5R8F]A<F0@9&5V:6-E/3$U#0I696YD;W(@240@(" @(" ]
M(#DP,#1H+"!!9&%P=&5C($EN8RX-“D1E=FEC92!)1” @(" @(#T@.# W.&@L
M($%)0RTW.#@P(%-#4TD@8V]N=’)O;&QE<@T*(" @(" @(" @(" @(" @("!)
M3E1!/3,L-“PU+#<L.2PQ,“PQ,2PQ,BPQ-“PQ-2!3;&]T,3I)3E1#(%-L;W0R
M.DE.5$(@4VQO=#,Z24Y402!3;&]T-#I)3E1$($UO=&AE<F)O87)D.DE.5$0-
M"B @(” @(” @(” @(" @(" @24Y40CTS+#0L-2PW+#DL,3 L,3$L,3(L,30L
M,34@4VQO=#$Z24Y40B!3;&]T,CI)3E1!(%-L;W0S.DE.5$0@4VQO=#0Z24Y4
M0R!-;W1H97)B;V%R9#I)3E1##0H@(" @(" @(" @(" @(" @($E.5$,],RPT
M+#4L-RPY+#$P+#$Q+#$R+#$T+#$U(%-L;W0Q.DE.5$$@4VQO=#(Z24Y41"!3
M;&]T,SI)3E1#(%-L;W0T.DE.5$(@36]T:&5R8F]A<F0Z24Y40@T*(" @(" @
M(" @(" @(" @("!)3E1$/3,L-“PU+#<L.2PQ,“PQ,2PQ,BPQ-“PQ-2!3;&]T
M,3I)3E1$(%-L;W0R.DE.5$,@4VQO=#,Z24Y40B!3;&]T-#I)3E1!($UO=&AE
M<F)O87)D.DE.5$$-”@T25)1(%)O=71I;F<@(" @/2!B=7,],"!M;W1H97)B
M;V%R9"!D979I8V4],3<-“E9E;F1O<B!)1” @(" @(#T@,3 R8V@L($-H:7!S
M(“8@5&5C:&YO;&]G:65S#0I$979I8V4@240@(” @(" ](&,P:“P@#0H@(” @
M(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @(" @
M(" @(" @(" @(" @(" @#0I)4E$@4F]U=&EN9R @(" ](&)U<STP(&UO=&AE
M<F)O87)D(&1E=FEC93TW(&9U;F,],0T5F5N9&]R($E$(” @(” @/2 X,#@V
M:“P@24Y414P@0T]24$]2051)3TX-“D1E=FEC92!)1” @(” @(#T@-S$Q,&@L
M( T5F5N9&]R($E$(" @(" @/2 X,#@V:“P@24Y414P@0T]24$]2051)3TX-
M"D1E=FEC92!)1” @(" @(#T@-S$Q,6@L( T5F5N9&]R($E$(" @(" @/2 X
M,#@V:“P@24Y414P@0T]24$]2051)3TX-“D1E=FEC92!)1” @(” @(#T@-S$Q
M,F@L( T5F5N9&]R($E$(" @(" @/2 X,#@V:“P@24Y414P@0T]24$]2051)
M3TX-“D1E=FEC92!)1” @(” @(#T@-S$Q,V@L( T(" @(" @(" @(" @(" @
M("!)3E1!/3,L-“PU+#<L.2PQ,“PQ,2PQ,BPQ-“PQ-2!3;&]T,3I)3E1$(%-L
M;W0R.DE.5$,@4VQO=#,Z24Y40B!3;&]T-#I)3E1!($UO=&AE<F)O87)D.DE.
M5$0-“B @(” @(” @(” @(” @(" @24Y40CTS+#0L-2PW+#DL,3 L,3$L,3(L
M,30L,34@4VQO=#$Z24Y402!3;&]T,CI)3E1$(%-L;W0S.DE.5$,@4VQO=#0Z
M24Y40B!-;W1H97)B;V%R9#I)3E1##0H@(" @(" @(" @(" @(" @($E.5$,]
M,RPT+#4L-RPY+#$P+#$Q+#$R+#$T+#$U(%-L;W0Q.DE.5$(@4VQO=#(Z24Y4
M02!3;&]T,SI)3E1$(%-L;W0T.DE.5$,@36]T:&5R8F]A<F0Z24Y40@T*(" @
M(" @(" @(" @(" @("!)3E1$/3,L-"PU+#<L.2PQ,"PQ,2PQ,BPQ-“PQ-2!3
M;&]T,3I)3E1#(%-L;W0R.DE.5$(@4VQO=#,Z24Y402!3;&]T-#I)3E1$($UO
4=&AE<F)O87)D.DE.5$$-”@T*#0H
end

2

I have tested the driver here with the same chipset and it works fine.
I can ping with any size packet without any problems. Can you please
post the ‘netinfo’ output after this happens?

Previously, Cesar Hernandez wrote in qdn.public.qnx4:

Hello,

We got 2 new system that have an onboard NIC 82558 and we are using the
Net.ether82557 version 4.25G driver with QNX 4.25D and TCPIP 4.25C.

The network card seams to works fine except when we try to transmit large
packet sizes. We can easly reproduce this by using the “ping -s2000
hostname” command. For small packets sizes we can ping the unit no problem,
for large packet sizes of 2000+ there is no response. Same thing, when we
telnet to the unit, it works fine, but when we try to view a console or a
file with too much information the telnet stop responding.

This problem happens on both units and running netinfo do not display errors
or OWC.

We disabled the onbard NIC and installed a 3COM network card and that solved
the problem, so the network is fine, but we will be receiving a lot of these
units and will like to be able to use the onboard NIC.

Any idea? have someone run into something like this?

I have included the output of “show_pci -v” and “netinfo -l”.

3

Well the netinfo posted is the one collected after some ping commands
jammed. The unit still remains functional and will continue to respond to
further commands (only if using small packets).

Tomorrow we will receive another unit, I will then be able to perform
further tests in-house, these traces were collected from a client site and
since we disabled the NIC and replaced it with a 3COM card I cannot collect
more traces at the moment.

What is the latest version of the driver, is it the one from patchE ?

“Hugh Brown” <hsbrown@qnx.com> wrote in message
news:Voyager.020207134342.22836H@node90.ott.qnx.com…

I have tested the driver here with the same chipset and it works fine.
I can ping with any size packet without any problems. Can you please
post the ‘netinfo’ output after this happens?

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Hello,

We got 2 new system that have an onboard NIC 82558 and we are using the
Net.ether82557 version 4.25G driver with QNX 4.25D and TCPIP 4.25C.

The network card seams to works fine except when we try to transmit
large
packet sizes. We can easly reproduce this by using the “ping -s2000
hostname” command. For small packets sizes we can ping the unit no
problem,
for large packet sizes of 2000+ there is no response. Same thing, when
we
telnet to the unit, it works fine, but when we try to view a console or
a
file with too much information the telnet stop responding.

This problem happens on both units and running netinfo do not display
errors
or OWC.

We disabled the onbard NIC and installed a 3COM network card and that
solved
the problem, so the network is fine, but we will be receiving a lot of
these
units and will like to be able to use the onboard NIC.

Any idea? have someone run into something like this?

I have included the output of “show_pci -v” and “netinfo -l”.

4

Previously, Cesar Hernandez wrote in qdn.public.qnx4:

Well the netinfo posted is the one collected after some ping commands
jammed. The unit still remains functional and will continue to respond to
further commands (only if using small packets).

The netinfo that you posted is the ‘netinfo -l’ output. I just want the
‘netinfo’ output.

Tomorrow we will receive another unit, I will then be able to perform
further tests in-house, these traces were collected from a client site and
since we disabled the NIC and replaced it with a 3COM card I cannot collect
more traces at the moment.

What is the latest version of the driver, is it the one from patchE ?

You have the latest version of the driver.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207134342.22836H@node90.ott.qnx.com> …
I have tested the driver here with the same chipset and it works fine.
I can ping with any size packet without any problems. Can you please
post the ‘netinfo’ output after this happens?

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Hello,

We got 2 new system that have an onboard NIC 82558 and we are using the
Net.ether82557 version 4.25G driver with QNX 4.25D and TCPIP 4.25C.

The network card seams to works fine except when we try to transmit
large
packet sizes. We can easly reproduce this by using the “ping -s2000
hostname” command. For small packets sizes we can ping the unit no
problem,
for large packet sizes of 2000+ there is no response. Same thing, when
we
telnet to the unit, it works fine, but when we try to view a console or
a
file with too much information the telnet stop responding.

This problem happens on both units and running netinfo do not display
errors
or OWC.

We disabled the onbard NIC and installed a 3COM network card and that
solved
the problem, so the network is fine, but we will be receiving a lot of
these
units and will like to be able to use the onboard NIC.

Any idea? have someone run into something like this?

I have included the output of “show_pci -v” and “netinfo -l”.

\

5

Ok! I think I found the origin of the problem.

I can reproduce the problem in-house when we connect the unit to to a 10Mbps
switch capable of both half and full duplex (3COM SuperStack II switch
3C16460).The unit onboard lan has a 82558B NIC with auto-sensing and it
automatic sets it self to use FULL-DUPLEX. I can then only send small
packets.
If I connect it to a half-duplex only hub there is no problem, it works fine
on a 100Mbps hub (3COM SuperStack II HUB 100TX 3C250C) and on a 10Mbps hub
(CentreCom 3024TR).

I guess what I need is a “-H” option, the oposite of the “-F” option on the
Net.ether82557 driver to force the card to set it self to half-duplex.

So maybe the driver or the onbard NIC is having a problem in full-duplex
mode.
Monday, I will install Windows on one of the units to see if the same
happens, this will clarify which one is having a problem.

In any case I have included the netinfo output you requested.
Please let me know if you need more trace, or if you have an updated driver
that you want me to try.

“Hugh Brown” <hsbrown@qnx.com> wrote in message
news:Voyager.020207155144.14271A@node90.ott.qnx.com…

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Well the netinfo posted is the one collected after some ping commands
jammed. The unit still remains functional and will continue to respond
to
further commands (only if using small packets).


The netinfo that you posted is the ‘netinfo -l’ output. I just want the
‘netinfo’ output.

Tomorrow we will receive another unit, I will then be able to perform
further tests in-house, these traces were collected from a client site
and
since we disabled the NIC and replaced it with a 3COM card I cannot
collect
more traces at the moment.

What is the latest version of the driver, is it the one from patchE ?


You have the latest version of the driver.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207134342.22836H@node90.ott.qnx.com> …
I have tested the driver here with the same chipset and it works fine.
I can ping with any size packet without any problems. Can you please
post the ‘netinfo’ output after this happens?

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Hello,

We got 2 new system that have an onboard NIC 82558 and we are using
the
Net.ether82557 version 4.25G driver with QNX 4.25D and TCPIP 4.25C.

The network card seams to works fine except when we try to transmit
large
packet sizes. We can easly reproduce this by using the “ping -s2000
hostname” command. For small packets sizes we can ping the unit no
problem,
for large packet sizes of 2000+ there is no response. Same thing,
when
we
telnet to the unit, it works fine, but when we try to view a console
or
a
file with too much information the telnet stop responding.

This problem happens on both units and running netinfo do not
display
errors
or OWC.

We disabled the onbard NIC and installed a 3COM network card and
that
solved
the problem, so the network is fine, but we will be receiving a lot
of
these
units and will like to be able to use the onboard NIC.

Any idea? have someone run into something like this?

I have included the output of “show_pci -v” and “netinfo -l”.



\

begin 666 netinfo.txt
M1&%T92 @(" @3F5T(“A.:61\4W1A='5S2 @0V]D92 @1&5S8W)I<'1I;VX-
M"C P.C R.C W(#$@(" P,#DP1#8@,# P,T0Q("@@-3@I($Y%5" H(&YM2!N
M971M87 @;7-G.B!P:'ES:6-A;”!N:60-“C P.C R.C X(#$@(” @(" @(" @
M(" @(" @("@R-#$I(#@P,#,@"!R>“D@8W5R<F5N=”!S97$C('5N:VYO=VXM
M(# @=FED#0HP,#HP,CHP." Q(" @4W1A='5S(# @(" @(" H(#0T2!.150@
M*"!R>“D@<&]S<VEB;&4@9’5P;&EC871E('9I9”!S97%U96YC92!N=6UB97(-
M"C P.C R.C X(#$@("!3=&%T=7,@,C(@(" @("@@,C,I($Y%5" @(" @("!F
M86EL960@<’)O8R!?=F-?871T86-H(&US9PT*,# Z,#(Z,#@@," @(" @(" @
M(" @(" @(" @" T.2D@3D54(“AR=G,I('9I9”!W87,@>F5R;PT,# Z,#(Z
M,#@@," @(" @(" @(" @(" @(" @" T."D@3D54(“AI=G,I('9I9”!W87,@
M>F5R;PT,# Z,#(Z,#@@,2 @(# P-# P-2 U0SDV-$4@" S-RD@3D54("@@
M<G@I(‘5N<F5C;V=N:7IE9"!R87<@<&%C:V5T(’!R;W1O8V]L#0HP,#HP,CHQ
M,B Q(" @4W1A='5S(#(R(" @(" H(#(S2!.150@(" @(" @9F%I;&5D(’!R
M;V,@7W9C7V%T=&%C:"!M<V<-“C P.C R.C$R(# @(” @(" @(" @(" @(" @
M("@@-#DI($Y%5" H<G9S2!V:60@=V%S('IE<F-“C P.C R.C$R(# @(” @
M(" @(" @(" @(" @("@@-#@I($Y%5" H:79S2!V:60@=V%S(‘IE<F-“C P
M.C R.C$X(#$@(”!3=&%T=7,@,C(@(" @("@@,C,I($Y%5" @(" @("!F86EL
M960@<’)O8R!?=F-?871T86-H(&US9PT*,# Z,#(Z,3@@," @(" @(" @(" @
M(" @(" @" T.2D@3D54(“AR=G,I('9I9”!W87,@>F5R;PT,# Z,#(Z,3@@
M," @(" @(" @(" @(" @(" @" T."D@3D54(“AI=G,I('9I9”!W87,@>F5R
M;PT,# Z,#(Z,C0@,2 @(%-T871U<R R,B @(" @" R,RD@3D54(" @(" @
M(&9A:6QE9"!P<F]C(%]V8U]A='1A8V@@;7-G#0HP,#HP,CHR-" P(" @(" @
M(" @(" @(" @(" H(#0Y2!.150@’)V<RD@=FED(’=A<R!Z97)O#0HP,#HP
M,CHR-" P(" @(" @(" @(" @(" @(" H(#0X2!.150@&EV<RD@=FED(’=A
M<R!Z97)O#0HP,#HP,CHS," Q(" @4W1A='5S(#(R(" @(" H(#(S2!.150@
M(" @(" @9F%I;&5D(’!R;V,@7W9C7V%T=&%C:"!M<V<-“C P.C R.C,P(# @
M(” @(" @(" @(" @(" @("@@-#DI($Y%5" H<G9S2!V:60@=V%S('IE<F-
M"C P.C R.C,P(# @(" @(" @(" @(" @(" @("@@-#@I($Y%5" H:79S2!V
M:60@=V%S(‘IE<F-“C P.C R.C,V(#$@(” @(" @(" @(" @(" @("@R-#$I
M(#@P,#,@"!R>“D@8W5R<F5N=”!S97$C('5N:VYO=VXM(# @=FED#0HP,#HP
M,CHS-B Q(" @4W1A='5S(#,@(" @(" H(#(U2!.150@(" @(" @9F%I;&5D
M(’!R;V,@7W9C7V1E=&%C:"!M<V<-“C P.C R.C,V(#$@(” @(" @(" @(" @
M(" @("@R-#$I(#@P,#,@"!R>“D@8W5R<F5N=”!S97$C('5N:VYO=VXM(# @
M=FED#0HP,#HP,CHS-B Q(" @4W1A='5S(#,@(" @(" H(#(U2!.150@(" @
M(" @9F%I;&5D(’!R;V,@7W9C7V1E=&%C:"!M<V<-“C P.C R.C,V(#$@(” @
M(" @(" @(" @(" @("@R-#$I(#@P,#,@"!R>“D@8W5R<F5N=”!S97$C('5N
M:VYO=VXM(# @=FED#0HP,#HP,CHS-B Q(" @4W1A='5S(#,@(" @(" H(#(U
M2!.150@(" @(" @9F%I;&5D(’!R;V,@7W9C7V1E=&%C:"!M<V<-“C P.C R
M.C,V(#$@(” @(" @(" @(" @(" @("@R-#$I(#@P,#,@"!R>“D@8W5R<F5N
M=”!S97$C('5N:VYO=VXM(# @=FED#0HP,#HP,CHS-B Q(" @4W1A='5S(#,@
M(" @(" H(#(U2!.150@(" @(" @9F%I;&5D(’!R;V,@7W9C7V1E=&%C:"!M
M<V<-“C P.C R.C,V(#$@(”!3=&%T=7,@,C(@(" @("@@,C,I($Y%5" @(" @
M("!F86EL960@<’)O8R!?=F-?871T86-H(&US9PT*,# Z,#(Z,S8@," @(" @
M(" @(" @(" @(" @" T.2D@3D54(“AR=G,I('9I9”!W87,@>F5R;PT,# Z
M,#(Z,S8@," @(" @(" @(" @(" @(" @" T."D@3D54(“AI=G,I('9I9”!W
M87,@>F5R;PT,# Z,#(Z-#(@,2 @(%-T871U<R R,B @(" @" R,RD@3D54
M(" @(" @(&9A:6QE9"!P<F]C(%]V8U]A='1A8V@@;7-G#0HP,#HP,CHT,B P
M(" @(" @(" @(" @(" @(" H(#0Y2!.150@’)V<RD@=FED(’=A<R!Z97)O
M#0HP,#HP,CHT,B P(" @(" @(" @(" @(" @(" H(#0X2!.150@&EV<RD@
M=FED(’=A<R!Z97)O#0HP,#HP,CHT-B Q(" @(" @(" @(" @(" @(" H,C0Q
M2 X,# S("@@<G@I(&-U<G)E;G0@<V5Q(R!U;FMN;W=N+2 P(‘9I9 T*,# Z
M,#(Z-#8@,2 @(%-T871U<R S(" @(" @" R-2D@3D54(" @(" @(&9A:6QE
M9"!P<F]C(%]V8U]D971A8V@@;7-G#0HP,#HP,CHT." Q(" @4W1A='5S(#(R
M(" @(" H(#(S2!.150@(" @(" @9F%I;&5D(’!R;V,@7W9C7V%T=&%C:"!M
M<V<-“C P.C R.C0X(# @(” @(" @(" @(" @(" @("@@-#DI($Y%5" H<G9S
M2!V:60@=V%S('IE<F-“C P.C R.C0X(# @(” @(" @(" @(" @(" @("@@
M-#@I($Y%5" H:79S2!V:60@=V%S(‘IE<F-“C P.C R.C4T(#$@(”!3=&%T
M=7,@,C(@(" @("@@,C,I($Y%5" @(" @("!F86EL960@<’)O8R!?=F-?871T
M86-H(&US9PT*,# Z,#(Z-30@," @(" @(" @(" @(" @(" @" T.2D@3D54
M(“AR=G,I('9I9”!W87,@>F5R;PT,# Z,#(Z-30@," @(" @(" @(" @(" @
M(" @" T."D@3D54(“AI=G,I('9I9”!W87,@>F5R;PT,# Z,#(Z-38@,2 @
M(" @(" @(" @(" @(" @#(T,2D@.# P,R H(’)X2!C=7)R96YT(’-E<2,@
M=6YK;F]W;BT@,"!V:60-“C P.C R.C4V(#$@(”!3=&%T=7,@,R @(" @("@@
M,C4I($Y%5" @(" @("!F86EL960@<’)O8R!?=F-?9&5T86-H(&US9PT*,# Z
M,#(Z-38@,2 @(" @(" @(" @(" @(" @#(T,2D@.# P,R H(’)X2!C=7)R
M96YT(’-E<2,@=6YK;F]W;BT@,"!V:60-“C P.C R.C4V(#$@(”!3=&%T=7,@
M,R @(" @("@@,C4I($Y%5" @(" @("!F86EL960@<’)O8R!?=F-?9&5T86-H
M(&US9PT*,# Z,#,Z,# @,2 @(%-T871U<R R,B @(" @" R,RD@3D54(" @
M(" @(&9A:6QE9"!P<F]C(%]V8U]A='1A8V@@;7-G#0HP,#HP,SHP," P(" @
M(" @(" @(" @(" @(" H(#0Y2!.150@’)V<RD@=FED(’=A<R!Z97)O#0HP
M,#HP,SHP," P(" @(" @(" @(" @(" @(" H(#0X2!.150@&EV<RD@=FED
M(’=A<R!Z97)O#0HP,#HP,SHP-B Q(" @(" @(" @(" @(" @(" H,C0Q2 X
M,# S("@@<G@I(&-U<G)E;G0@<V5Q(R!U;FMN;W=N+2 P(‘9I9 T*,# Z,#,Z
M,#8@,2 @(%-T871U<R S(" @(" @" R-2D@3D54(" @(" @(&9A:6QE9"!P
M<F]C(%]V8U]D971A8V@@;7-G#0HP,#HP,SHP-B Q(" @(" @(" @(" @(" @
M(" H,C0Q2 X,# S("@@<G@I(&-U<G)E;G0@<V5Q(R!U;FMN;W=N+2 P(‘9I
M9 T*,# Z,#,Z,#8@,2 @(%-T871U<R S(" @(" @" R-2D@3D54(" @(" @
M(&9A:6QE9"!P<F]C(%]V8U]D971A8V@@;7-G#0HP,#HP,SHP-B Q(" @4W1A
M='5S(#(R(" @(" H(#(S2!.150@(" @(" @9F%I;&5D(’!R;V,@7W9C7V%T
M=&%C:"!M<V<-“C P.C S.C V(# @(” @(" @(" @(" @(" @("@@-#DI($Y%
M5" H<G9S2!V:60@=V%S('IE<F-“C P.C S.C V(# @(” @(" @(" @(" @
M(" @("@@-#@I($Y%5" H:79S2!V:60@=V%S(‘IE<F-“C P.C S.C$R(#$@
M(”!3=&%T=7,@,C(@(" @("@@,C,I($Y%5" @(" @("!F86EL960@<’)O8R!?
M=F-?871T86-H(&US9PT*,# Z,#,Z,3(@," @(" @(" @(" @(" @(" @" T
M.2D@3D54(“AR=G,I('9I9”!W87,@>F5R;PT,# Z,#,Z,3(@," @(" @(" @
M(" @(" @(" @" T."D@3D54(“AI=G,I('9I9”!W87,@>F5R;PT,# Z,#,Z
M,38@,2 @(" @(" @(" @(" @(" @#(T,2D@.# P,R H(’)X2!C=7)R96YT
M(’-E<2,@=6YK;F]W;BT@,"!V:60-“C P.C S.C$V(#$@(”!3=&%T=7,@,R @
M(" @("@@,C4I($Y%5" @(" @("!F86EL960@<’)O8R!?=F-?9&5T86-H(&US
#9PT*
`
end

6

I’ll take a look at the full/half-duplex detection and see if there is a
problem and get back to you.

Previously, Cesar Hernandez wrote in qdn.public.qnx4:

Ok! I think I found the origin of the problem.

I can reproduce the problem in-house when we connect the unit to to a 10Mbps
switch capable of both half and full duplex (3COM SuperStack II switch
3C16460).The unit onboard lan has a 82558B NIC with auto-sensing and it
automatic sets it self to use FULL-DUPLEX. I can then only send small
packets.
If I connect it to a half-duplex only hub there is no problem, it works fine
on a 100Mbps hub (3COM SuperStack II HUB 100TX 3C250C) and on a 10Mbps hub
(CentreCom 3024TR).

I guess what I need is a “-H” option, the oposite of the “-F” option on the
Net.ether82557 driver to force the card to set it self to half-duplex.

So maybe the driver or the onbard NIC is having a problem in full-duplex
mode.
Monday, I will install Windows on one of the units to see if the same
happens, this will clarify which one is having a problem.

In any case I have included the netinfo output you requested.
Please let me know if you need more trace, or if you have an updated driver
that you want me to try.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207155144.14271A@node90.ott.qnx.com> …
Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Well the netinfo posted is the one collected after some ping commands
jammed. The unit still remains functional and will continue to respond
to
further commands (only if using small packets).


The netinfo that you posted is the ‘netinfo -l’ output. I just want the
‘netinfo’ output.

Tomorrow we will receive another unit, I will then be able to perform
further tests in-house, these traces were collected from a client site
and
since we disabled the NIC and replaced it with a 3COM card I cannot
collect
more traces at the moment.

What is the latest version of the driver, is it the one from patchE ?


You have the latest version of the driver.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207134342.22836H@node90.ott.qnx.com> …
I have tested the driver here with the same chipset and it works fine.
I can ping with any size packet without any problems. Can you please
post the ‘netinfo’ output after this happens?

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Hello,

We got 2 new system that have an onboard NIC 82558 and we are using
the
Net.ether82557 version 4.25G driver with QNX 4.25D and TCPIP 4.25C.

The network card seams to works fine except when we try to transmit
large
packet sizes. We can easly reproduce this by using the “ping -s2000
hostname” command. For small packets sizes we can ping the unit no
problem,
for large packet sizes of 2000+ there is no response. Same thing,
when
we
telnet to the unit, it works fine, but when we try to view a console
or
a
file with too much information the telnet stop responding.

This problem happens on both units and running netinfo do not
display
errors
or OWC.

We disabled the onbard NIC and installed a 3COM network card and
that
solved
the problem, so the network is fine, but we will be receiving a lot
of
these
units and will like to be able to use the onboard NIC.

Any idea? have someone run into something like this?

I have included the output of “show_pci -v” and “netinfo -l”.








begin 666 netinfo.txt
M1&%T92 @(" @3F5T(“A.:61\4W1A='5S2 @0V]D92 @1&5S8W)I<'1I;VX-
M"C P.C R.C W(#$@(" P,#DP1#8@,# P,T0Q("@@-3@I($Y%5" H(&YM2!N
M971M87 @;7-G.B!P:'ES:6-A;”!N:60-“C P.C R.C X(#$@(” @(" @(" @
M(" @(" @("@R-#$I(#@P,#,@"!R>“D@8W5R<F5N=”!S97$C('5N:VYO=VXM
M(# @=FED#0HP,#HP,CHP." Q(" @4W1A='5S(# @(" @(" H(#0T2!.150@
M*"!R>“D@<&]S<VEB;&4@9’5P;&EC871E('9I9”!S97%U96YC92!N=6UB97(-
M"C P.C R.C X(#$@("!3=&%T=7,@,C(@(" @("@@,C,I($Y%5" @(" @("!F
M86EL960@<’)O8R!?=F-?871T86-H(&US9PT*,# Z,#(Z,#@@," @(" @(" @
M(" @(" @(" @" T.2D@3D54(“AR=G,I('9I9”!W87,@>F5R;PT,# Z,#(Z
M,#@@," @(" @(" @(" @(" @(" @" T."D@3D54(“AI=G,I('9I9”!W87,@
M>F5R;PT,# Z,#(Z,#@@,2 @(# P-# P-2 U0SDV-$4@" S-RD@3D54("@@
M<G@I(‘5N<F5C;V=N:7IE9"!R87<@<&%C:V5T(’!R;W1O8V]L#0HP,#HP,CHQ
M,B Q(" @4W1A='5S(#(R(" @(" H(#(S2!.150@(" @(" @9F%I;&5D(’!R
M;V,@7W9C7V%T=&%C:"!M<V<-“C P.C R.C$R(# @(” @(" @(" @(" @(" @
M("@@-#DI($Y%5" H<G9S2!V:60@=V%S('IE<F-“C P.C R.C$R(# @(” @
M(" @(" @(" @(" @("@@-#@I($Y%5" H:79S2!V:60@=V%S(‘IE<F-“C P
M.C R.C$X(#$@(”!3=&%T=7,@,C(@(" @("@@,C,I($Y%5" @(" @("!F86EL
M960@<’)O8R!?=F-?871T86-H(&US9PT*,# Z,#(Z,3@@," @(" @(" @(" @
M(" @(" @" T.2D@3D54(“AR=G,I('9I9”!W87,@>F5R;PT,# Z,#(Z,3@@
M," @(" @(" @(" @(" @(" @" T."D@3D54(“AI=G,I('9I9”!W87,@>F5R
M;PT,# Z,#(Z,C0@,2 @(%-T871U<R R,B @(" @" R,RD@3D54(" @(" @
M(&9A:6QE9"!P<F]C(%]V8U]A='1A8V@@;7-G#0HP,#HP,CHR-" P(" @(" @
M(" @(" @(" @(" H(#0Y2!.150@’)V<RD@=FED(’=A<R!Z97)O#0HP,#HP
M,CHR-" P(" @(" @(" @(" @(" @(" H(#0X2!.150@&EV<RD@=FED(’=A
M<R!Z97)O#0HP,#HP,CHS," Q(" @4W1A='5S(#(R(" @(" H(#(S2!.150@
M(" @(" @9F%I;&5D(’!R;V,@7W9C7V%T=&%C:"!M<V<-“C P.C R.C,P(# @
M(” @(" @(" @(" @(" @("@@-#DI($Y%5" H<G9S2!V:60@=V%S('IE<F-
M"C P.C R.C,P(# @(" @(" @(" @(" @(" @("@@-#@I($Y%5" H:79S2!V
M:60@=V%S(‘IE<F-“C P.C R.C,V(#$@(” @(" @(" @(" @(" @("@R-#$I
M(#@P,#,@"!R>“D@8W5R<F5N=”!S97$C('5N:VYO=VXM(# @=FED#0HP,#HP
M,CHS-B Q(" @4W1A='5S(#,@(" @(" H(#(U2!.150@(" @(" @9F%I;&5D
M(’!R;V,@7W9C7V1E=&%C:"!M<V<-“C P.C R.C,V(#$@(” @(" @(" @(" @
M(" @("@R-#$I(#@P,#,@"!R>“D@8W5R<F5N=”!S97$C('5N:VYO=VXM(# @
M=FED#0HP,#HP,CHS-B Q(" @4W1A='5S(#,@(" @(" H(#(U2!.150@(" @
M(" @9F%I;&5D(’!R;V,@7W9C7V1E=&%C:"!M<V<-“C P.C R.C,V(#$@(” @
M(" @(" @(" @(" @("@R-#$I(#@P,#,@"!R>“D@8W5R<F5N=”!S97$C('5N
M:VYO=VXM(# @=FED#0HP,#HP,CHS-B Q(" @4W1A='5S(#,@(" @(" H(#(U
M2!.150@(" @(" @9F%I;&5D(’!R;V,@7W9C7V1E=&%C:"!M<V<-“C P.C R
M.C,V(#$@(” @(" @(" @(" @(" @("@R-#$I(#@P,#,@"!R>“D@8W5R<F5N
M=”!S97$C('5N:VYO=VXM(# @=FED#0HP,#HP,CHS-B Q(" @4W1A='5S(#,@
M(" @(" H(#(U2!.150@(" @(" @9F%I;&5D(’!R;V,@7W9C7V1E=&%C:"!M
M<V<-“C P.C R.C,V(#$@(”!3=&%T=7,@,C(@(" @("@@,C,I($Y%5" @(" @
M("!F86EL960@<’)O8R!?=F-?871T86-H(&US9PT*,# Z,#(Z,S8@," @(" @
M(" @(" @(" @(" @" T.2D@3D54(“AR=G,I('9I9”!W87,@>F5R;PT,# Z
M,#(Z,S8@," @(" @(" @(" @(" @(" @" T."D@3D54(“AI=G,I('9I9”!W
M87,@>F5R;PT,# Z,#(Z-#(@,2 @(%-T871U<R R,B @(" @" R,RD@3D54
M(" @(" @(&9A:6QE9"!P<F]C(%]V8U]A='1A8V@@;7-G#0HP,#HP,CHT,B P
M(" @(" @(" @(" @(" @(" H(#0Y2!.150@’)V<RD@=FED(’=A<R!Z97)O
M#0HP,#HP,CHT,B P(" @(" @(" @(" @(" @(" H(#0X2!.150@&EV<RD@
M=FED(’=A<R!Z97)O#0HP,#HP,CHT-B Q(" @(" @(" @(" @(" @(" H,C0Q
M2 X,# S("@@<G@I(&-U<G)E;G0@<V5Q(R!U;FMN;W=N+2 P(‘9I9 T*,# Z
M,#(Z-#8@,2 @(%-T871U<R S(" @(" @" R-2D@3D54(" @(" @(&9A:6QE
M9"!P<F]C(%]V8U]D971A8V@@;7-G#0HP,#HP,CHT." Q(" @4W1A='5S(#(R
M(" @(" H(#(S2!.150@(" @(" @9F%I;&5D(’!R;V,@7W9C7V%T=&%C:"!M
M<V<-“C P.C R.C0X(# @(” @(" @(" @(" @(" @("@@-#DI($Y%5" H<G9S
M2!V:60@=V%S('IE<F-“C P.C R.C0X(# @(” @(" @(" @(" @(" @("@@
M-#@I($Y%5" H:79S2!V:60@=V%S(‘IE<F-“C P.C R.C4T(#$@(”!3=&%T
M=7,@,C(@(" @("@@,C,I($Y%5" @(" @("!F86EL960@<’)O8R!?=F-?871T
M86-H(&US9PT*,# Z,#(Z-30@," @(" @(" @(" @(" @(" @" T.2D@3D54
M(“AR=G,I('9I9”!W87,@>F5R;PT,# Z,#(Z-30@," @(" @(" @(" @(" @
M(" @" T."D@3D54(“AI=G,I('9I9”!W87,@>F5R;PT,# Z,#(Z-38@,2 @
M(" @(" @(" @(" @(" @#(T,2D@.# P,R H(’)X2!C=7)R96YT(’-E<2,@
M=6YK;F]W;BT@,"!V:60-“C P.C R.C4V(#$@(”!3=&%T=7,@,R @(" @("@@
M,C4I($Y%5" @(" @("!F86EL960@<’)O8R!?=F-?9&5T86-H(&US9PT*,# Z
M,#(Z-38@,2 @(" @(" @(" @(" @(" @#(T,2D@.# P,R H(’)X2!C=7)R
M96YT(’-E<2,@=6YK;F]W;BT@,"!V:60-“C P.C R.C4V(#$@(”!3=&%T=7,@
M,R @(" @("@@,C4I($Y%5" @(" @("!F86EL960@<’)O8R!?=F-?9&5T86-H
M(&US9PT*,# Z,#,Z,# @,2 @(%-T871U<R R,B @(" @" R,RD@3D54(" @
M(" @(&9A:6QE9"!P<F]C(%]V8U]A='1A8V@@;7-G#0HP,#HP,SHP," P(" @
M(" @(" @(" @(" @(" H(#0Y2!.150@’)V<RD@=FED(’=A<R!Z97)O#0HP
M,#HP,SHP," P(" @(" @(" @(" @(" @(" H(#0X2!.150@&EV<RD@=FED
M(’=A<R!Z97)O#0HP,#HP,SHP-B Q(" @(" @(" @(" @(" @(" H,C0Q2 X
M,# S("@@<G@I(&-U<G)E;G0@<V5Q(R!U;FMN;W=N+2 P(‘9I9 T*,# Z,#,Z
M,#8@,2 @(%-T871U<R S(" @(" @" R-2D@3D54(" @(" @(&9A:6QE9"!P
M<F]C(%]V8U]D971A8V@@;7-G#0HP,#HP,SHP-B Q(" @(" @(" @(" @(" @
M(" H,C0Q2 X,# S("@@<G@I(&-U<G)E;G0@<V5Q(R!U;FMN;W=N+2 P(‘9I
M9 T*,# Z,#,Z,#8@,2 @(%-T871U<R S(" @(" @" R-2D@3D54(" @(" @
M(&9A:6QE9"!P<F]C(%]V8U]D971A8V@@;7-G#0HP,#HP,SHP-B Q(" @4W1A
M='5S(#(R(" @(" H(#(S2!.150@(" @(" @9F%I;&5D(’!R;V,@7W9C7V%T
M=&%C:"!M<V<-“C P.C S.C V(# @(” @(" @(" @(" @(" @("@@-#DI($Y%
M5" H<G9S2!V:60@=V%S('IE<F-“C P.C S.C V(# @(” @(" @(" @(" @
M(" @("@@-#@I($Y%5" H:79S2!V:60@=V%S(‘IE<F-“C P.C S.C$R(#$@
M(”!3=&%T=7,@,C(@(" @("@@,C,I($Y%5" @(" @("!F86EL960@<’)O8R!?
M=F-?871T86-H(&US9PT*,# Z,#,Z,3(@," @(" @(" @(" @(" @(" @" T
M.2D@3D54(“AR=G,I('9I9”!W87,@>F5R;PT,# Z,#,Z,3(@," @(" @(" @
M(" @(" @(" @" T."D@3D54(“AI=G,I('9I9”!W87,@>F5R;PT,# Z,#,Z
M,38@,2 @(" @(" @(" @(" @(" @#(T,2D@.# P,R H(’)X2!C=7)R96YT
M(’-E<2,@=6YK;F]W;BT@,"!V:60-“C P.C S.C$V(#$@(”!3=&%T=7,@,R @
M(" @("@@,C4I($Y%5" @(" @("!F86EL960@<’)O8R!?=F-?9&5T86-H(&US
#9PT*
`
end

7

Previously, Hugh Brown wrote in qdn.public.qnx4:

I’ll take a look at the full/half-duplex detection and see if there is a
problem and get back to you.

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Ok! I think I found the origin of the problem.

I can reproduce the problem in-house when we connect the unit to to a 10Mbps
switch capable of both half and full duplex (3COM SuperStack II switch
3C16460).The unit onboard lan has a 82558B NIC with auto-sensing and it
automatic sets it self to use FULL-DUPLEX. I can then only send small
packets.
If I connect it to a half-duplex only hub there is no problem, it works fine
on a 100Mbps hub (3COM SuperStack II HUB 100TX 3C250C) and on a 10Mbps hub
(CentreCom 3024TR).

I guess what I need is a “-H” option, the oposite of the “-F” option on the
Net.ether82557 driver to force the card to set it self to half-duplex.

If you don’t specify “-F” but you do specify a “-s”, this will set the chip
to half-duplex. What happens if you don’t specify any command line options
and let the chip autonegotiate the link speed/duplex?

So maybe the driver or the onbard NIC is having a problem in full-duplex
mode.
Monday, I will install Windows on one of the units to see if the same
happens, this will clarify which one is having a problem.

In any case I have included the netinfo output you requested.
Please let me know if you need more trace, or if you have an updated driver
that you want me to try.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207155144.14271A@node90.ott.qnx.com> …
Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Well the netinfo posted is the one collected after some ping commands
jammed. The unit still remains functional and will continue to respond
to
further commands (only if using small packets).


The netinfo that you posted is the ‘netinfo -l’ output. I just want the
‘netinfo’ output.

Tomorrow we will receive another unit, I will then be able to perform
further tests in-house, these traces were collected from a client site
and
since we disabled the NIC and replaced it with a 3COM card I cannot
collect
more traces at the moment.

What is the latest version of the driver, is it the one from patchE ?


You have the latest version of the driver.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207134342.22836H@node90.ott.qnx.com> …
I have tested the driver here with the same chipset and it works fine.
I can ping with any size packet without any problems. Can you please
post the ‘netinfo’ output after this happens?

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Hello,

We got 2 new system that have an onboard NIC 82558 and we are using
the
Net.ether82557 version 4.25G driver with QNX 4.25D and TCPIP 4.25C.

The network card seams to works fine except when we try to transmit
large
packet sizes. We can easly reproduce this by using the “ping -s2000
hostname” command. For small packets sizes we can ping the unit no
problem,
for large packet sizes of 2000+ there is no response. Same thing,
when
we
telnet to the unit, it works fine, but when we try to view a console
or
a
file with too much information the telnet stop responding.

This problem happens on both units and running netinfo do not
display
errors
or OWC.

We disabled the onbard NIC and installed a 3COM network card and
that
solved
the problem, so the network is fine, but we will be receiving a lot
of
these
units and will like to be able to use the onboard NIC.

Any idea? have someone run into something like this?

I have included the output of “show_pci -v” and “netinfo -l”.

\

8

Initially we did not use the “-s” and “-F” options, but even playing with
all the combinations of the “-s” and “-F” options did not change anything.
So the NIC seams to definitely have a problem in Full-Duplex mode since it
works when we connect it to a half-duplex which do not support
auto-negotiation. It is possible that on the auto-negotiating switch, the
switch sets itself to full-duplex event if the board sets itself to
half-duplex, but I have no way of knowing (no led and no utilities to
query).
PS: The “ifconfig en1” command always shows SIMPLEX, do this refer to
half-duplex?

“Hugh Brown” <hsbrown@qnx.com> wrote in message
news:Voyager.020211143813.4658A@node90.ott.qnx.com…

Previously, Hugh Brown wrote in qdn.public.qnx4:
I’ll take a look at the full/half-duplex detection and see if there is a
problem and get back to you.

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Ok! I think I found the origin of the problem.

I can reproduce the problem in-house when we connect the unit to to a
10Mbps
switch capable of both half and full duplex (3COM SuperStack II switch
3C16460).The unit onboard lan has a 82558B NIC with auto-sensing and
it
automatic sets it self to use FULL-DUPLEX. I can then only send small
packets.
If I connect it to a half-duplex only hub there is no problem, it
works fine
on a 100Mbps hub (3COM SuperStack II HUB 100TX 3C250C) and on a 10Mbps
hub
(CentreCom 3024TR).

I guess what I need is a “-H” option, the oposite of the “-F” option
on the
Net.ether82557 driver to force the card to set it self to half-duplex.


If you don’t specify “-F” but you do specify a “-s”, this will set the
chip
to half-duplex. What happens if you don’t specify any command line options
and let the chip autonegotiate the link speed/duplex?

So maybe the driver or the onbard NIC is having a problem in
full-duplex
mode.
Monday, I will install Windows on one of the units to see if the same
happens, this will clarify which one is having a problem.

In any case I have included the netinfo output you requested.
Please let me know if you need more trace, or if you have an updated
driver
that you want me to try.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207155144.14271A@node90.ott.qnx.com> …
Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Well the netinfo posted is the one collected after some ping
commands
jammed. The unit still remains functional and will continue to
respond
to
further commands (only if using small packets).


The netinfo that you posted is the ‘netinfo -l’ output. I just want
the
‘netinfo’ output.

Tomorrow we will receive another unit, I will then be able to
perform
further tests in-house, these traces were collected from a client
site
and
since we disabled the NIC and replaced it with a 3COM card I
cannot
collect
more traces at the moment.

What is the latest version of the driver, is it the one from
patchE ?


You have the latest version of the driver.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207134342.22836H@node90.ott.qnx.com> …
I have tested the driver here with the same chipset and it works
fine.
I can ping with any size packet without any problems. Can you
please
post the ‘netinfo’ output after this happens?

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Hello,

We got 2 new system that have an onboard NIC 82558 and we are
using
the
Net.ether82557 version 4.25G driver with QNX 4.25D and TCPIP
4.25C.

The network card seams to works fine except when we try to
transmit
large
packet sizes. We can easly reproduce this by using the
“ping -s2000
hostname” command. For small packets sizes we can ping the
unit no
problem,
for large packet sizes of 2000+ there is no response. Same
thing,
when
we
telnet to the unit, it works fine, but when we try to view a
console
or
a
file with too much information the telnet stop responding.

This problem happens on both units and running netinfo do not
display
errors
or OWC.

We disabled the onbard NIC and installed a 3COM network card
and
that
solved
the problem, so the network is fine, but we will be receiving
a lot
of
these
units and will like to be able to use the onboard NIC.

Any idea? have someone run into something like this?

I have included the output of “show_pci -v” and “netinfo -l”.


\

9

I have tried the speedo driver here with a full-duplex and a half-duplex
hub as well as a full-duplex switch and have seen no problems with
autonegotiation. I have however, seen problems when trying to force the
speed and duplex. If you force the speed to 100 half-duplex, then slay
the driver and re-start it with 100 full-duplex, then the hub/switch
stays in half-duplex although the driver indicates that the link is at
100 full-duplex. The only way to overcome this is by re-booting the PC.
I will look into this some time.

Previously, Cesar Hernandez wrote in qdn.public.qnx4:

Initially we did not use the “-s” and “-F” options, but even playing with
all the combinations of the “-s” and “-F” options did not change anything.
So the NIC seams to definitely have a problem in Full-Duplex mode since it
works when we connect it to a half-duplex which do not support
auto-negotiation. It is possible that on the auto-negotiating switch, the
switch sets itself to full-duplex event if the board sets itself to
half-duplex, but I have no way of knowing (no led and no utilities to
query).
PS: The “ifconfig en1” command always shows SIMPLEX, do this refer to
half-duplex?

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020211143813.4658A@node90.ott.qnx.com> …
Previously, Hugh Brown wrote in qdn.public.qnx4:
I’ll take a look at the full/half-duplex detection and see if there is a
problem and get back to you.

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Ok! I think I found the origin of the problem.

I can reproduce the problem in-house when we connect the unit to to a
10Mbps
switch capable of both half and full duplex (3COM SuperStack II switch
3C16460).The unit onboard lan has a 82558B NIC with auto-sensing and
it
automatic sets it self to use FULL-DUPLEX. I can then only send small
packets.
If I connect it to a half-duplex only hub there is no problem, it
works fine
on a 100Mbps hub (3COM SuperStack II HUB 100TX 3C250C) and on a 10Mbps
hub
(CentreCom 3024TR).

I guess what I need is a “-H” option, the oposite of the “-F” option
on the
Net.ether82557 driver to force the card to set it self to half-duplex.


If you don’t specify “-F” but you do specify a “-s”, this will set the
chip
to half-duplex. What happens if you don’t specify any command line options
and let the chip autonegotiate the link speed/duplex?

So maybe the driver or the onbard NIC is having a problem in
full-duplex
mode.
Monday, I will install Windows on one of the units to see if the same
happens, this will clarify which one is having a problem.

In any case I have included the netinfo output you requested.
Please let me know if you need more trace, or if you have an updated
driver
that you want me to try.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207155144.14271A@node90.ott.qnx.com> …
Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Well the netinfo posted is the one collected after some ping
commands
jammed. The unit still remains functional and will continue to
respond
to
further commands (only if using small packets).


The netinfo that you posted is the ‘netinfo -l’ output. I just want
the
‘netinfo’ output.

Tomorrow we will receive another unit, I will then be able to
perform
further tests in-house, these traces were collected from a client
site
and
since we disabled the NIC and replaced it with a 3COM card I
cannot
collect
more traces at the moment.

What is the latest version of the driver, is it the one from
patchE ?


You have the latest version of the driver.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207134342.22836H@node90.ott.qnx.com> …
I have tested the driver here with the same chipset and it works
fine.
I can ping with any size packet without any problems. Can you
please
post the ‘netinfo’ output after this happens?

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Hello,

We got 2 new system that have an onboard NIC 82558 and we are
using
the
Net.ether82557 version 4.25G driver with QNX 4.25D and TCPIP
4.25C.

The network card seams to works fine except when we try to
transmit
large
packet sizes. We can easly reproduce this by using the
“ping -s2000
hostname” command. For small packets sizes we can ping the
unit no
problem,
for large packet sizes of 2000+ there is no response. Same
thing,
when
we
telnet to the unit, it works fine, but when we try to view a
console
or
a
file with too much information the telnet stop responding.

This problem happens on both units and running netinfo do not
display
errors
or OWC.

We disabled the onbard NIC and installed a 3COM network card
and
that
solved
the problem, so the network is fine, but we will be receiving
a lot
of
these
units and will like to be able to use the onboard NIC.

Any idea? have someone run into something like this?

I have included the output of “show_pci -v” and “netinfo -l”.





\

10

Did you try the “ping -s8000 hostname” command to see if you can send large
packets?
For us also every thing seams to work fine, on all
10/100/half-duplex/full-duplex combinations, except for the problem of not
beeing able to send or receive large packets on certain combinations.

“Hugh Brown” <hsbrown@qnx.com> wrote in message
news:Voyager.020212084228.13804A@node90.ott.qnx.com…

I have tried the speedo driver here with a full-duplex and a half-duplex
hub as well as a full-duplex switch and have seen no problems with
autonegotiation. I have however, seen problems when trying to force the
speed and duplex. If you force the speed to 100 half-duplex, then slay
the driver and re-start it with 100 full-duplex, then the hub/switch
stays in half-duplex although the driver indicates that the link is at
100 full-duplex. The only way to overcome this is by re-booting the PC.
I will look into this some time.

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Initially we did not use the “-s” and “-F” options, but even playing
with
all the combinations of the “-s” and “-F” options did not change
anything.
So the NIC seams to definitely have a problem in Full-Duplex mode since
it
works when we connect it to a half-duplex which do not support
auto-negotiation. It is possible that on the auto-negotiating switch,
the
switch sets itself to full-duplex event if the board sets itself to
half-duplex, but I have no way of knowing (no led and no utilities to
query).
PS: The “ifconfig en1” command always shows SIMPLEX, do this refer to
half-duplex?

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020211143813.4658A@node90.ott.qnx.com> …
Previously, Hugh Brown wrote in qdn.public.qnx4:
I’ll take a look at the full/half-duplex detection and see if there
is a
problem and get back to you.

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Ok! I think I found the origin of the problem.

I can reproduce the problem in-house when we connect the unit to
to a
10Mbps
switch capable of both half and full duplex (3COM SuperStack II
switch
3C16460).The unit onboard lan has a 82558B NIC with auto-sensing
and
it
automatic sets it self to use FULL-DUPLEX. I can then only send
small
packets.
If I connect it to a half-duplex only hub there is no problem, it
works fine
on a 100Mbps hub (3COM SuperStack II HUB 100TX 3C250C) and on a
10Mbps
hub
(CentreCom 3024TR).

I guess what I need is a “-H” option, the oposite of the “-F”
option
on the
Net.ether82557 driver to force the card to set it self to
half-duplex.


If you don’t specify “-F” but you do specify a “-s”, this will set the
chip
to half-duplex. What happens if you don’t specify any command line
options
and let the chip autonegotiate the link speed/duplex?

So maybe the driver or the onbard NIC is having a problem in
full-duplex
mode.
Monday, I will install Windows on one of the units to see if the
same
happens, this will clarify which one is having a problem.

In any case I have included the netinfo output you requested.
Please let me know if you need more trace, or if you have an
updated
driver
that you want me to try.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207155144.14271A@node90.ott.qnx.com> …
Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Well the netinfo posted is the one collected after some ping
commands
jammed. The unit still remains functional and will continue to
respond
to
further commands (only if using small packets).


The netinfo that you posted is the ‘netinfo -l’ output. I just
want
the
‘netinfo’ output.

Tomorrow we will receive another unit, I will then be able to
perform
further tests in-house, these traces were collected from a
client
site
and
since we disabled the NIC and replaced it with a 3COM card I
cannot
collect
more traces at the moment.

What is the latest version of the driver, is it the one from
patchE ?


You have the latest version of the driver.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020207134342.22836H@node90.ott.qnx.com> …
I have tested the driver here with the same chipset and it
works
fine.
I can ping with any size packet without any problems. Can
you
please
post the ‘netinfo’ output after this happens?

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Hello,

We got 2 new system that have an onboard NIC 82558 and we
are
using
the
Net.ether82557 version 4.25G driver with QNX 4.25D and
TCPIP
4.25C.

The network card seams to works fine except when we try to
transmit
large
packet sizes. We can easly reproduce this by using the
“ping -s2000
hostname” command. For small packets sizes we can ping the
unit no
problem,
for large packet sizes of 2000+ there is no response. Same
thing,
when
we
telnet to the unit, it works fine, but when we try to view
a
console
or
a
file with too much information the telnet stop responding.

This problem happens on both units and running netinfo do
not
display
errors
or OWC.

We disabled the onbard NIC and installed a 3COM network
card
and
that
solved
the problem, so the network is fine, but we will be
receiving
a lot
of
these
units and will like to be able to use the onboard NIC.

Any idea? have someone run into something like this?

I have included the output of “show_pci -v” and
“netinfo -l”.






\

11

Yes, I tried this on both full and half-duplex links and it worked fine.

Previously, Cesar Hernandez wrote in qdn.public.qnx4:

Did you try the “ping -s8000 hostname” command to see if you can send large
packets?
For us also every thing seams to work fine, on all
10/100/half-duplex/full-duplex combinations, except for the problem of not
beeing able to send or receive large packets on certain combinations.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020212084228.13804A@node90.ott.qnx.com> …
I have tried the speedo driver here with a full-duplex and a half-duplex
hub as well as a full-duplex switch and have seen no problems with
autonegotiation. I have however, seen problems when trying to force the
speed and duplex. If you force the speed to 100 half-duplex, then slay
the driver and re-start it with 100 full-duplex, then the hub/switch
stays in half-duplex although the driver indicates that the link is at
100 full-duplex. The only way to overcome this is by re-booting the PC.
I will look into this some time.

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Initially we did not use the “-s” and “-F” options, but even playing
with
all the combinations of the “-s” and “-F” options did not change
anything.
So the NIC seams to definitely have a problem in Full-Duplex mode since
it
works when we connect it to a half-duplex which do not support
auto-negotiation. It is possible that on the auto-negotiating switch,
the
switch sets itself to full-duplex event if the board sets itself to
half-duplex, but I have no way of knowing (no led and no utilities to
query).
PS: The “ifconfig en1” command always shows SIMPLEX, do this refer to
half-duplex?

12

Many thanks for your help Hugh,

I’ve tried it also on Window98SE, and the same problem show-up, so we have
escalated this problem to Crystal the board manufacturer. So definitely
there is something wrong with this onboard NIC.
But if you fix the force option problem you found, let us know maybe this
will fix our problem too!, it maybe that this NIC has a negociation problem.

“Hugh Brown” <hsbrown@qnx.com> wrote in message
news:Voyager.020212102513.13804B@node90.ott.qnx.com…

Yes, I tried this on both full and half-duplex links and it worked fine.

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Did you try the “ping -s8000 hostname” command to see if you can send
large
packets?
For us also every thing seams to work fine, on all
10/100/half-duplex/full-duplex combinations, except for the problem of
not
beeing able to send or receive large packets on certain combinations.

“Hugh Brown” <> hsbrown@qnx.com> > wrote in message
news:> Voyager.020212084228.13804A@node90.ott.qnx.com> …
I have tried the speedo driver here with a full-duplex and a
half-duplex
hub as well as a full-duplex switch and have seen no problems with
autonegotiation. I have however, seen problems when trying to force
the
speed and duplex. If you force the speed to 100 half-duplex, then slay
the driver and re-start it with 100 full-duplex, then the hub/switch
stays in half-duplex although the driver indicates that the link is at
100 full-duplex. The only way to overcome this is by re-booting the
PC.
I will look into this some time.

Previously, Cesar Hernandez wrote in qdn.public.qnx4:
Initially we did not use the “-s” and “-F” options, but even playing
with
all the combinations of the “-s” and “-F” options did not change
anything.
So the NIC seams to definitely have a problem in Full-Duplex mode
since
it
works when we connect it to a half-duplex which do not support
auto-negotiation. It is possible that on the auto-negotiating
switch,
the
switch sets itself to full-duplex event if the board sets itself to
half-duplex, but I have no way of knowing (no led and no utilities
to
query).
PS: The “ifconfig en1” command always shows SIMPLEX, do this refer
to
half-duplex?