From rationalize at vogelhuis.info Thu Sep 3 04:35:42 2009 From: rationalize at vogelhuis.info (Murdy Weast) Date: Thu Sep 3 04:35:49 2009 Subject: D be made to offset them. The South therefore had been anxious to hav Message-ID: <4A9F46EB.2040301@lephoenix.com> the pride of Clary's Grove in his arms like a child, and holding him high in the air, almost choked the life out of him. It seemed for a moment as though a general fight must follow; but even while Lincoln's fierce rage compelled their respect, his quickly returning self-control won their admiration, and the crisis was safely passed. Instead of becoming enemies and leaders in a neighborhood feud, as might have been expected, the two grew to be warm friends, the affection thus strangely begun lasting through life. They proved useful to each other in various ways, and years afterward Lincoln made ample amends for his rough treatment of the other's throat by saving the neck of Jack Armstrong's son from the halter in a memorable trial for murder. The Clary's Grove "boys" voted Lincoln "the cleverest fellow that had ever broke into the settlement," and thereafter took as much pride in his peaceableness and book-learning as they did in the rougher and more questionable accomplishments of their discomfited leader. Lincoln himself was not so easily satisfied. His mind as well as his muscles hungered for work, and he confided to Mentor Graham, possibly with some diffidence, his "notion to study English grammar." Instead of laughing at him, Graham heartily encouraged the idea, saying it was the very best thing he could do. With quickened zeal Lincoln announced that if he had a grammar he would begin at once at this the schoolmaster was obliged to confess that he knew of no such book in New Salem. He thought, however, that there might be one at Vaner's, six miles away. Promptly after breakfast the next morning Lincoln set out in search of it. He brought the precious volume home in triumph, and with Graham's occasional help found no difficulty in mastering its contents. Indeed, it is very likely that he was astonished, and even a bit disappointed, to find so little mystery in it. He is reported to have said that if this was a "science," he thought he would like to begin on another one. In the eyes of the townspeople, however, it was no small achievement, and added greatly to his reputation as a scholar. There is no record of any other study commenced at this time, but it is certain that he profited much by helpful talks with Mentor Graham, and that he borrowed every book the schoolmaster's scanty library was able to furnish. Though outw From Gabor at Zahemszky.HU Thu Sep 3 19:25:12 2009 From: Gabor at Zahemszky.HU (Zahemszky =?ISO-8859-2?Q?G=E1bor?=) Date: Thu Sep 3 19:25:22 2009 Subject: connecting FreeBSD 7 to a DVD-recorder on FW Message-ID: <20090903204250.765c7bca@Picasso.Zahemszky.HU> Hi! I've got some DV files (grabbed from a Pana-camera, with iMovie - from iLife - on a Mac). In my laptop I have an PCMCIA based FW-card, so I'd like to transfer these files to my DVD-recorder's disk, which has DV-IN connector on it. I connected my machine with a DV-cable to my recorder, set up the recorder to use the DV connector as a source, and tried the "fwcontrol -S myfile.dv" command. fwcontrol printed numbers 1234... and so on, and after about a minute, (it was the length of the DV-file) it stopped. But the dvd-recorder didn't see any data on the DV-IN line. So after it, I tried fwcontrol -r, fwcontrol -t, tried to ask the configuration with -c 0, -c 1, but it wasn't good. So some questions: - what does the information mean in an "fwcontrol -t" output? Eg, like this one in the laptop: nothing plugged in it: crc_len: 3 generation:3 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 -1W - - 1 0 plugged the cable into one of the ports: crc_len: 4 generation:9 node_count:2 sid_count:2 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 5 S100 0 1 0W - P 0 0 01 1 5 S400 0 1 -1W - C 1 0 When I plugged the cable on the other connector of my FW-card, the C went from port1 to port0: crc_len: 4 generation:14 node_count:2 sid_count:2 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 5 S100 0 1 0W - P 0 0 01 1 5 S400 0 1 -1W C - 1 0 And this one is from my other machine, with a built-in FW-controller, with only one connector, and without a cable plugged in it: crc_len: 3 generation:2 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 -1W - - 1 0 So what do these pieces of information mean? What are node names - I need them to the -c or -d, or to some other options? Where can I see them? How can I know, that my machine sees the DVD-recorder on the link, or what can I do, if it doesn't see? Thanks, G?bor < Gabor at Zahemszky dot HU > -- #!/bin/ksh Z='21N16I25C25E30, 40M30E33E25T15U!'; IFS=' ABCDEFGHIJKLMNOPQRSTUVWXYZ '; set -- $Z;for i;{ [[ $i = ? ]]&&print $i&&break; [[ $i = ??? ]]&&j=$i&&i=${i%?}; typeset -i40 i=8#$i;print -n ${i#???}; [[ "$j" = ??? ]]&&print -n "${j#??} "&&j=;typeset +i i;}; IFS=' 0123456789 ';set -- $Z;for i;{ [[ $i = , ]]&&i=2; [[ $i = ?? ]]||typeset -l i;j="$j $i";typeset +l i;};print "$j" From sean.bruno at dsl-only.net Thu Sep 3 22:50:38 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Thu Sep 3 22:50:45 2009 Subject: connecting FreeBSD 7 to a DVD-recorder on FW In-Reply-To: <20090903204250.765c7bca@Picasso.Zahemszky.HU> References: <20090903204250.765c7bca@Picasso.Zahemszky.HU> Message-ID: <1252018236.2779.9.camel@Lappy> On Thu, 2009-09-03 at 20:42 +0200, Zahemszky G?bor wrote: > Hi! > > I've got some DV files (grabbed from a Pana-camera, with iMovie - from > iLife - on a Mac). In my laptop I have an PCMCIA based FW-card, so > I'd like to transfer these files to my DVD-recorder's disk, which has > DV-IN connector on it. I connected my machine with a DV-cable to my > recorder, set up the recorder to use the DV connector as a source, and > tried the "fwcontrol -S myfile.dv" command. fwcontrol printed numbers > 1234... and so on, and after about a minute, (it was the length of the > DV-file) it stopped. But the dvd-recorder didn't see any data on the > DV-IN line. Can you point me to the model/make of the DVD recorder? It looks like you connected your DVD recorder to your FreeBSD machine. If that is the case, can you check your system dmesg when you plug in the DVD recorder? > So after it, I tried fwcontrol -r, fwcontrol -t, tried to ask the > configuration with -c 0, -c 1, but it wasn't good. So some questions: > > - what does the information mean in an "fwcontrol -t" output? Eg, like fwcontrol -t is the "topology map" it lists information about speeds(S400/S800), connections and IDs. The man page for fwcontrol explains a lot of this. > When I plugged the cable on the other connector of my FW-card, the C > went from port1 to port0: > > crc_len: 4 generation:14 node_count:2 sid_count:2 > id link gap_cnt speed delay cIRM power port0 port1 port2 ini more > 00 1 5 S100 0 1 0W - P 0 0 > 01 1 5 S400 0 1 -1W C - 1 0 > > And this one is from my other machine, with a built-in FW-controller, > with only one connector, and without a cable plugged in it: > > crc_len: 3 generation:2 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 -1W - - 1 0 > > So what do these pieces of information mean? This is showing the connection status of the various FW ports and how things are connected. > What are node names - I need them to the -c or -d, or to some other > options? Where can I see them? The node "name" is the "id" field from fwcontrol -t. It's a number, like 0, 1 or 2 > How can I know, that my machine sees the DVD-recorder on the link, or > what can I do, if it doesn't see? I am worried about the "speed" of the unit that shows up as "S100". That's the minimum speed, and with modern FW components usually means that something failed in negotiation. I know of one bug (fixed in version > 8.0) that will show up IF an S800 capable device is connected to a S400 device via one of it's S800 ports. If you can connect both ends to S400 ports, it would work around that problem. Sean From bugmaster at FreeBSD.org Mon Sep 7 11:06:58 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 7 11:07:47 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200909071106.n87B6vB4010196@freefall.freebsd.org> 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 Gabor at Zahemszky.HU Mon Sep 14 08:20:38 2009 From: Gabor at Zahemszky.HU (Zahemszky =?ISO-8859-2?Q?G=E1bor?=) Date: Mon Sep 14 08:20:45 2009 Subject: connecting FreeBSD 7 to a DVD-recorder on FW In-Reply-To: <1252018236.2779.9.camel@Lappy> References: <20090903204250.765c7bca@Picasso.Zahemszky.HU> <1252018236.2779.9.camel@Lappy> Message-ID: <20090914102035.4da8d30c@Picasso.Zahemszky.HU> Hi! Thanks for your answer. Thu, 03 Sep 2009 15:50:36 -0700 -n Sean Bruno ?rta: > On Thu, 2009-09-03 at 20:42 +0200, Zahemszky G?bor wrote: > > Hi! > > > > I've got some DV files (grabbed from a Pana-camera, with iMovie - > > from iLife - on a Mac). In my laptop I have an PCMCIA based > > FW-card, so I'd like to transfer these files to my DVD-recorder's > > disk, which has DV-IN connector on it. I connected my machine with > > a DV-cable to my recorder, set up the recorder to use the DV > > connector as a source, and tried the "fwcontrol -S myfile.dv" > > command. fwcontrol printed numbers 1234... and so on, and after > > about a minute, (it was the length of the DV-file) it stopped. But > > the dvd-recorder didn't see any data on the DV-IN line. > > Can you point me to the model/make of the DVD recorder? It's a German, UMax-build "Yamada DVR-9300HX HDD and DVD-recorder" machine. > It looks like > you connected your DVD recorder to your FreeBSD machine. If that is > the case, can you check your system dmesg when you plug in the DVD > recorder? Here you are. I plugged my PCMCIA FW-card, connected the cable, switched on the DVR, switched off and switched on again. === drm0: [ITHREAD] cardbus0: Expecting link target, got 0xff fwohci0: mem 0xe4205000-0xe4205fff,0xe4206000-0xe42060ff,0xe4207000-0xe42070ff irq 18 at device 0.0 on cardbus0 fwohci0: [FILTER] fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:00:00:00:00:00:00:00 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:00:00:00:00:00 fwe0: Ethernet address: 02:00:00:00:00:00 fwip0: on firewire0 fwip0: Firewire address: 00:00:00:00:00:00:00:00 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x7db04000 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) cardbus0: Expecting link target, got 0xff fwohci0: BUS reset fwohci0: node_id=0xc000ffc1, gen=2, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) fwohci0: BUS reset fwohci0: node_id=0x8000ffc0, gen=3, non CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 fwohci0: BUS reset fwohci0: node_id=0xc000ffc1, gen=4, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=0xffc0 data=1d051284 firewire0: New S100 device ID:000e3a0000000000 fwohci0: BUS reset fwohci0: node_id=0xc000ffc1, gen=5, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=0xffc0 data=af141284 fwohci0: BUS reset fwohci0: node_id=0xc000ffc1, gen=6, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=0xffc0 data=25201284 bge0: link state changed to UP cpu0: Cx states changed fwohci0: BUS reset fwohci0: node_id=0xc000ffc0, gen=7, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) acpi_tz0: _CRT value is absurd, ignored (256.0C) acpi_tz0: _CRT value is absurd, ignored (256.0C) fwohci0: BUS reset fwohci0: node_id=0x8000ffc0, gen=8, 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: BUS reset fwohci0: node_id=0xc000ffc1, gen=9, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) fwohci0: BUS reset fwohci0: node_id=0xc000ffc1, gen=10, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=0xffc0 data=63c41284 fwohci0: BUS reset fwohci0: node_id=0xc000ffc1, gen=11, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=0xffc0 data=f6d31284 fwohci0: BUS reset fwohci0: node_id=0xc000ffc1, gen=12, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=0xffc0 data=acde1284 acpi_tz0: _CRT value is absurd, ignored (256.0C) fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc000ffc1, gen=13, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) Unknown service addr 0xffff:0xf0000900 RREQQ(4) src=0xffc0 data=bf201284 acpi_tz0: _CRT value is absurd, ignored (256.0C) === And the output of fwcontrol -r -t: $ fwcontrol -r -t crc_len: 4 generation:17 node_count:2 sid_count:2 id link gap_cnt speed delay cIRM power port0 port1 port2 ini more 00 1 5 S100 0 1 0W - P 0 0 01 1 5 S400 0 1 -1W C - 1 0 $ === > > - what does the information mean in an "fwcontrol -t" output? Eg, > > like > > fwcontrol -t is the "topology map" it lists information about > speeds(S400/S800), connections and IDs. The man page for fwcontrol > explains a lot of this. I have this information about it (a 7.X-machine with csup-ped and built yesterday): -t Show the topology map. And no other information. So I don't know, what the flags C or P in the port-column means, and I didn't know (now, I know it), that the ID (with 2 numbers) are the same, that the node. It's OK. But: > The node "name" is the "id" field from fwcontrol -t. It's a number, > like 0, 1 or 2 My problem is: after the previous fwcontrol output (which showed me, that I have a node with ID: 00 and another node with ID: 01, I cannot ask anything from these nodes: # fwcontrol -n 0 fwcontrol: no such node 0. # fwcontrol -c 1 fwcontrol: no such node 1. # fwcontrol -c 00 fwcontrol: no such node 0. # fwcontrol -c 01 fwcontrol: no such node 1. ???? > I am worried about the "speed" of the unit that shows up as "S100". > That's the minimum speed, and with modern FW components usually means > that something failed in negotiation. Can I switch on some debugging (only) about the FW? > I know of one bug (fixed in version > 8.0) that will show up IF an (I hope, I can switch to 8.0 in one ot two month.) > S800 capable device is connected to a S400 device via one of it's > S800 ports. If you can connect both ends to S400 ports, it would work > around that problem. I don't think, this is my problem, as tt (the DVR) has only one FW-connector port. (I didn't find any information about it's HW - is it an S400- or an S800-capable machine.) Thanks, Zahy < Gabor at Zahemszky dot HU > -- #!/bin/ksh Z='21N16I25C25E30, 40M30E33E25T15U!'; IFS=' ABCDEFGHIJKLMNOPQRSTUVWXYZ '; set -- $Z;for i;{ [[ $i = ? ]]&&print $i&&break; [[ $i = ??? ]]&&j=$i&&i=${i%?}; typeset -i40 i=8#$i;print -n ${i#???}; [[ "$j" = ??? ]]&&print -n "${j#??} "&&j=;typeset +i i;}; IFS=' 0123456789 ';set -- $Z;for i;{ [[ $i = , ]]&&i=2; [[ $i = ?? ]]||typeset -l i;j="$j $i";typeset +l i;};print "$j" From bugmaster at FreeBSD.org Mon Sep 14 11:06:58 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 14 11:07:54 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200909141106.n8EB6vlJ072297@freefall.freebsd.org> 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 bugmaster at FreeBSD.org Mon Sep 21 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 21 11:07:57 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200909211106.n8LB6rge030218@freefall.freebsd.org> 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 danfe at FreeBSD.org Mon Sep 21 20:15:19 2009 From: danfe at FreeBSD.org (Alexey Dokuchaev) Date: Mon Sep 21 20:15:25 2009 Subject: FA-101 audio interface support Message-ID: <20090921201518.GA10574@FreeBSD.org> 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 sean.bruno at dsl-only.net Tue Sep 22 17:10:04 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Tue Sep 22 17:10:15 2009 Subject: FA-101 audio interface support In-Reply-To: <20090921201518.GA10574@FreeBSD.org> References: <20090921201518.GA10574@FreeBSD.org> Message-ID: <1253639402.2621.0.camel@Lappy> 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 sean.bruno at dsl-only.net Sat Sep 26 07:23:35 2009 From: sean.bruno at dsl-only.net (Sean Bruno) Date: Sat Sep 26 07:23:41 2009 Subject: FireWire Patch [8/HEAD] Message-ID: <1253949811.2729.6.camel@Lappy> 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 From areilly at bigpond.net.au Sun Sep 27 06:50:03 2009 From: areilly at bigpond.net.au (Andrew Reilly) Date: Sun Sep 27 06:50:09 2009 Subject: kern/136652: [firewire] Firewire-attached "WD My Book 1028" does not mount at boot but is OK if connected after boot. Message-ID: <200909270650.n8R6o2sl041435@freefall.freebsd.org> The following reply was made to PR kern/136652; it has been noted by GNATS. From: Andrew Reilly To: bug-followup@FreeBSD.org, areilly@bigpond.net.au Cc: Subject: Re: kern/136652: [firewire] Firewire-attached "WD My Book 1028" does not mount at boot but is OK if connected after boot. Date: Sun, 27 Sep 2009 15:27:19 +1000 As of this weekend, I've had two consecutive boots that ran all the way through to multi-user, unassisted. Thanks guys! I suspect that this PR can be closed... Cheers, -- Andrew From bugmaster at FreeBSD.org Mon Sep 28 11:06:53 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Sep 28 11:07:52 2009 Subject: Current problem reports assigned to freebsd-firewire@FreeBSD.org Message-ID: <200909281106.n8SB6q0E063976@freefall.freebsd.org> 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 js at alien8.de Tue Sep 29 13:38:02 2009 From: js at alien8.de (Julian Stecklina) Date: Tue Sep 29 13:38:09 2009 Subject: FireWire Patch [8/HEAD] References: <1253949811.2729.6.camel@Lappy> Message-ID: <87iqf1dg7n.fsf@tabernacle.localhost> Sean Bruno writes: > 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 The box that exhibits the problem is currently repurposed for other tasks. So I cannot test this at the moment. If no one else steps up to test this, I can test it in a week or so. Regards, -- Julian Stecklina The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners - Ernst Jan Plugge From sbruno at FreeBSD.org Tue Sep 29 17:34:47 2009 From: sbruno at FreeBSD.org (sbruno@FreeBSD.org) Date: Tue Sep 29 17:34:54 2009 Subject: kern/136652: [firewire] Firewire-attached "WD My Book 1028" does not mount at boot but is OK if connected after boot. Message-ID: <200909291734.n8THYlUm095416@freefall.freebsd.org> Synopsis: [firewire] Firewire-attached "WD My Book 1028" does not mount at boot but is OK if connected after boot. State-Changed-From-To: open->closed State-Changed-By: sbruno State-Changed-When: Tue Sep 29 17:33:17 UTC 2009 State-Changed-Why: User reports problem has cleared. http://www.freebsd.org/cgi/query-pr.cgi?pr=136652