diag

[Carl K. <ca...@pe...>]

A friend is helping me by coding up a diagnostic tool.  It is meant to
test firewire hardware.  We don't have a baseline to know the quality
of the hardware we are testing, so we are not sure if the results are
due to faulty hardware or faulty code or we just don't know how to
interpret the results.

Could someone help review this?

https://gitorious.org/~eviljoel/cfk_misc/fwdiag-cleanup/

1 box with 2 controllers, cable between the 2, here is what the
results look like:

************************************
(veyepar)juser@pc9d:~/fwdiag-cleanup$ sudo ./async-loop-ck
0, node_id: 65473, local_node_id: 65473, devices[ 0
]->receiveDescriptor: /dev/fw0
1, node_id: 65472, local_node_id: 65472, devices[ 1
]->receiveDescriptor: /dev/fw1
2, node_id: 65472, local_node_id: 65473, devices[ 0 ]->sendDescriptor: /dev/fw2
3, node_id: 65473, local_node_id: 65472, devices[ 1 ]->sendDescriptor: /dev/fw3
Main process: starting receiver
Main: receiver started, pid: 11107; waiting 4 seconds...
 Receiver child process 11107 starting...
Main process: starting sender
Main: sender started, pid: 11108
Main process, waiting for child processes to finish...
 Sender child process 11108 starting...

 Received 524289389 bytes = 500.00 MB in 511745 packets in 21 seconds
 ...receiver finished

 Sent 524288119 bytes = 500.00 MB in 511753 packets in 21 seconds
 ...sender finished
Main: processes finished

Main process: starting receiver
Main: receiver started, pid: 11109; waiting 4 seconds...
 Receiver child process 11109 starting...
 unexpected packet: 0x7cf2c
 unexpected packet: 0x7cf2d
 unexpected packet: 0x7cf2e
 unexpected packet: 0x7cf2f
 unexpected packet: 0x7cf30
 unexpected packet: 0x7cf31
 unexpected packet: 0x7cf32
 unexpected packet: 0x7cf33
 unexpected packet: 0x7cf34
 unexpected packet: 0x7cf35
 unexpected packet: 0x7cf36
 unexpected packet: 0x7cf37
 unexpected packet: 0x7cf38
 unexpected packet: 0x7cf39
Main process: starting sender
Main: sender started, pid: 11110
Main process, waiting for child processes to finish...
 Sender child process 11110 starting...

 Received 524289257 bytes = 500.00 MB in 511746 packets in 32 seconds
 ...receiver finished

 Sent 524288119 bytes = 500.00 MB in 511753 packets in 28 seconds
 ...sender finished
Main: processes finished
************************************

And sometimes it gets stuck:

************************************
(veyepar)juser@pc9d:~/fwdiag-cleanup$ sudo ./async-loop-ck
0, node_id: 65472, local_node_id: 65472, devices[ 0
]->receiveDescriptor: /dev/fw0
1, node_id: 65473, local_node_id: 65473, devices[ 1
]->receiveDescriptor: /dev/fw1
2, node_id: 65472, local_node_id: 65473, devices[ 1 ]->sendDescriptor: /dev/fw2
3, node_id: 65473, local_node_id: 65472, devices[ 0 ]->sendDescriptor: /dev/fw3
Main process: starting receiver
Main: receiver started, pid: 11516; waiting 4 seconds...
 Receiver child process 11516 starting...
Main process: starting sender
Main: sender started, pid: 11517
Main process, waiting for child processes to finish...
 Sender child process 11517 starting...
send error: 0x10
************************************

-- 
Carl K