From owner-freebsd-firewire@FreeBSD.ORG Mon Jan 25 11:06:59 2010 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 609F610656B0 for ; Mon, 25 Jan 2010 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 4D2BB8FC27 for ; Mon, 25 Jan 2010 11:06:59 +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 o0PB6xDj038744 for ; Mon, 25 Jan 2010 11:06:59 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o0PB6wrB038742 for freebsd-firewire@FreeBSD.org; Mon, 25 Jan 2010 11:06:58 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Jan 2010 11:06:58 GMT Message-Id: <201001251106.o0PB6wrB038742@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, 25 Jan 2010 11:06:59 -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/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 9 problems total. From owner-freebsd-firewire@FreeBSD.ORG Wed Jan 27 05:10:15 2010 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 C7C25106566B; Wed, 27 Jan 2010 05:10:15 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-98-108-131-15.ptldor.fios.verizon.net [98.108.131.15]) by mx1.freebsd.org (Postfix) with ESMTP id 5F7E28FC08; Wed, 27 Jan 2010 05:10:14 +0000 (UTC) Received: by sopwith.solgatos.com (Postfix, from userid 66) id 4ADCDB650; Tue, 26 Jan 2010 21:09:17 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id SAA13144; Tue, 26 Jan 2010 18:56:30 GMT Message-Id: <201001261856.SAA13144@sopwith.solgatos.com> To: freebsd-firewire@freebsd.org, bug-followup@freebsd.org Date: Tue, 26 Jan 2010 10:56:30 PST From: Dieter Cc: Subject: Re: kern/118093: firewire bus reset hogs CPU, causing data to be lost 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: Wed, 27 Jan 2010 05:10:15 -0000 > Looks like the kernel printf takes a *lot* of CPU, and > somehow locks out Ethernet. Looking through man pages working on an unrelated problem, I found: man timed says: Messages printed by the kernel on the system console occur with inter- rupts disabled. This means that the clock stops while they are printing. A machine with many disk or network hardware problems and consequent mes- sages cannot keep good time by itself. Each message typically causes the clock to lose a dozen milliseconds. If a kernel printf disables Ethernet interrupts for 12 milliseconds, that would create the problem. From owner-freebsd-firewire@FreeBSD.ORG Wed Jan 27 05:10:15 2010 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 D3CB8106566C for ; Wed, 27 Jan 2010 05:10:15 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-98-108-131-15.ptldor.fios.verizon.net [98.108.131.15]) by mx1.freebsd.org (Postfix) with ESMTP id 90D8C8FC0A for ; Wed, 27 Jan 2010 05:10:14 +0000 (UTC) Received: by sopwith.solgatos.com (Postfix, from userid 66) id 444B2B64F; Tue, 26 Jan 2010 21:09:17 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id SAA16838; Tue, 26 Jan 2010 18:33:30 GMT Message-Id: <201001261833.SAA16838@sopwith.solgatos.com> To: Kevin Roettger In-reply-to: Your message of "Wed, 20 Jan 2010 10:35:51 +0100." <9755046264163886827980728780868960484-Webmail@me.com> Date: Tue, 26 Jan 2010 10:33:29 PST From: Dieter Cc: freebsd-firewire@freebsd.org Subject: Re: Boot from Firewire (VIA Fire II) 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: Wed, 27 Jan 2010 05:10:16 -0000 In message <9755046264163886827980728780868960484-Webmail@me.com>, Kevin Roettger writes: >> On an unrelated note, are you able to get your >> VT6306 into "non-CYCLEMASTER mode"? > Being not familiar with the CYCLEMASTER mode, I googled around and just tried this: > > saloon# fwcontrol -u 0 -f 0 > send phy_config root_node=0 gap_count=-1 > saloon# fwcontrol -u 0 -r > After those commands, end of dmesg gives me this: > > fwohci0: Initiate bus reset > fwohci0: fwohci_intr_core: BUS reset > fwohci0: fwohci_intr_core: node_id=0x00000000, SelfID Count=2, CYCLEMASTER mode > firewire0: 1 nodes, maxhop <= 0 cable IRM irm(0) (me) > firewire0: bus manager 0 So it isn't just me. Thanks. From owner-freebsd-firewire@FreeBSD.ORG Wed Jan 27 05:20:03 2010 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 32EB4106566C for ; Wed, 27 Jan 2010 05:20:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 211268FC14 for ; Wed, 27 Jan 2010 05:20:03 +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 o0R5K3WZ089341 for ; Wed, 27 Jan 2010 05:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o0R5K2ek089320; Wed, 27 Jan 2010 05:20:02 GMT (envelope-from gnats) Date: Wed, 27 Jan 2010 05:20:02 GMT Message-Id: <201001270520.o0R5K2ek089320@freefall.freebsd.org> To: freebsd-firewire@FreeBSD.org From: Dieter Cc: Subject: Re: kern/118093: firewire bus reset hogs CPU, causing data to be lost X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dieter List-Id: Firewire support in FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Jan 2010 05:20:03 -0000 The following reply was made to PR kern/118093; it has been noted by GNATS. From: Dieter To: freebsd-firewire@freebsd.org, bug-followup@freebsd.org Cc: Subject: Re: kern/118093: firewire bus reset hogs CPU, causing data to be lost Date: Tue, 26 Jan 2010 10:56:30 PST > Looks like the kernel printf takes a *lot* of CPU, and > somehow locks out Ethernet. Looking through man pages working on an unrelated problem, I found: man timed says: Messages printed by the kernel on the system console occur with inter- rupts disabled. This means that the clock stops while they are printing. A machine with many disk or network hardware problems and consequent mes- sages cannot keep good time by itself. Each message typically causes the clock to lose a dozen milliseconds. If a kernel printf disables Ethernet interrupts for 12 milliseconds, that would create the problem. From owner-freebsd-firewire@FreeBSD.ORG Wed Jan 27 10:45:09 2010 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 9FA791065676 for ; Wed, 27 Jan 2010 10:45:09 +0000 (UTC) (envelope-from flymac@mac.com) Received: from asmtpout019.mac.com (asmtpout019.mac.com [17.148.16.94]) by mx1.freebsd.org (Postfix) with ESMTP id 7D1E58FC21 for ; Wed, 27 Jan 2010 10:45:09 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-1 Received: from spool004.mac.com ([10.150.69.54]) by asmtp019.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTP id <0KWW003FLJ6EXM30@asmtp019.mac.com> for freebsd-firewire@freebsd.org; Wed, 27 Jan 2010 02:45:09 -0800 (PST) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-1001270041 Received: from webmail061 ([10.13.128.61]) by spool004.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTP id <0KWW005EPJ75NSC0@spool004.mac.com> for freebsd-firewire@freebsd.org; Wed, 27 Jan 2010 02:45:07 -0800 (PST) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-1001270041 Date: Wed, 27 Jan 2010 11:45:05 +0100 From: Kevin Roettger To: freebsd-firewire@freebsd.org Message-id: <30020756551208869699406666152307139673-Webmail@me.com> In-reply-to: <150037666413973298114868926391845557718-Webmail@me.com> References: <150037666413973298114868926391845557718-Webmail@me.com> Received: from [195.160.149.36] from webmail.me.com with HTTP; Wed, 27 Jan 2010 11:45:05 +0100 Received: from [ 88.221.144.12] from webmail.me.com with HTTP; Wed, 27 Jan 2010 11:45:05 +0100 X-Originating-IP: 195.160.149.36, 88.221.144.12 Subject: Re: Boot from Firewire (VIA Fire II) 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: Wed, 27 Jan 2010 10:45:09 -0000 Hi, Follow-up of my little journey: No luck with FLOSS BIOS for my mainboard. Some exist for similar mainboard but not mine (at least I could not find any). I've tried pretty much everything to boot from that USB stick but since the BIOS (even a fresh update a few days ago) does not support USB HDD but only USB FDD, no way to boot from it that I know of. Last resort, I've tried netbooting via PXE, the idea being to use it as a way to get into the loader, load whatever Firewire modules and then select that drive to boot from. Ideally I can shutdown the NFS access afterwards to run only from that Firewire drive. So, I've managed to boot and get into the loader, which is a good start. But of course "lsdev" will not show my Firewire drive no matter what modules I load: I've tried "load firewire", "load sbp" and so on... Just a note, if I continue booting from NFS, everything works fine and the drive is recognized as sbp device without any intervention, so there is definitly support for it in the kernel and/or modules found on the NFS boot kernel (I used the 8.0-REL Bootonly image to boot from). Any ideas? Is it even possible to do what I'd like to do? Kevin