We are using the Intel 82559 Ethernet controller with QNX4.25 and a Geode
CPU. Sometimes the Net.ether82557 driver appears to load OK, but spits out
an “WAIT_CMD Timeout” error each time that we attempt to Tx a packet. The
packets are copunted at the IP level (using netstat) but are not counted at
the Ethernet level (using Netinfo) and do not get transmitted. Can anyone
help me understand the meaing of the “WAIT_CMD TImeout” error message?
Andrew McCartney
Aksys, Ltd.
Hi Andrew,
When you say that they don’t get counted on the ethernet level, do you mean
you are not monitoring them there? Just wondering, but does netinfo -l give
any hint of errors?
Regards,
E.
Andrew McCartney <amccartney@aksys.com> wrote:
We are using the Intel 82559 Ethernet controller with QNX4.25 and a Geode
CPU. Sometimes the Net.ether82557 driver appears to load OK, but spits out
an “WAIT_CMD Timeout” error each time that we attempt to Tx a packet. The
packets are copunted at the IP level (using netstat) but are not counted at
the Ethernet level (using Netinfo) and do not get transmitted. Can anyone
help me understand the meaing of the “WAIT_CMD TImeout” error message?Andrew McCartney
Aksys, Ltd.
Eric,
All the counters in netinfo remain at 0. The packet counters in netstat
increment for each packet sent. On the console there is a “WAIT_CMD Timeout”
message for each packet.
Andrew
“Erick Muis” <emuis@node55.ott.qnx.com> wrote in message
news:c15vj8$iel$2@inn.qnx.com…
Hi Andrew,
When you say that they don’t get counted on the ethernet level, do you
mean
you are not monitoring them there? Just wondering, but does netinfo -l
give
any hint of errors?Regards,
E.
Andrew McCartney <> amccartney@aksys.com> > wrote:
We are using the Intel 82559 Ethernet controller with QNX4.25 and a
Geode
CPU. Sometimes the Net.ether82557 driver appears to load OK, but spits
out
an “WAIT_CMD Timeout” error each time that we attempt to Tx a packet.
The
packets are copunted at the IP level (using netstat) but are not counted
at
the Ethernet level (using Netinfo) and do not get transmitted. Can
anyone
help me understand the meaing of the “WAIT_CMD TImeout” error message?Andrew McCartney
Aksys, Ltd.
\
Erick Muis
Hardware Group
QNX Software Systems Ltd.
Email: emuis at qnx.com
“Andrew McCartney” <amccartney@aksys.com> wrote in message
news:c15voi$j1c$1@inn.qnx.com…
Eric,
All the counters in netinfo remain at 0. The packet counters in netstat
increment for each packet sent. On the console there is a “WAIT_CMD
Timeout”
message for each packet.
It’s either a problem with IRQ, or the card for some reason can’t detect the
cable speed or thing there is not cable.
post output of netinfo -l
Andrew
“Erick Muis” <> emuis@node55.ott.qnx.com> > wrote in message
news:c15vj8$iel$> 2@inn.qnx.com> …
Hi Andrew,When you say that they don’t get counted on the ethernet level, do you
mean
you are not monitoring them there? Just wondering, but does netinfo -l
give
any hint of errors?Regards,
E.
Andrew McCartney <> amccartney@aksys.com> > wrote:
We are using the Intel 82559 Ethernet controller with QNX4.25 and a
Geode
CPU. Sometimes the Net.ether82557 driver appears to load OK, but spits
out
an “WAIT_CMD Timeout” error each time that we attempt to Tx a packet.
The
packets are copunted at the IP level (using netstat) but are not
counted
at
the Ethernet level (using Netinfo) and do not get transmitted. Can
anyone
help me understand the meaing of the “WAIT_CMD TImeout” error message?Andrew McCartney
Aksys, Ltd.
\
Erick Muis
Hardware Group
QNX Software Systems Ltd.
Email: emuis at qnx.com
“Andrew McCartney” <amccartney@aksys.com> wrote in message
news:c15qtu$etl$1@inn.qnx.com…
We are using the Intel 82559 Ethernet controller with QNX4.25 and a Geode
CPU. Sometimes the Net.ether82557 driver appears to load OK, but spits out
an “WAIT_CMD Timeout” error each time that we attempt to Tx a packet. The
packets are copunted at the IP level (using netstat) but are not counted
at
the Ethernet level (using Netinfo) and do not get transmitted. Can anyone
help me understand the meaing of the “WAIT_CMD TImeout” error message?
The WAIT_CMD Timeout occurs when a command is sent to the controller and the
controller does not acknowledge the command after 50ms.
Please post the output from ‘sin in’, ‘sin ver’ as well as ‘show_pci -vv’.
Andrew McCartney
Aksys, Ltd.