sbp_targ errors with windows initiators

[Sean Bruno]

When connecting to a Windows 2K3 initiator, I seem to get different 
behavior that I don't understand.  Can you explain what this firewire 
debug log means?

AFAIK my code base works with Linux, FreeBSD and OS/X based initiators, 
yet Windows eludes me.  :(


fwohci0: BUS reset
fwohci0: node_id=0x8800ffc0, gen=4, non CYCLEMASTER mode
firewire0: 2 nodes, maxhop <= 1, cable IRM = 1
sbp_targ_recv: cannot resolve nodeid=1
sbp_targ_recv: rtcode = 6 lo == 0x0
fwohci0: start AT DMA status=0
fwohci0: maxdesc: 3
fwohci0: start AT DMA status=f
fwohci0: fw_set_bus_manager: 1->1 (loop=0)
firewire0: bus manager 1
fwohci0: txd err= 3 miss Ack err
fw_explore: node 2, err = -1
fwohci0: txd err= 3 miss Ack err
fw_explore: node 2, err = -1
fwohci0: txd err= 3 miss Ack err
fw_explore: node 2, err = -1
bus_explore done
sbp_targ_recv: cannot resolve nodeid=1
sbp_targ_recv: rtcode = 6 lo == 0x0
sbp_targ_recv: cannot resolve nodeid=1
sbp_targ_recv: rtcode = 6 lo == 0x0
sbp_targ_recv: cannot resolve nodeid=1
sbp_targ_recv: rtcode = 6 lo == 0x0
sbp_targ_recv: cannot resolve nodeid=1
sbp_targ_recv: rtcode = 6 lo == 0x0