|
Robert Craig
03/14/2008 2:31 PM
post5827
|
Hi Gary:
Couple of questions: Which version of the software are you using
(freshly built or one of the pre-built binary packages)? What's the command
line that you're using for QNET over IP?
Don't be too quick to discount the driver. IP will quietly accommodate for
lost packets (you'll get delays, but you won't see any other transport
problems). QNET is a bit noisier and can accommodate for them but, will let
you know that they're happening.
We do have driver testing infrastructure that you can use
(sys/dev_qnx/drvrtest) that exercises the driver layer exclusively. It
requires a "known good" card to test the driver that you're debugging.
Robert.
-----Original Message-----
From: Gary Faulkner [mailto:gary.faulkner@ucontrol.com]
Sent: Friday, March 14, 2008 12:51 PM
To: ionetmig-networking
Subject: qnet issues
Hello:
I'm having some QNET issues under io-pkt, and I am hopeful that someone can
give me some pointers about them.
First, when I do the "mount -Tio-pkt lsm-qnet.so", qnet appears to startup
just fine. I can see other qnet nodes (in this case a node running qnet
under io-net) from the standpoint that the nodes appear in /net.
However, if (from either side) I try to access the remote node, I get this
on the io-pkt node (in slogger):
(I started with messages that happen showing that QNET is up and running).
What I cannot figure out is why I get a timeout on transmit in this
situation (at least that's what I think is happening). Eventually the stack
calls my driver's watchdog routine. Since all IP traffic is just fine on
this interface, I'm fairly certain that the driver is solid.
I also tried to use the "bind=ip" option to lsm-qnet.so, but it does not
appear that it's interpreting that option correctly; when I use the bind=ip
option, it just tells me it won't use my interface.
Jan 01 00:00:24 7 15 0 qnet(L4): lr_verify_my_name_and_domain():
qnet going online
Jan 01 00:00:25 7 15 0 qnet(L4): lr_add_ndb(): adding L4 0 addr to
ndb for nd 1 qnxbuild.ucontrol.com
Jan 01 00:00:25 7 15 0 qnet(QOS): nd_change_notify(): Node Up:
nd 1 qnxbuild.ucontrol.com
Jan 01 00:00:25 5 14 0 m->m_pkthdr.len = 164
Jan 01 00:00:37 7 15 0 qnet(kif): server_lookup(): invalid scoid
27, 0
Jan 01 00:00:37 7 15 0 qnet(QOS): tx_xmit_init_conn_pkt(): to nd 1
on L4 0
Jan 01 00:00:37 5 14 0 m->m_pkthdr.len = 100
Jan 01 00:00:37 5 14 0 m->m_pkthdr.len = 244
Jan 01 00:00:37 5 14 0 m->m_pkthdr.len = 62
Jan 01 00:00:37 5 14 0 m->m_pkthdr.len = 62
Jan 01 00:00:37 5 14 0 m->m_pkthdr.len = 62
Jan 01 00:00:37 5 14 0 m->m_pkthdr.len = 62
Jan 01 00:00:37 5 14 0 m->m_pkthdr.len = 62
Jan 01 00:00:37 5 14 0 m->m_pkthdr.len = 62
Jan 01 00:00:38 7 15 0 qnet(L4): l4_tx_timeout(): timeout: nd 1 sc
1 dc 8 ss 4 tk 18069 ct 18071
Jan 01 00:00:38 7 15 0 qnet(L4): l4_tx_timeout(): timeout: nd 1 sc
1 dc 8 ss 4 tk 18071 ct 18073
Jan 01 00:00:39 7 15 0 qnet(L4): l4_tx_timeout(): timeout: nd 1 sc
1 dc 8 ss 4 tk 18073 ct 18075
Jan 01 00:00:39 7 15 0 qnet(L4): l4_tx_timeout(): timeout: nd 1 sc
1 dc 8 ss 4 tk 18075 ct 18077
Jan 01 00:00:39 7 15 0 qnet(L4): l4_tx_timeout(): timeout: nd 1 sc
1 dc 8 ss 4 tk 18077 ct 18079
Jan 01 00:00:40 7 15 0 qnet(L4): l4_tx_timeout(): timeout: nd 1 sc
1 dc 8 ss 4 tk 18079 ct 18081
Jan 01 00:00:40 7 15 0 qnet(L4): l4_tx_timeout(): timeout: nd 1 sc
1 dc 8 ss 4 tk 18081 ct 18083
Jan 01 00:00:41 7 15 0 qnet(L4): l4_tx_timeout(): timeout: nd 1 sc
1 dc 8 ss 4 tk 18083 ct 18085
Jan 01 00:00:41 7 15 0 qnet(L4): l4_tx_timeout(): timeout: nd 1 sc
1 dc 8 ss 4 tk 18085 ct 18087
Jan 01 00:00:41 7 15 0 qnet(L4): l4_tx_timeout(): timeout: nd 1 sc
1 dc 8 ss 4 tk...
View Full Message
|
|
|
|
|
