From owner-freebsd-firewire@FreeBSD.ORG Thu Apr 7 06:44:01 2005 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6FB316A4CE for ; Thu, 7 Apr 2005 06:44:01 +0000 (GMT) Received: from mx1.mail.ru (mx1.mail.ru [194.67.23.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94D5A43D48 for ; Thu, 7 Apr 2005 06:44:01 +0000 (GMT) (envelope-from batuto@mail.ru) Received: from [80.87.192.2] (port=56483 helo=kadaver) by mx1.mail.ru with asmtp id 1DJQkC-000LTT-00 for freebsd-firewire@freebsd.org; Thu, 07 Apr 2005 10:44:00 +0400 From: "Yan V. Batuto" To: freebsd-firewire@freebsd.org Date: Thu, 7 Apr 2005 10:43:09 +0400 User-Agent: KMail/1.8 References: <200504061910.44800.batuto@mail.ru> <874qejcpud.wl@tora.nunu.org> In-Reply-To: <874qejcpud.wl@tora.nunu.org> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504071043.09924.batuto@mail.ru> Subject: Re: sbp failure X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2005 06:44:02 -0000 > VIA chip doesn't seem to work without cyclemaster. > > At Wed, 6 Apr 2005 19:10:42 +0400, > Yan V. Batuto wrote: > > > > Hi, anybody... > > > > I encountered a trouble attaching external firewire hdd drive. > > > > When drive is connected, it looks like fwohci founds it, but sbp module failed to > > get reply from device. > > kernel: sbp0:0:0 request timeout(cmd orb:0x1bafd28c) ... agent reset > > kernel: sbp0:0:0 request timeout(cmd orb:0x1bafd3c4) ... target reset > > kernel: sbp0:0:0 request timeout(cmd orb:0x1bafd634) ... reset start > > kernel: sbp0:0:0 login failed > > kernel: sbp0:0:0 sbp_reset_start failed: resp=60 Thank you for reply. I forgot to mention about FreeBSD version. It's RELENG_5 (12.04.2005) > Try 'fwcontrol -r' at this point. Bus reset does not help. Apr 7 08:38:00 yb3791 kernel: fwohci0: Initiate bus reset Apr 7 08:38:00 yb3791 kernel: fwohci0: BUS reset Apr 7 08:38:00 yb3791 kernel: fwohci0: node_id=0xc800ffc1, gen=7, CYCLEMASTER mode Apr 7 08:38:00 yb3791 kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) Apr 7 08:38:00 yb3791 kernel: firewire0: bus manager 1 (me) Apr 7 08:39:00 yb3791 kernel: sbp0:0:0 request timeout(cmd orb:0x198e0b14) ... Apr 7 08:41:06 yb3791 kernel: fwohci0: Initiate bus reset Apr 7 08:41:06 yb3791 kernel: fwohci0: BUS reset Apr 7 08:41:06 yb3791 kernel: fwohci0: node_id=0xc800ffc1, gen=8, CYCLEMASTER mode Apr 7 08:41:06 yb3791 kernel: firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) Apr 7 08:41:06 yb3791 kernel: firewire0: bus manager 1 (me) Apr 7 08:42:07 yb3791 kernel: sbp0:0:0 request timeout(cmd orb:0x198e0d84) ... ------------------------------------------------------ Best regards! Yan Batuto