|
Mario Charest
09/03/2010 5:22 PM
post66007
|
When I use option io-pkt-v4 -de1000 -pqnet -tcpip mclbytes=8192,pagesize=8192 qnet will not work. I can see the other
machines in /net, the other machines can see them machine. Any operation like pidin or ls will never return (even after
5 minutes)
Even weirder is that the program that is block on the other machine, being ls or pidin is not in a REPLY stated but in a
RUNNING stated ???
If I get rid of the mclbytwes options everything is fine. All this time tcpip works ok.
- Mario
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: qnet 6.5.0 and mclbytes
|
|
Andrew Boyd(deleted)
09/04/2010 7:36 AM
post66018
|
RE: qnet 6.5.0 and mclbytes
Try manually specifying the correct MTU to qnet
on the command line. I suspect it is trying to
guess it, and is getting it wrong.
--
aboyd
________________________________
From: Mario Charest [mailto:community-noreply@qnx.com]
Sent: Fri 9/3/2010 2:22 PM
To: general-networking
Subject: qnet 6.5.0 and mclbytes
When I use option io-pkt-v4 -de1000 -pqnet -tcpip mclbytes=8192,pagesize=8192 qnet will not work. I can see the other
machines in /net, the other machines can see them machine. Any operation like pidin or ls will never return (even after
5 minutes)
Even weirder is that the program that is block on the other machine, being ls or pidin is not in a REPLY stated but in a
RUNNING stated ???
If I get rid of the mclbytwes options everything is fine. All this time tcpip works ok.
- Mario
_______________________________________________
General
http://community.qnx.com/sf/go/post66007
|
|
|
|
|
|
Mario Charest
|
RE: qnet 6.5.0 and mclbytes
|
|
Mario Charest
09/07/2010 12:06 PM
post66149
|
RE: qnet 6.5.0 and mclbytes
I already tried that, (mtu_en=1500) and that didn`t help. Further more /proc/qnetstat shows mtu to be 1496.
What I do not understand is that this problem showed up with a new computer model we are evaluating, but the image we
are using is the same as with our other model. Maybe I'm looking at bad hardware. Will keep you posted.
Thank you.
-----Message d'origine-----
De : Andrew Boyd [mailto:community-noreply@qnx.com]
Envoyé : 4 septembre 2010 07:36
À : general-networking
Objet : RE: qnet 6.5.0 and mclbytes
Try manually specifying the correct MTU to qnet on the command line. I suspect it is trying to guess it, and is getting
it wrong.
--
aboyd
________________________________
From: Mario Charest [mailto:community-noreply@qnx.com]
Sent: Fri 9/3/2010 2:22 PM
To: general-networking
Subject: qnet 6.5.0 and mclbytes
When I use option io-pkt-v4 -de1000 -pqnet -tcpip mclbytes=8192,pagesize=8192 qnet will not work. I can see the other
machines in /net, the other machines can see them machine. Any operation like pidin or ls will never return (even after
5 minutes)
Even weirder is that the program that is block on the other machine, being ls or pidin is not in a REPLY stated but in a
RUNNING stated ???
If I get rid of the mclbytwes options everything is fine. All this time tcpip works ok.
- Mario
_______________________________________________
General
http://community.qnx.com/sf/go/post66007
_______________________________________________
General
http://community.qnx.com/sf/go/post66018
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: qnet 6.5.0 and mclbytes
|
|
Andrew Boyd(deleted)
09/07/2010 12:08 PM
post66151
|
RE: qnet 6.5.0 and mclbytes
Qnet logs from both sides would help.
--
aboyd
|
|
|
|
|
|
Mario Charest
|
RE: qnet 6.5.0 and mclbytes
|
|
Mario Charest
09/07/2010 3:05 PM
post66181
|
RE: qnet 6.5.0 and mclbytes
I have some other information. The motherboard has two build in NIC and we add another card with two NIC. The addon
card has vendor id 10c9 and internal is 10a7 (all intel).
With both devices, to get tcpip to work I have to disable all capabilities; checksum sand tso4. These are enabled by
default in our boot procedure if the capabilities are supported.
With the build-in NIC we can set mclbytes at 9016 and it works but on the external card it fails.
In the zip file you will find attached four files:
- Pci.txt output of pci -v
- Other.txt content of /proc/qnetstats on an older and "reliable" machine ( the one I'm trying to access
- Ok.txt content of /proc/qnetstats on the bad machine without setting mclbytes
io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50
- Bad.txt content of /proc/qnetstats on the bad machine with setting mclbytes and pagesize to 9016
io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50
-ptcpip mclbytes=9016,pagesize=9016
That being said Andrew so far we really like this machine aside from that issue. It's long life ( 7 years) so we would
be willing to invest some money and have QNX look into this. In the short term we can live with the situation by using
use the internal NIC for qnet and disabling all of the NICs capabilities.
This is with 6.5.0.
Cheers,
-----Message d'origine-----
De : Andrew Boyd [mailto:community-noreply@qnx.com]
Envoyé : 7 septembre 2010 12:09
À : general-networking
Objet : RE: qnet 6.5.0 and mclbytes
Qnet logs from both sides would help.
--
aboyd
_______________________________________________
General
http://community.qnx.com/sf/go/post66151
|
|
|
|
|
|
Andrew Boyd(deleted)
|
RE: qnet 6.5.0 and mclbytes
|
|
Andrew Boyd(deleted)
09/07/2010 3:13 PM
post66186
|
RE: qnet 6.5.0 and mclbytes
I have forwarded this to Hugh to look at when he
gets back from vacation. Sounds like another e1000
variation!
-----Original Message-----
From: Mario Charest [mailto:community-noreply@qnx.com]
Sent: Tuesday, September 07, 2010 3:05 PM
To: general-networking
Subject: RE: qnet 6.5.0 and mclbytes
I have some other information. The motherboard has two build in NIC and we add another card with two NIC. The addon
card has vendor id 10c9 and internal is 10a7 (all intel).
With both devices, to get tcpip to work I have to disable all capabilities; checksum sand tso4. These are enabled by
default in our boot procedure if the capabilities are supported.
With the build-in NIC we can set mclbytes at 9016 and it works but on the external card it fails.
In the zip file you will find attached four files:
- Pci.txt output of pci -v
- Other.txt content of /proc/qnetstats on an older and "reliable" machine ( the one I'm trying to access
- Ok.txt content of /proc/qnetstats on the bad machine without setting mclbytes
io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50
- Bad.txt content of /proc/qnetstats on the bad machine with setting mclbytes and pagesize to 9016
io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50
-ptcpip mclbytes=9016,pagesize=9016
That being said Andrew so far we really like this machine aside from that issue. It's long life ( 7 years) so we would
be willing to invest some money and have QNX look into this. In the short term we can live with the situation by using
use the internal NIC for qnet and disabling all of the NICs capabilities.
This is with 6.5.0.
Cheers,
-----Message d'origine-----
De : Andrew Boyd [mailto:community-noreply@qnx.com]
Envoyé : 7 septembre 2010 12:09
À : general-networking
Objet : RE: qnet 6.5.0 and mclbytes
Qnet logs from both sides would help.
--
aboyd
_______________________________________________
General
http://community.qnx.com/sf/go/post66151
_______________________________________________
General
http://community.qnx.com/sf/go/post66181
|
|
|
|
|
|
Mario Charest
|
RE: qnet 6.5.0 and mclbytes
|
|
Mario Charest
09/07/2010 4:45 PM
post66208
|
RE: qnet 6.5.0 and mclbytes
Much appreciated!
-----Message d'origine-----
De : Andrew Boyd [mailto:community-noreply@qnx.com]
Envoyé : 7 septembre 2010 15:14
À : general-networking
Objet : RE: qnet 6.5.0 and mclbytes
I have forwarded this to Hugh to look at when he gets back from vacation. Sounds like another e1000 variation!
-----Original Message-----
From: Mario Charest [mailto:community-noreply@qnx.com]
Sent: Tuesday, September 07, 2010 3:05 PM
To: general-networking
Subject: RE: qnet 6.5.0 and mclbytes
I have some other information. The motherboard has two build in NIC and we add another card with two NIC. The addon
card has vendor id 10c9 and internal is 10a7 (all intel).
With both devices, to get tcpip to work I have to disable all capabilities; checksum sand tso4. These are enabled by
default in our boot procedure if the capabilities are supported.
With the build-in NIC we can set mclbytes at 9016 and it works but on the external card it fails.
In the zip file you will find attached four files:
- Pci.txt output of pci -v
- Other.txt content of /proc/qnetstats on an older and "reliable" machine ( the one I'm trying to access
- Ok.txt content of /proc/qnetstats on the bad machine without setting mclbytes
io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50
- Bad.txt content of /proc/qnetstats on the bad machine with setting mclbytes and pagesize to 9016
io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50
-ptcpip mclbytes=9016,pagesize=9016
That being said Andrew so far we really like this machine aside from that issue. It's long life ( 7 years) so we would
be willing to invest some money and have QNX look into this. In the short term we can live with the situation by using
use the internal NIC for qnet and disabling all of the NICs capabilities.
This is with 6.5.0.
Cheers,
-----Message d'origine-----
De : Andrew Boyd [mailto:community-noreply@qnx.com]
Envoyé : 7 septembre 2010 12:09
À : general-networking
Objet : RE: qnet 6.5.0 and mclbytes
Qnet logs from both sides would help.
--
aboyd
_______________________________________________
General
http://community.qnx.com/sf/go/post66151
_______________________________________________
General
http://community.qnx.com/sf/go/post66181
_______________________________________________
General
http://community.qnx.com/sf/go/post66186
|
|
|
|
|
|
Hugh Brown
|
Re: qnet 6.5.0 and mclbytes
|
|
Hugh Brown
09/13/2010 9:03 AM
post66919
|
Re: qnet 6.5.0 and mclbytes
Do you specify the MTU size with ifconfig? Unfortunately I don't have one of
these adapters to try and reproduce the problem.
On 10-09-07 3:05 PM, "Mario Charest" <community-noreply@qnx.com> wrote:
> I have some other information. The motherboard has two build in NIC and we
> add another card with two NIC. The addon card has vendor id 10c9 and internal
> is 10a7 (all intel).
>
> With both devices, to get tcpip to work I have to disable all capabilities;
> checksum sand tso4. These are enabled by default in our boot procedure if the
> capabilities are supported.
>
> With the build-in NIC we can set mclbytes at 9016 and it works but on the
> external card it fails.
>
> In the zip file you will find attached four files:
>
> - Pci.txt output of pci -v
> - Other.txt content of /proc/qnetstats on an older and "reliable" machine (
> the one I'm trying to access
> - Ok.txt content of /proc/qnetstats on the bad machine without setting
> mclbytes
> io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet
> bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50
> - Bad.txt content of /proc/qnetstats on the bad machine with setting mclbytes
> and pagesize to 9016
> io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet
> bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50 -ptcpip
> mclbytes=9016,pagesize=9016
>
> That being said Andrew so far we really like this machine aside from that
> issue. It's long life ( 7 years) so we would be willing to invest some money
> and have QNX look into this. In the short term we can live with the situation
> by using use the internal NIC for qnet and disabling all of the NICs
> capabilities.
>
> This is with 6.5.0.
>
> Cheers,
>
> -----Message d'origine-----
> De : Andrew Boyd [mailto:community-noreply@qnx.com]
> Envoyé : 7 septembre 2010 12:09
> À : general-networking
> Objet : RE: qnet 6.5.0 and mclbytes
>
> Qnet logs from both sides would help.
>
> --
> aboyd
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post66151
>
>
>
_______________________________________________
General
http://community.
> qnx.com/sf/go/post66181
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Mario Charest
|
RE: qnet 6.5.0 and mclbytes
|
|
Mario Charest
09/13/2010 9:42 AM
post66933
|
RE: qnet 6.5.0 and mclbytes
Yes the MTU size is specify with ifconfig
We could send you the machine if you'd like ;-) We also have trouble with startup-apic/pci-bios-v2 that make the
computer reboot as soon as the image starts.
-----Message d'origine-----
De : Hugh Brown [mailto:community-noreply@qnx.com]
Envoyé : 13 septembre 2010 09:04
À : general-networking
Objet : Re: qnet 6.5.0 and mclbytes
Do you specify the MTU size with ifconfig? Unfortunately I don't have one of these adapters to try and reproduce the
problem.
On 10-09-07 3:05 PM, "Mario Charest" <community-noreply@qnx.com> wrote:
> I have some other information. The motherboard has two build in NIC
> and we add another card with two NIC. The addon card has vendor id
> 10c9 and internal is 10a7 (all intel).
>
> With both devices, to get tcpip to work I have to disable all
> capabilities; checksum sand tso4. These are enabled by default in our
> boot procedure if the capabilities are supported.
>
> With the build-in NIC we can set mclbytes at 9016 and it works but on
> the external card it fails.
>
> In the zip file you will find attached four files:
>
> - Pci.txt output of pci -v
> - Other.txt content of /proc/qnetstats on an older and "reliable"
> machine ( the one I'm trying to access
> - Ok.txt content of /proc/qnetstats on the bad machine without setting
> mclbytes
> io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet
> bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50
> - Bad.txt content of /proc/qnetstats on the bad machine with setting
> mclbytes and pagesize to 9016
> io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet
> bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50 -ptcpip
> mclbytes=9016,pagesize=9016
>
> That being said Andrew so far we really like this machine aside from
> that issue. It's long life ( 7 years) so we would be willing to invest
> some money and have QNX look into this. In the short term we can live
> with the situation by using use the internal NIC for qnet and
> disabling all of the NICs capabilities.
>
> This is with 6.5.0.
>
> Cheers,
>
> -----Message d'origine-----
> De : Andrew Boyd [mailto:community-noreply@qnx.com]
> Envoyé : 7 septembre 2010 12:09
> À : general-networking
> Objet : RE: qnet 6.5.0 and mclbytes
>
> Qnet logs from both sides would help.
>
> --
> aboyd
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post66151
>
>
>
_______________________________________________
General
http://community.
> qnx.com/sf/go/post66181
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
_______________________________________________
General
http://community.qnx.com/sf/go/post66919
|
|
|
|
|
|
Hugh Brown
|
Re: qnet 6.5.0 and mclbytes
|
|
Hugh Brown
09/13/2010 9:45 AM
post66934
|
Re: qnet 6.5.0 and mclbytes
Yes, if you could send me the machine, that would help.
Thanks, Hugh.
On 10-09-13 9:42 AM, "Mario Charest" <community-noreply@qnx.com> wrote:
> Yes the MTU size is specify with ifconfig
>
> We could send you the machine if you'd like ;-) We also have trouble with
> startup-apic/pci-bios-v2 that make the computer reboot as soon as the image
> starts.
>
> -----Message d'origine-----
> De : Hugh Brown [mailto:community-noreply@qnx.com]
> Envoyé : 13 septembre 2010 09:04
> À : general-networking
> Objet : Re: qnet 6.5.0 and mclbytes
>
> Do you specify the MTU size with ifconfig? Unfortunately I don't have one of
> these adapters to try and reproduce the problem.
>
>
> On 10-09-07 3:05 PM, "Mario Charest" <community-noreply@qnx.com> wrote:
>
>> I have some other information. The motherboard has two build in NIC
>> and we add another card with two NIC. The addon card has vendor id
>> 10c9 and internal is 10a7 (all intel).
>>
>> With both devices, to get tcpip to work I have to disable all
>> capabilities; checksum sand tso4. These are enabled by default in our
>> boot procedure if the capabilities are supported.
>>
>> With the build-in NIC we can set mclbytes at 9016 and it works but on
>> the external card it fails.
>>
>> In the zip file you will find attached four files:
>>
>> - Pci.txt output of pci -v
>> - Other.txt content of /proc/qnetstats on an older and "reliable"
>> machine ( the one I'm trying to access
>> - Ok.txt content of /proc/qnetstats on the bad machine without setting
>> mclbytes
>> io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet
>> bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50
>> - Bad.txt content of /proc/qnetstats on the bad machine with setting
>> mclbytes and pagesize to 9016
>> io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet
>> bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50 -ptcpip
>> mclbytes=9016,pagesize=9016
>>
>> That being said Andrew so far we really like this machine aside from
>> that issue. It's long life ( 7 years) so we would be willing to invest
>> some money and have QNX look into this. In the short term we can live
>> with the situation by using use the internal NIC for qnet and
>> disabling all of the NICs capabilities.
>>
>> This is with 6.5.0.
>>
>> Cheers,
>>
>> -----Message d'origine-----
>> De : Andrew Boyd [mailto:community-noreply@qnx.com]
>> Envoyé : 7 septembre 2010 12:09
>> À : general-networking
>> Objet : RE: qnet 6.5.0 and mclbytes
>>
>> Qnet logs from both sides would help.
>>
>> --
>> aboyd
>>
>>
>>
>>
>>
>> _______________________________________________
>>
>> General
>> http://community.qnx.com/sf/go/post66151
>>
>>
>>
>
>
>
> _______________________________________________
>
> General
> http://community.
>> qnx.com/sf/go/post66181
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
|
|
|
|
|
|
Mario Charest
|
RE: qnet 6.5.0 and mclbytes
|
|
Mario Charest
09/13/2010 9:57 AM
post66937
|
RE: qnet 6.5.0 and mclbytes
Awesome, we'll send it to you next week as we only have one machine and still need it for further testing/validation ,
we will receive the others Friday.
Thanks
Mario
-----Message d'origine-----
De : Hugh Brown [mailto:community-noreply@qnx.com]
Envoyé : 13 septembre 2010 09:46
À : general-networking
Objet : Re: qnet 6.5.0 and mclbytes
Yes, if you could send me the machine, that would help.
Thanks, Hugh.
On 10-09-13 9:42 AM, "Mario Charest" <community-noreply@qnx.com> wrote:
> Yes the MTU size is specify with ifconfig
>
> We could send you the machine if you'd like ;-) We also have trouble
> with
> startup-apic/pci-bios-v2 that make the computer reboot as soon as the
> image starts.
>
> -----Message d'origine-----
> De : Hugh Brown [mailto:community-noreply@qnx.com]
> Envoyé : 13 septembre 2010 09:04
> À : general-networking
> Objet : Re: qnet 6.5.0 and mclbytes
>
> Do you specify the MTU size with ifconfig? Unfortunately I don't have
> one of these adapters to try and reproduce the problem.
>
>
> On 10-09-07 3:05 PM, "Mario Charest" <community-noreply@qnx.com> wrote:
>
>> I have some other information. The motherboard has two build in NIC
>> and we add another card with two NIC. The addon card has vendor id
>> 10c9 and internal is 10a7 (all intel).
>>
>> With both devices, to get tcpip to work I have to disable all
>> capabilities; checksum sand tso4. These are enabled by default in
>> our boot procedure if the capabilities are supported.
>>
>> With the build-in NIC we can set mclbytes at 9016 and it works but
>> on the external card it fails.
>>
>> In the zip file you will find attached four files:
>>
>> - Pci.txt output of pci -v
>> - Other.txt content of /proc/qnetstats on an older and "reliable"
>> machine ( the one I'm trying to access
>> - Ok.txt content of /proc/qnetstats on the bad machine without
>> setting mclbytes
>> io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet
>> bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50
>> - Bad.txt content of /proc/qnetstats on the bad machine with setting
>> mclbytes and pagesize to 9016
>> io-pkt-v4 -t4 -de1000 transmit=2048,receive=2048,priority=100 -pqnet
>> bind=wm0,no_slog=1,periodic_ticks=100,tx_retries=50 -ptcpip
>> mclbytes=9016,pagesize=9016
>>
>> That being said Andrew so far we really like this machine aside from
>> that issue. It's long life ( 7 years) so we would be willing to
>> invest some money and have QNX look into this. In the short term we
>> can live with the situation by using use the internal NIC for qnet
>> and disabling all of the NICs capabilities.
>>
>> This is with 6.5.0.
>>
>> Cheers,
>>
>> -----Message d'origine-----
>> De : Andrew Boyd [mailto:community-noreply@qnx.com]
>> Envoyé : 7 septembre 2010 12:09
>> À : general-networking
>> Objet : RE: qnet 6.5.0 and mclbytes
>>
>> Qnet logs from both sides would help.
>>
>> --
>> aboyd
>>
>>
>>
>>
>>
>> _______________________________________________
>>
>> General
>> http://community.qnx.com/sf/go/post66151
>>
>>
>>
>
>
>
> _______________________________________________
>
> General
> http://community.
>> qnx.com/sf/go/post66181
>
--
Hugh Brown (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd. (613) 591-3579 (fax)
175 Terence Matthews Cres. email: hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
...
|
|
|
|
|
|
