From owner-freebsd-firewire@FreeBSD.ORG Tue Jun 10 21:17:33 2008 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A0C31065670; Tue, 10 Jun 2008 21:17:33 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id EC7018FC14; Tue, 10 Jun 2008 21:17:32 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 68D7E1A93D2; Tue, 10 Jun 2008 14:15:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at X-Spam-Flag: NO X-Spam-Score: -4.399 X-Spam-Level: X-Spam-Status: No, score=-4.399 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599] Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RROcs3JekV0p; Tue, 10 Jun 2008 14:15:07 -0700 (PDT) Received: from iago.office.miralink.com (iago.office.miralink.com [10.0.0.40]) by plato.miralink.com (Postfix) with ESMTP id 1C34A1A93D1; Tue, 10 Jun 2008 14:15:07 -0700 (PDT) Message-ID: <484EEF6B.7010407@miralink.com> Date: Tue, 10 Jun 2008 14:17:31 -0700 From: Sean Bruno User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Hidetoshi Shimokawa References: <4846F3F9.1080302@miralink.com> <48482800.8000501@miralink.com> In-Reply-To: <48482800.8000501@miralink.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-firewire@freebsd.org Subject: Re: sbp_targ errors with windows initiators X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2008 21:17:33 -0000 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