Re: sbp_targ errors with windows initiators
Sean Bruno <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.firewire |
|---|---|
| Message-ID | <[email protected]> |
So, it appears that the firewire target (sbp_targ) has some kind of race condition that makes a windows initiator fall down and cry. Most times when I connect a windows initiator to my sbp_targ host, I get the following: fwohci0: BUS reset fwohci0: node_id=0x8800ffc0, gen=5, non CYCLEMASTER mode sbp_targ_recv: cannot resolve nodeid=1 sbp_targ_recv: rtcode = 6 lo == 0x0 firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 fwohci0: txd err= 3 miss Ack err firewire0: New S400 device ID:0011060000004d63 fwohci0: txd err= 3 miss Ack err fwohci0: txd err= 3 miss Ack err 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 fwohci0: txd err= 3 miss Ack err Sometimes, the initiator succeeds in the login process and sometimes it doesn't. I'm not sure why yet. Any clues? -- Sean Bruno MiraLink Corporation 6015 NE 80th Ave, Ste 100 Portland, OR 97218 Phone 503-621-5143 Fax 503-621-5199 _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-firewire To unsubscribe, send any mail to "[email protected]"