From owner-freebsd-firewire@FreeBSD.ORG Mon Aug 8 11:07:02 2011 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 EE2FE1065672 for ; Mon, 8 Aug 2011 11:07:02 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DC4A98FC18 for ; Mon, 8 Aug 2011 11:07:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p78B72uJ078522 for ; Mon, 8 Aug 2011 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p78B72Qm078520 for freebsd-firewire@FreeBSD.org; Mon, 8 Aug 2011 11:07:02 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Aug 2011 11:07:02 GMT Message-Id: <201108081107.p78B72Qm078520@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-firewire@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org 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: Mon, 08 Aug 2011 11:07:03 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/155303 firewire [firewire] Mounted firewire disks prevent reboot o kern/144843 firewire [firewire] [panic] fwcontrol(8) -S causes kernel panic o kern/143623 firewire [firewire] firewire fails to attach DV camera and down o kern/139549 firewire [firewire] reconnecting a firewire disk does not cause o kern/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re p kern/125673 firewire [firewire] [panic] FreeBSD7 panics when kldunloading f o kern/122951 firewire [firewire] video-transfer via fwcontrol triggers a pan o kern/118093 firewire [firewire] firewire bus reset hogs CPU, causing data t p kern/114646 firewire [firewire] [patch] firewire fails after suspend/resume o kern/113785 firewire [firewire] dropouts when playing DV on firewire o kern/97208 firewire [firewire] System hangs / locks up when a firewire dis o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 12 problems total. From owner-freebsd-firewire@FreeBSD.ORG Mon Aug 8 17:22:33 2011 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 9B44C1065672 for ; Mon, 8 Aug 2011 17:22:33 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.re1.yahoo.com (mrout1-b.corp.re1.yahoo.com [69.147.107.20]) by mx1.freebsd.org (Postfix) with ESMTP id 700B98FC16 for ; Mon, 8 Aug 2011 17:22:33 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout1-b.corp.re1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p78HC8tt075135; Mon, 8 Aug 2011 10:12:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1312823529; bh=uVTNiL0uOQYWG3FfjKCTUU3L3Q9X0y2f4Cro8h0X5yM=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=W6ufbd6XXX3zqcD5+lL2m/i7e8iT25N9AWCa+9LdcUiBzwztvrOhcphbdAz+pTXYc 703qt89KWTA8HEQp4CZL41WLQwuHGc9AJgzV51KrlgXqBH+eBbnLxUgnameZnUiwFV 7SJX6mhwKr/+EILXfaKCdxMSwJPevHWIDYSzdNmI= From: Sean Bruno To: Jim Pryor In-Reply-To: <20110806155511.GA3034@vaio.jimpryor.net> References: <20110806155511.GA3034@vaio.jimpryor.net> Content-Type: text/plain; charset="UTF-8" Date: Mon, 08 Aug 2011 10:12:08 -0700 Message-ID: <1312823528.22563.6.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Cc: "freebsd-firewire@freebsd.org" Subject: Re: Firewire drives not recognized when I load sbp 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: Mon, 08 Aug 2011 17:22:33 -0000 Jim: thanks for the detailed information. Let me digest and review this tonight and see if I can determine what the badness here is. Sean On Sat, 2011-08-06 at 08:55 -0700, Jim Pryor wrote: > I also posted this to the Peripheral Hardware section of the forums. > Apologies if it's inappropriate to also mail here. This mailing list > seems the right place to discuss my issue, but it looks like it's been > very quiet for the past year. > > > What I'll call Computer Bad: Mac mini (Intel Core 2), was running > FreeBSD 8.2-release, tried upgrading to 8-STABLE, but these issues > persist. Has a single Firewire 400 port. > > Device 1: a dual Firewire enclosure, has both a Firewire 400 port and > two Firewire 800 ports. Contains two drives. > > Device 2: a pocket-sized Firewire enclosure, has one Firewire 400 and > one Firewire 800 port. > > Device 3 is this: . It attaches to > the mini via Firewire and USB, and provides a hub for each, and > additionally has a drive on the Firewire bus. We can ignore the USB > aspects of this. > > I'll compare against Computer Good: which is a Sony Vaio, whose details > probably not important, except it's also running FreeBSD 8-STABLE. After > I do a `kldload sbp` on this machine, and attach either of Device 1 or > 2, or both of them in a chain, they all are immediately recognized and > show up as /dev/da0, da1, and da2. > > However that's just for testing. I need to get these devices recognized > on Computer Bad. > > And on Computer Bad, **when Device 3 is in the mix**, and the other > devices are chained off it, I can do so--- although it takes some > voodoo. I cannot have the sbp module loaded at boot time; if I do so the > boot will hang until I disconnect or power down all attached Firewire > devices. However, if I wait until boot has completed, then do a `kldload > sbp`, once or twice the devices were then recognized. Most often, > though, I have to do a dance of unplugging the devices, replugging them, > power-cycling them, fwcontrol -r'ing, and so on. If there's a system > that works reliably, I haven't been able to find it. Nor have I found > any way to make this work solely from the commandline. `camcontrol > rescan all` hangs until I disconnect or power down the devices. > `fwcontrol -r` resets the bus, but the devices don't show up. And so on. > However, with some persistence at the cable/power-cycling dance, I have > always been able to get the drives recognized when they're chained off > of Device 3. And once the drives get recognized, they give me no further > trouble during that session. Even if I then power Device 3 down. I've > transferred 1 TB of data to Device 1, I think without any trouble. > > I'd live with this if I could. However, I can't keep Device 3 in this > setup; it's required elsewhere. > > And **without Device 3**, I can't find any way to get Devices 1 and 2, > either together or solo, to be recognized on Computer Bad. I've tried > connecting to either their Firewire 400 or their Firewire 800 ports > (though on the other side, Computer Bad is only attempting Firewire > 400). I've tried doing the `kldload sbp` before connecting them, or > after, or whatever, and no luck. I've tried `sysctl -w > hw.firewire.sbp.auto_login=0` and `sysctl -w > hw.firewire.nocyclemaster=1` at various points, but this doesn't seem to > change anything. > > > These problems showed up when Computer Bad had a fresh 8.2-release > installation. I tried upgrading to 8-STABLE, which is what Computer Good > had, but no joy there. > > I've been searching and searching but haven't found much, even ideas to > try. Any suggestions would be much appreciated. > > Here are some details. > > 1. Here's uname -a, pciconf -lcv, kldstat, and sysctl hw.firewire on Computer Good: > > 2. Here's the stretch of dmesg where the devices are connected and > successfully recognized on Computer Good: > > 3. And here's what I then see on Computer Good (fwcontrol, fwcontrol -t, > and camcontrol devlist -v): > > 4. Here's uname -a, pciconf -lcv, kldstat, and sysctl hw.firewire on > Computer Bad: . Notice the > hw.firewire.sbp.auto_login is at 0, that's because following some > diagnostic advice I found while searching I disabled that in > /boot/loader.conf. It doesn't seem to affect my results at all. > 5. Here's the stretch of dmesg where the devices are connected but fail > to be recognized on Computer Bad: > 6. Here are fwcontrol, fwcontrol -t, and camcontrol devlist -v on > Computer Bad, before kldloading sbp and attaching the devices: > > 7. Here are the results of the same, after kldloading sbp and attaching > the devices: . At this point, doing > `sysctl -w hw.firewire.sbp.auto_login=1; fwcontrol -r` seems to produce > no change. Allowing sbp to load with auto_login=1 from the beginning > produces no change either. > > At some points in my experimenting, I was able to get one or two > additional entries in the `fwcontrol` output on Computer Bad, but I > can't reproduce that now. And I didn't notice any additional progress > when that occurred. >