Is this on exactly the same hardware, as 6.3?

Because it sounds like you're somehow missing
or dropping interrupts.

The io-net driver, when run with the shim under
io-pkt, does exactly the same hardware accessing
as it does under io-net - it's the same binary
after all.

Is the interrupt shared?  That causes weirdness.

Is there any very high priority processing that
is occuring?

I would probably use the instrumented kernel to
try to get some more information about what's 
actually happening - if the interrupt is firing,
and io-pkt is ignoring it - you will see it.

--
aboyd



-----Original Message-----
From: Dan Tascione [mailto:community-noreply@qnx.com] 
Sent: Monday, January 19, 2009 3:46 PM
To: ionetmig-networking
Subject: QNX 6.4 using old QNX 6.3 CAN drivers

I'm using some old drivers for a CAN card that used io-net. They start
up fine in QNX 6.4 and seem to share the same io-pkt instance as the
Ethernet drivers.

Everything generally works OK, but we are seeing some odd latency in
receiving packets from the CAN card. When we have some decent network
traffic going into/out of the network, CAN packets come in at their
desired rates. When the network traffic stops, the CAN packets only come
in every 200-500ms or so.

Could this be related to forcing io-pkt into single threaded mode due to
it loading older drivers? If so, is there a way to force these drivers
to use different instances of io-pkt? I tried the mount command but that
returned errors about missing symbols.



_______________________________________________
io-net migration
http://community.qnx.com/sf/go/post20350