From owner-freebsd-firewire@FreeBSD.ORG Mon Jan 7 11:06:59 2008 Return-Path: Delivered-To: freebsd-firewire@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1A37B16A479 for ; Mon, 7 Jan 2008 11:06:59 +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 E8FEA13C442 for ; Mon, 7 Jan 2008 11:06:58 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m07B6wOc061750 for ; Mon, 7 Jan 2008 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m07B6w7h061746 for freebsd-firewire@FreeBSD.org; Mon, 7 Jan 2008 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 7 Jan 2008 11:06:58 GMT Message-Id: <200801071106.m07B6w7h061746@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, 07 Jan 2008 11:06:59 -0000 Current FreeBSD problem reports Critical problems Serious problems S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/74238 firewire [firewire] fw_rcv: unknown response; firewire ad-hoc w 1 problem total. Non-critical problems S Tracker Resp. Description -------------------------------------------------------------------------------- f kern/113785 firewire [firewire] dropouts when playing DV on firewire 1 problem total. From owner-freebsd-firewire@FreeBSD.ORG Tue Jan 8 09:24:28 2008 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 B8A8216A417 for ; Tue, 8 Jan 2008 09:24:28 +0000 (UTC) (envelope-from heliocentric@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id 880EF13C458 for ; Tue, 8 Jan 2008 09:24:28 +0000 (UTC) (envelope-from heliocentric@gmail.com) Received: by py-out-1112.google.com with SMTP id u52so13094949pyb.10 for ; Tue, 08 Jan 2008 01:24:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; bh=MbnYS72YB5yuQPFHiX0lzaHD6TkdcjMKuAKBrrMcQKg=; b=RxHb//lRzk/v2pZLOecSzdR5YdCx3eysGPuXzR/bmRAPzFFgU7h1whFzxgP90zx+AmJoJP/sjoR/b+5/xbkwLTjG77IpAm9krs2oFIRl/oXbNo71E1LhF2nWgjUHAJTAjpi+1ztWOircM6iZY8XY0MmHfSg0BIBLO0ZMsRvgpf8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth; b=s+gh4F2Aj/BAk9BhyIX7dJtiIh2STotib8V85UY4j1QCw2eLJ431hlt2FIWA3bfBdeCHin4XjI7AQLRdPugTranksOdpmZMfd1YnLkkRER8e1e0c9X1BpGSBRqod4bGVZaa0endKZl42671EQKzOCXTThLZ/jZgQF25X1auPbY8= Received: by 10.142.88.20 with SMTP id l20mr46712wfb.72.1199782531279; Tue, 08 Jan 2008 00:55:31 -0800 (PST) Received: by 10.142.11.9 with HTTP; Tue, 8 Jan 2008 00:55:31 -0800 (PST) Message-ID: Date: Tue, 8 Jan 2008 03:55:31 -0500 From: "Dylan Cochran" Sender: heliocentric@gmail.com To: freebsd-firewire@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: 63254be564d18175 Subject: Multiple dcons writers 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, 08 Jan 2008 09:24:28 -0000 I've looked in the man page, and haven't found any information regarding multiple writers across the bus to dcons; I'm pretty sure it wouldn't work, but I'm not sure of the behavior defined for that scenario. Would both writers write to the same address given by the configuration rom, and stomp on each other, leaving a mess, or would it be serialized by the firewire card in some way? Or would an error be passed up to dconschat? From owner-freebsd-firewire@FreeBSD.ORG Thu Jan 10 08:17:37 2008 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 D243216A419 for ; Thu, 10 Jan 2008 08:17:37 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from plato.miralink.com (mail.miralink.com [70.103.185.20]) by mx1.freebsd.org (Postfix) with ESMTP id 86F9E13C442 for ; Thu, 10 Jan 2008 08:17:37 +0000 (UTC) (envelope-from sbruno@miralink.com) Received: from localhost (localhost.localdomain [127.0.0.1]) by plato.miralink.com (Postfix) with ESMTP id 69ED61C8038 for ; Thu, 10 Jan 2008 00:17:37 -0800 (PST) Received: from plato.miralink.com ([127.0.0.1]) by localhost (plato.miralink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29176-10 for ; Thu, 10 Jan 2008 00:17:35 -0800 (PST) Received: from [10.47.1.226] (vpn.office.miralink.com [10.0.0.5]) by plato.miralink.com (Postfix) with ESMTP id A84BC1C8037 for ; Thu, 10 Jan 2008 00:17:35 -0800 (PST) Message-ID: <4785D49F.9040701@miralink.com> Date: Thu, 10 Jan 2008 00:17:35 -0800 From: Sean Bruno User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: freebsd-firewire@freebsd.org References: <47716073.1050701@miralink.com> In-Reply-To: <47716073.1050701@miralink.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Thu Jan 10 00:17:37 2008 X-DSPAM-Confidence: 0.9997 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4785d4a176052362839998 X-DSPAM-Factors: 27, X-Virus-Scanned: amavisd-new at X-Spam-Status: No, score=-4.499 tagged_above=-10 required=6.6 autolearn=ham tests=[ALL_TRUSTED=-1.8, BAYES_00=-2.599, DSPAM_HAM=-0.1] X-Spam-Score: -4.499 X-Spam-Level: Subject: Re: Accessing a Macbook in TargetMode 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: Thu, 10 Jan 2008 08:17:37 -0000 Sean Bruno wrote: > I placed a shiny new MacBook into Firewire target mode while connected > to my RELENG_6_2 box and was suprised to see that FreeBSD can't really > access the disk via sbp(). I'm fairly certain that we don't have > access to the filesystem under FreeBSD(Apple is hfs?). > > Anyone else care to give this a try and report please? > Does any firewire disk work with FreeBSD? Hmmm...not much going on with a MacBook. Here's a little log trace from sbp with debug = 1. source # ls -la /dev/da* crw-r----- 1 root operator 0, 94 Jan 10 11:24 /dev/da0 source # fdisk /dev/da0 sbp0:0:0 ORB status src:1 resp:0 dead:1 len:2 stat:0 orb:0002ce634 sbp0:0:0 No additional information to report sbp0:0:0 XPT_SCSI_IO: cmd: 25 00 00 00 00 00 00 00 00 00, flags: 0x40, 10b cmd/8b data/32b sense sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 2 code 3a qlfr 0 len 2 sbp0:0:0 sbp_agent_reset (da0:sbp0:0:0:0): error 6 (da0:sbp0:0:0:0): Unretryable Error Opened disk da0 -> 6 fdisk: cannot open disk /dev/da0: Device not configured source # fwohci0: BUS reset sbp_post_busreset fwohci0: node_id=0xc800ffc0, gen=5, CYCLEMASTER mode firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me) firewire0: bus manager 0 (me) sbp_post_explore (sbp_cold=0) sbp_post_explore: EUI:001d4ffffe78600c not attached, state=3. target 0 lun 0 found target 0 lun 0 found sbp0:0:0 lost target fwohci0: BUS reset sbp_post_busreset fwohci0: node_id=0x8800ffc0, gen=6, 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? sbp_post_explore (sbp_cold=0) sbp_post_explore: EUI:001d4ffffe78600c attached target 0 lun 0 found target 0 lun 0 found sbp0:0:0 ordered:0 type:14 EUI:001d4ffffe78600c node:1 speed:2 maxrec:0 sbp0:0:0 'AAPL' '' '' sbp0:0:0 RECONNECT sbp0:0:0 mgm orb: 002ce76c sbp0:0:0 reconnect failed sbp_login: sec = 0 usec = 679651 ticks = 679 sbp0:0:0 LOGIN sbp0:0:0 mgm orb: 002ce8a4 sbp0:0:0 login: len 16, ID 1, cmd 0000fffff0ef1020, recon_hold 0 sbp0:0:0 sbp_busy_timeout sbp0:0:0 sbp_agent_reset sbp0:0:0 sbp_do_attach sbp0:0:0 sbp_cam_scan_target sbp0:0:0 ORB status src:1 resp:0 dead:1 len:2 stat:0 orb:0002ce9dc sbp0:0:0 No additional information to report sbp0:0:0 XPT_SCSI_IO: cmd: 00 00 00 00 00 00 00 00 00 00, flags: 0xc0, 6b cmd/0b data/32b sense sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 2 code 3a qlfr 0 len 2 sbp0:0:0 sbp_agent_reset (probe0:sbp0:0:0:0): error 6 (probe0:sbp0:0:0:0): Unretryable Error sbp0:0:0 ORB status src:1 resp:0 dead:1 len:2 stat:0 orb:0002ced84 sbp0:0:0 No additional information to report sbp0:0:0 XPT_SCSI_IO: cmd: 12 01 80 00 ff 00 00 00 00 00, flags: 0x40, 6b cmd/255b data/18b sense sbp0:0:0 SCSI status 2 sfmt 0 valid 0 key 5 code 24 qlfr 0 len 2 sbp0:0:0 sbp_agent_reset (probe0:sbp0:0:0:0): error 22 (probe0:sbp0:0:0:0): Unretryable Error sbp0:0:0 sbp_cam_scan_lun Sean From owner-freebsd-firewire@FreeBSD.ORG Thu Jan 10 13:23:48 2008 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 312BC16A419 for ; Thu, 10 Jan 2008 13:23:48 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.225]) by mx1.freebsd.org (Postfix) with ESMTP id B181913C4F3 for ; Thu, 10 Jan 2008 13:23:47 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: by wx-out-0506.google.com with SMTP id i29so383775wxd.7 for ; Thu, 10 Jan 2008 05:23:46 -0800 (PST) Received: by 10.142.203.13 with SMTP id a13mr910006wfg.210.1199971425812; Thu, 10 Jan 2008 05:23:45 -0800 (PST) Received: by 10.142.224.12 with HTTP; Thu, 10 Jan 2008 05:23:45 -0800 (PST) Message-ID: <626eb4530801100523v16cbe40ave11033c6074536c5@mail.gmail.com> Date: Thu, 10 Jan 2008 22:23:45 +0900 From: "Hidetoshi Shimokawa" Sender: freebsd@gm.nunu.org To: "Dylan Cochran" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: b889e48fa75e1973 Cc: freebsd-firewire@freebsd.org Subject: Re: Multiple dcons writers 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: Thu, 10 Jan 2008 13:23:48 -0000 It is unpredictable if multiple dconschat write to dcons buffer at the same time because there is no serialization on updating the current pointer of input buffer. The pointer is not on the configuration rom but on the dcons buffer. (see dcons.h) Since dconschat polls the pointer, multiple writers work as expected for usual interactive use. On Jan 8, 2008 5:55 PM, Dylan Cochran wrote: > I've looked in the man page, and haven't found any information > regarding multiple writers across the bus to dcons; I'm pretty sure it > wouldn't work, but I'm not sure of the behavior defined for that > scenario. Would both writers write to the same address given by the > configuration rom, and stomp on each other, leaving a mess, or would > it be serialized by the firewire card in some way? Or would an error > be passed up to dconschat? > _______________________________________________ > freebsd-firewire@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-firewire > To unsubscribe, send any mail to "freebsd-firewire-unsubscribe@freebsd.org" > > -- /\ Hidetoshi Shimokawa \/ simokawa@FreeBSD.ORG From owner-freebsd-firewire@FreeBSD.ORG Thu Jan 10 20:15:08 2008 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 2A3CB16A421 for ; Thu, 10 Jan 2008 20:15:08 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (pool-96-225-216-68.ptldor.fios.verizon.net [96.225.216.68]) by mx1.freebsd.org (Postfix) with ESMTP id EFF1213C442 for ; Thu, 10 Jan 2008 20:15:07 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from schitzo.solgatos.com (localhost.home.localnet [127.0.0.1]) by schitzo.solgatos.com (8.14.1/8.13.8) with ESMTP id m0AJfDgR012204 for ; Thu, 10 Jan 2008 11:41:13 -0800 Received: from sopwith.solgatos.com (uucp@localhost) by schitzo.solgatos.com (8.14.1/8.13.4/Submit) with UUCP id m0AJfDSc012201 for freebsd-firewire@freebsd.org; Thu, 10 Jan 2008 11:41:13 -0800 Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id TAA05489; Thu, 10 Jan 2008 19:39:00 GMT Message-Id: <200801101939.TAA05489@sopwith.solgatos.com> To: freebsd-firewire@freebsd.org Date: Thu, 10 Jan 2008 11:39:00 +0000 From: Dieter Subject: Can I force "non CYCLEMASTER mode" ? 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: Thu, 10 Jan 2008 20:15:08 -0000 Re: kern/113785 Could "CYCLEMASTER mode" vs. "non CYCLEMASTER mode" be the source of my firewire problems? Is it possible to force FreeBSD to be in "non CYCLEMASTER mode" ? Thanks. ------- Forwarded Message > > There is no initialization packet to send streams; > > By initialization, I meant whatever conversation FreeBSD and the > camcorder have once they are both up. > > > however, > > it might be a problem who is the cycle/bus/IR manager. > > Can you see some difference of the output of the fwcontrol(8) and demsg(8) > > in node-id, cycle master and etc. between success and failed cases? > > Yes, we have a couple of new clues: > > When FreeBSD says "CYCLEMASTER mode" it does not work. > When FreeBSD says "non CYCLEMASTER mode" it works. > > Also: > > The controller that works (if booted in correct order): > > just bsd: > # fwcontrol -u 1 -t > 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 -9W - - 1 0 > > now power up camcorder (does not work): > > # fwcontrol -u 1 -t > crc_len: 4 generation:3 node_count:2 sid_count:2 > id link gap_cnt speed delay cIRM power port0 port1 port2 ini more > 00 1 63 S100 0 1 0W - P 1 0 > 01 1 5 S400 0 1 -9W - C 0 0 > > Looks like the S400 & non-zero power device (BSD box) changed id from 00 to 01? > > after booting camcorder and FreeBSD in correct order (works): > > # fwcontrol -u 1 -t > crc_len: 4 generation:1 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 -9W - P 1 0 > 01 1 63 S100 0 1 0W - C 0 0 > > Note that the BSD box is id 00. > > The controller that never works: > > # fwcontrol -u 0 -t > crc_len: 4 generation:2 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 15W C - 1 0 > > The BSD box is id 01. > Perhaps the "C" showing up under port0 instead of port1 is significant? > > So: if the BSD box is id 00, camcorder is id 01 -> works > if the BSD box is id 01, camcorder is id 00 -> does not work > > > Thanks for a fix for the compiler warning. > > You're welcome. ------- End of Forwarded Message