From owner-freebsd-firewire@FreeBSD.ORG Mon Sep 21 11:06:53 2009 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 D94061065695 for ; Mon, 21 Sep 2009 11:06:53 +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 C72F68FC15 for ; Mon, 21 Sep 2009 11:06:53 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n8LB6rXe030222 for ; Mon, 21 Sep 2009 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n8LB6rge030218 for freebsd-firewire@FreeBSD.org; Mon, 21 Sep 2009 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Sep 2009 11:06:53 GMT Message-Id: <200909211106.n8LB6rge030218@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, 21 Sep 2009 11:06:53 -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/136946 firewire [fwohci] fwohci throws an"unrecoverable error" upon re o kern/136652 firewire [firewire] Firewire-attached "WD My Book 1028" does no 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 9 problems total. From owner-freebsd-firewire@FreeBSD.ORG Mon Sep 21 20:15:19 2009 Return-Path: Delivered-To: firewire@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id 05635106566C; Mon, 21 Sep 2009 20:15:19 +0000 (UTC) Date: Mon, 21 Sep 2009 20:15:19 +0000 From: Alexey Dokuchaev To: firewire@freebsd.org Message-ID: <20090921201518.GA10574@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: FA-101 audio interface support 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, 21 Sep 2009 20:15:19 -0000 Hi there, I've just bought Roland FA-101 external firewire audio interface box to start experimenting with multichannel sound processing on my FreeBSD laptop (NEC Versa S950). 7.2-STABLE runs quite nicely on it, and sees FW host controller (per pciconf -lv): fwohci0@pci0:6:7:2: class=0x0c0010 card=0x83191033 chip=0x8032104c rev=0x00 hdr=0x00 vendor = 'Texas Instruments (TI)' device = 'OHCI Compliant IEEE-1394 FireWire Controller' class = serial bus subclass = FireWire My intention (and ultimate goal for now) is to port ffado.org project code to our beloved FreeBSD. However, after I kldload firewire.ko and connect FA-101, I see the following in dmesg: fwohci0: <1394 Open Host Controller Interface> mem 0xb0117000-0xb01177ff,0xb0110000-0xb0113fff irq 18 at device 7.2 on pci6 fwohci0: [FILTER] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:c0:9f:00:00:d5:f6:a1 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=1, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) fwohci0: BUS reset fwohci0: node_id=0x8000ffc0, gen=3, non CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 0 (me) firewire0: root node is not cycle master capable firewire0: bus manager 0 (me) fwohci0: too many cycle lost, no cycle master presents? fwohci0: txd err= 3 miss Ack err fwohci0: txd err= 3 miss Ack err fwohci0: txd err= 3 miss Ack err These messages do not look very exciting, and apparently my box does not see the device afterwards: # fwcontrol -t crc_len: 3 generation:14 node_count:1 sid_count:1 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 5 S400 0 1 0W - - 1 0 I've tried several things; e.g. setting gapcount to 8, but fwcontrol -t shows the following lines for couple of seconds, and than it disappears (rapid repeat of fwcontrol -t command output below): # fwcontrol -t crc_len: 4 generation:19 node_count:2 sid_count:2 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 63 S400 0 0 -9W - P 1 0 01 1 8 S400 0 1 0W C - 0 0 # fwcontrol -t crc_len: 4 generation:19 node_count:2 sid_count:2 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 63 S400 0 0 -9W - P 1 0 01 1 8 S400 0 1 0W C - 0 0 # fwcontrol -t crc_len: 4 generation:20 node_count:2 sid_count:2 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 63 S400 0 1 15W - P 1 0 01 1 5 S400 0 1 0W C - 0 0 # fwcontrol -t crc_len: 4 generation:20 node_count:2 sid_count:2 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 63 S400 0 1 15W - P 1 0 01 1 5 S400 0 1 0W C - 0 0 # fwcontrol -t crc_len: 3 generation:22 node_count:1 sid_count:1 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 5 S400 0 1 0W - - 1 along with the following dmesg output that might be relevant: fw_rcv: unknown response RRESQ(6) src=0x3f tl=0x19 rt=1 data=0x6ed42504 firewire0: split transaction timeout: tl=0x19 flag=0x04 send: dst=0x00 tl=0x19 rt=0 tcode=0x4 pri=0x0 src=0x000 fw_rcv: unknown response RRESQ(6) src=0x3f tl=0x1a rt=1 data=0x6ed42504 firewire0: split transaction timeout: tl=0x1a flag=0x04 send: dst=0x00 tl=0x1a rt=0 tcode=0x4 pri=0x0 src=0x000 fw_rcv: unknown response RRESQ(6) src=0x3f tl=0x1b rt=1 data=0x6ed42504 firewire0: split transaction timeout: tl=0x1b flag=0x04 send: dst=0x00 tl=0x1b rt=0 tcode=0x4 pri=0x0 src=0x000 fwohci0: BUS reset fwohci0: node_id=0xc000ffc1, gen=22, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=23, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) fwohci0: txd err= 3 miss Ack err fwohci0: txd err= 3 miss Ack err I've been browsing through fbsd-fw@ archives tonight and discovered several patches by sbruno@ that might address [some of the] issues I'm seeing. Sean (and anyone else, of course), can you give me some hand on the subject? I'm happy to provide any debug info, glad to test patches, etc. Root access to my laptop is also quite possible, shall it be needed. Thanks. ./danfe From owner-freebsd-firewire@FreeBSD.ORG Tue Sep 22 17:10:04 2009 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 914DE106568F for ; Tue, 22 Sep 2009 17:10:04 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id 733A08FC16 for ; Tue, 22 Sep 2009 17:10:04 +0000 (UTC) Received: (qmail 27897 invoked from network); 22 Sep 2009 10:10:02 -0700 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.214?) (69.64.235.60) by iron2.pdx.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 22 Sep 2009 10:10:02 -0700 From: Sean Bruno To: Alexey Dokuchaev In-Reply-To: <20090921201518.GA10574@FreeBSD.org> References: <20090921201518.GA10574@FreeBSD.org> Content-Type: text/plain Date: Tue, 22 Sep 2009 10:10:02 -0700 Message-Id: <1253639402.2621.0.camel@Lappy> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) Content-Transfer-Encoding: 7bit Cc: freebsd-firewire@freebsd.org Subject: Re: FA-101 audio interface support 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, 22 Sep 2009 17:10:04 -0000 My first step would be to try 8/HEAD and see if you get any better results. After that, I'd like to get access to the laptop in question(ssh). Sean On Mon, 2009-09-21 at 20:15 +0000, Alexey Dokuchaev wrote: > fw_rcv: unknown response RRESQ(6) src=0x3f tl=0x19 rt=1 > data=0x6ed42504 From owner-freebsd-firewire@FreeBSD.ORG Sat Sep 26 07:23:34 2009 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 E5566106568F for ; Sat, 26 Sep 2009 07:23:34 +0000 (UTC) (envelope-from sean.bruno@dsl-only.net) Received: from iron2.pdx.net (iron2.pdx.net [69.64.224.71]) by mx1.freebsd.org (Postfix) with ESMTP id A9B1A8FC17 for ; Sat, 26 Sep 2009 07:23:34 +0000 (UTC) Received: (qmail 26784 invoked from network); 26 Sep 2009 00:23:34 -0700 Received: from pooker.samsco.org (HELO ?192.168.254.203?) (168.103.85.57) by iron2.pdx.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 26 Sep 2009 00:23:33 -0700 From: Sean Bruno To: freebsd-firewire@FreeBSD.org Content-Type: text/plain Date: Sat, 26 Sep 2009 00:23:31 -0700 Message-Id: <1253949811.2729.6.camel@Lappy> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 (2.26.3-1.fc11) Content-Transfer-Encoding: 7bit Cc: Wesley Shields , Nathan Whitehorn , Andriy Gapon , Julian Stecklina Subject: FireWire Patch [8/HEAD] 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: Sat, 26 Sep 2009 07:23:35 -0000 Ok folks, some time has passed and I was able to get some wisdom from the CAM folks in Colorado (Thanks Scott, Justin, Warner, Ken). For those of you experiencing boot failures with firewire/sbp enabled in your configuration, please try the following patch and let me see the full boot dmesg. This is an extensive patch that does "stuff" and "things". :-) Mainly, it should behave better at initialization time and play nice with CAM and the scheduler via a config_intrhook. Let me know --> http://consultcsg.com/firewire.diff Sean