Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote:
Hi,
We are using QNX 4.25 with Patch G installed.
It’s been a while since I debugged QNX 4 network problems…
Our problem appears only on two computers.
These machines are equiped with two different
motherboards but the same network cards -
Realtek 8139 chip (device id 8139).
→ First scenario where cable is plugged into card:
slay Net
Net -vvvv &
After about 3 seconds system prints the following
error message:
Net: Runtime error 0053
Net: Runtime error 0007
If you do a “netinfo -a” it will list all the runtime error codes with
a bit more information.
Those two are:
53 NET ( nm) freeing nodemap not in list
7 NET ( tx) failed (vc_attach ctrl pkt)
I’m not familiar with the first one (53), but the second is fairly common –
it means that an attempt was made to connect to a remote node (a vc attach
action) and that the packet to request this failed to transmit. If you
haven’t run a driver yet, that could very well be the reason for a failure
to tx a packet.
These lines are printed about 9 times every 2 seconds.
I would bet that you have 10 QNX licenses, and something is trying to
talk to them.
→ Second scenario with cable unplugged:
Net -vvvv &
Net.rtl … &
Until now everything seems to be ok, but
when I will plug the cable then:
- driver properly detects and reports link presence,
- Net starts to print similar lines as above but with different codes:
Net: Runtime error 0023
Net: Runtime error 0048
(and sometimes Runtime error 0049).
23 NET failed proc _vc_attach msg
48 NET (ivs) vid was zero
49 NET (rvs) vid was zero
23 is a step further than 7, Net managed to tx the vc_attach packet, but
failed to succeed in talking to the remote node.
I think 48 and 49 are also from the failed attaches – more symptoms.
This points to incorrectly configured, or not available, QNX native
networking, no netmap entries, incorrect netmap entries, or other
such problems.
Another strange behaviour is as follows:
If I call “netmap -f” for example then Net terminates.
Sometimes immediately or just after a couple of seconds.
That shouldn’t happen. Does it give any reason? Does it create a
core file?
I would think even a corrupt netmap file wouldn’t do it, since I’m pretty
sure netmap reads and parses the netmap file, and just sends a bunch of
new mappings to Net as the new mapping message, and will report any
errors from that.
-David
David Gibbs
QNX Training Services
dagibbs@qnx.com