From owner-freebsd-current@FreeBSD.ORG Mon Aug 23 17:12:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0CB616A4CE for ; Mon, 23 Aug 2004 17:12:42 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4BC643D39 for ; Mon, 23 Aug 2004 17:12:42 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 97AA372DD4; Mon, 23 Aug 2004 10:12:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 92BBD72DCB; Mon, 23 Aug 2004 10:12:42 -0700 (PDT) Date: Mon, 23 Aug 2004 10:12:42 -0700 (PDT) From: Doug White To: George Hartzell In-Reply-To: <16681.26689.215660.854423@rosebud.alerce.com> Message-ID: <20040823101023.R4628@carver.gumbysoft.com> References: <16679.59263.287454.325068@rosebud.alerce.com> <16681.26689.215660.854423@rosebud.alerce.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Help making sense of firewire disk enclosure dilema X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Aug 2004 17:12:42 -0000 On Sun, 22 Aug 2004, George Hartzell wrote: > The enclosure is smeared across the kitchen table at the moment (see > below), so I can't give it's exact reaction to suggestion, but I have > some representative output. > > In the course of mucking around, I've tried various combinations of > 'fwcontrol -r' and 'camcontrol rescan all'. I'm not sure which caused > which part of the dmesg output below, but it might be interesting: > > sbp0:0:0 request timeout(cmd orb:0x163ca634) ... agent reset > sbp0:0:0 request timeout(cmd orb:0x163ca76c) ... target reset > fwohci0: BUS reset > fwohci0: node_id=0xc800ffc0, gen=6, CYCLEMASTER mode > firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) > firewire0: bus manager 0 (me) > sbp0:0:0 request timeout(cmd orb:0x163ca9dc) ... reset start > fwohci0: txd err= 3 miss Ack err > sbp0:0:0 sbp_reset_start failed: resp=22 > firewire0: split transaction timeout dst=0xffc0 tl=0x30 state=4 > sbp0:0:0 sbp_reset_start failed: resp=60 I've seen this before, if one of the nodes locks up during negotiation. My Athlon box with APIC enabled has a tendnecy to do that when the machine it was cabled to for debugging would reboot. > I figured out how to ask fwcontrol to tell me more about the device > inside the enclosure, and discovered that it's a Prolific PL-3507. A > little googling about suggests that it's a well known PITA device, e.g. > > http://forum.rpc1.org/viewtopic.php?t=25140&postdays=0&postorder=asc&&start=0&sid=0a359d410cfd87df72f2543365922421 > > So, I'm left to decide whether to muck with the firmware or just chuck > it..... I'd give up now. :) > Are there "quirks" for firewire devices like there used to be (are?) > for usb devices? Not that I'm aware of, but I don't know if firewire supports device/vendor IDs like USB that can be used to match the quirk. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org