Date: Tue, 10 Jun 2008 14:17:31 -0700 From: Sean Bruno <sbruno@miralink.com> To: Hidetoshi Shimokawa <simokawa@FreeBSD.ORG> Cc: freebsd-firewire@freebsd.org Subject: Re: sbp_targ errors with windows initiators Message-ID: <484EEF6B.7010407@miralink.com> In-Reply-To: <48482800.8000501@miralink.com> References: <4846F3F9.1080302@miralink.com> <48482800.8000501@miralink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?484EEF6B.7010407>