From owner-freebsd-firewire@FreeBSD.ORG Sun Jan 10 18:28:40 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 686C3106568B for ; Sun, 10 Jan 2010 18:28:40 +0000 (UTC) (envelope-from ka@flu.if0.org) Received: from flu.if0.org (v112022.ppp.asahi-net.or.jp [124.155.112.22]) by mx1.freebsd.org (Postfix) with ESMTP id 0C8A98FC0C for ; Sun, 10 Jan 2010 18:28:38 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by flu.if0.org (8.14.3/8.14.3) with ESMTP id o0AISPHc019501 for ; Mon, 11 Jan 2010 03:28:31 +0900 (JST) (envelope-from ka@flu.if0.org) Date: Mon, 11 Jan 2010 03:28:24 +0900 (JST) Message-Id: <20100111.032824.208936614.ka@flu.if0.org> To: freebsd-firewire@freebsd.org From: Kazumaro Aoki In-Reply-To: <1262639782.2209.305.camel@home-lappy> References: <20091228.001440.71123742.ka@flu.if0.org> <20100104.190107.74684647.ka@flu.if0.org> <1262639782.2209.305.camel@home-lappy> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: reset with fwcontrol -R 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: Sun, 10 Jan 2010 18:28:40 -0000 From: Sean Bruno Subject: Re: reset with fwcontrol -R Date: Mon, 04 Jan 2010 13:16:22 -0800 >> > I have several experiences that sudden reboot is happened just after >> > "fwcontrol -R foo.dv" was invoked. The operating system is FreeBSD >> > 7.2R/i386. Before I use 7.2R, I used 6.3R and I never experienced >> > such phenomenon. >> >> At December 27, I met the similar problem. The system caused a panic. (snip) > I'm not clear what is going on from the attached information. I have > been looking around to see what could have changed to affect these > problems. Thank you for considering my problem. > Can you try setting the firewire debug to 3 and testing? > sysctl debug.firewire_debug=3 Yes. I changed the value described above and I observed the system behavior. The OS hardly panics, but I finally got the panic. I copied the log message from messages without date and system name: start IR DMA 0x40000011 Fatal trap 12: page fault while in kern el mode cpuid = 0; apic id = 00 fault vi rtual addres s = 0x22 fault code = supervisor read, page not presen t instruction pointer = 0x20:0xc05f6d8 a stack poin ter = 0x28: 0xe5c3 8c2c fra me poi nter = 0x28 :0xe5c 38c9c code seg ment = base 0x0, limit 0x fffff, type 0x1b = D PL 0, pres 1, def32 1, gran 1 processor eflags = interrup t enab led, r esume, IOPL = 0 curr ent pr ocess = 42 (fw0_t askq) trap numbe kernel boot file is /boot/kernel/kernel I feel that no helpful information is logged. The panic was occurred January 7. After this, I did not meet a panic. At that time, I did not make a crash dump. When the panic happens next time, I can get a crash dump. I used fwcontrol -R about 17 times per day. Ah, I forgot to mention the following fact. When I used without -M dv option, fwcontrol -R outputs: fwcontrol: detect_recv_fn: ioctl FW_SSTBUF: Bad file descriptor So, I used fwcontrol implementation in FreeBSD 6.3R. Moreover, when I am using fwcontrol -R, I cannot use "fwcontrol" with no option. When I used FreeBSD6.3R, I can see the result from fwcontrol, because fwcontrol outputs: fwcontrol: main: Error opening firewire controller #0 /dev/fw0.0: Device busy That is the another reason why I use fwcontrol implemented in FreeBSD 6.3R, though the operating system is FreeBSD7.2R. Best regards, Kazumaro From owner-freebsd-firewire@FreeBSD.ORG Sun Jan 10 19:47:26 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 C55F41065695 for ; Sun, 10 Jan 2010 19:47:26 +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 A21058FC18 for ; Sun, 10 Jan 2010 19:47:26 +0000 (UTC) Received: (qmail 13302 invoked from network); 10 Jan 2010 11:47:24 -0800 Received: from ip67-88-206-98.z206-88-67.customer.algx.net (HELO ?172.20.21.37?) (67.88.206.98) by iron2.pdx.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 10 Jan 2010 11:47:22 -0800 From: Sean Bruno To: Kazumaro Aoki In-Reply-To: <20100111.032824.208936614.ka@flu.if0.org> References: <20091228.001440.71123742.ka@flu.if0.org> <20100104.190107.74684647.ka@flu.if0.org> <1262639782.2209.305.camel@home-lappy> <20100111.032824.208936614.ka@flu.if0.org> Content-Type: text/plain; charset="UTF-8" Date: Sun, 10 Jan 2010 11:47:18 -0800 Message-ID: <1263152838.8632.48.camel@home-lappy> Mime-Version: 1.0 X-Mailer: Evolution 2.28.2 (2.28.2-1.fc12) Content-Transfer-Encoding: 7bit Cc: freebsd-firewire@freebsd.org Subject: Re: reset with fwcontrol -R 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: Sun, 10 Jan 2010 19:47:26 -0000 On Mon, 2010-01-11 at 03:28 +0900, Kazumaro Aoki wrote: > From: Sean Bruno > Subject: Re: reset with fwcontrol -R > Date: Mon, 04 Jan 2010 13:16:22 -0800 > > >> > I have several experiences that sudden reboot is happened just after > >> > "fwcontrol -R foo.dv" was invoked. The operating system is FreeBSD > >> > 7.2R/i386. Before I use 7.2R, I used 6.3R and I never experienced > >> > such phenomenon. > >> > >> At December 27, I met the similar problem. The system caused a panic. > (snip) > > I'm not clear what is going on from the attached information. I have > > been looking around to see what could have changed to affect these > > problems. > > Thank you for considering my problem. > > > Can you try setting the firewire debug to 3 and testing? > > sysctl debug.firewire_debug=3 > > Yes. I changed the value described above and I observed the system > behavior. The OS hardly panics, but I finally got the panic. > I copied the log message from messages without date and system name: > start IR DMA 0x40000011 > > > > I feel that no helpful information is logged. > I agree. Not helpful. The debug.firewire_debug=3 will display more output on the console during use. This is the interesting information to capture. Probably, you would need to configure a serial console and capture the output from a second computer. However, the next bit of information is MORE interesting to me. > The panic was occurred January 7. After this, I did not meet a panic. > At that time, I did not make a crash dump. When the panic happens > next time, I can get a crash dump. I used fwcontrol -R about 17 times > per day. > > Ah, I forgot to mention the following fact. When I used without -M dv > option, fwcontrol -R outputs: > fwcontrol: detect_recv_fn: ioctl FW_SSTBUF: Bad file descriptor > So, I used fwcontrol implementation in FreeBSD 6.3R. Moreover, when > I am using fwcontrol -R, I cannot use "fwcontrol" with no option. > When I used FreeBSD6.3R, I can see the result from fwcontrol, because > fwcontrol outputs: > fwcontrol: main: Error opening firewire controller #0 /dev/fw0.0: Device busy > That is the another reason why I use fwcontrol implemented in FreeBSD > 6.3R, though the operating system is FreeBSD7.2R. > If I understand correctly, you are using the FBSD 6.3 fwcontrol on a FBSD 7.2 system to use your cameras. The fact that the 7.2 system does not work correctly *may* be easier to fix than the 6.3R panic with a 7.2R binary. I will attempt to debug this problem first and see if I can determine what's broken. Thank you for your patience. We'll get it working. Sean From owner-freebsd-firewire@FreeBSD.ORG Mon Jan 11 11:06:57 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 E7DB61065697 for ; Mon, 11 Jan 2010 11:06:57 +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 D75C28FC1A for ; Mon, 11 Jan 2010 11:06:57 +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 o0BB6v28034636 for ; Mon, 11 Jan 2010 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o0BB6vla034634 for freebsd-firewire@FreeBSD.org; Mon, 11 Jan 2010 11:06:57 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 11 Jan 2010 11:06:57 GMT Message-Id: <201001111106.o0BB6vla034634@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, 11 Jan 2010 11:06:58 -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 Tue Jan 12 08:44:47 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 8183A1065694 for ; Tue, 12 Jan 2010 08:44:47 +0000 (UTC) (envelope-from ka@flu.if0.org) Received: from flu.if0.org (v112022.ppp.asahi-net.or.jp [124.155.112.22]) by mx1.freebsd.org (Postfix) with ESMTP id 3A6B18FC1A for ; Tue, 12 Jan 2010 08:44:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by flu.if0.org (8.14.3/8.14.3) with ESMTP id o0BFF2di022637 for ; Tue, 12 Jan 2010 00:15:03 +0900 (JST) (envelope-from ka@flu.if0.org) Date: Tue, 12 Jan 2010 00:15:02 +0900 (JST) Message-Id: <20100112.001502.164372502.ka@flu.if0.org> To: freebsd-firewire@freebsd.org From: Kazumaro Aoki In-Reply-To: <1263152838.8632.48.camel@home-lappy> References: <1262639782.2209.305.camel@home-lappy> <20100111.032824.208936614.ka@flu.if0.org> <1263152838.8632.48.camel@home-lappy> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: reset with fwcontrol -R 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, 12 Jan 2010 08:44:47 -0000 From: Sean Bruno Subject: Re: reset with fwcontrol -R Date: Sun, 10 Jan 2010 11:47:18 -0800 > The debug.firewire_debug=3 will display more output on the console > during use. This is the interesting information to capture. Probably, > you would need to configure a serial console and capture the output from > a second computer. Unfortunately, the target computer is located far from me. I cannot change the physical connection of the computer. I can only request to reboot the system. I changed /etc/syslog.conf to log all information on the console to a file. >> Ah, I forgot to mention the following fact. When I used without -M dv >> option, fwcontrol -R outputs: >> fwcontrol: detect_recv_fn: ioctl FW_SSTBUF: Bad file descriptor >> So, I used fwcontrol implementation in FreeBSD 6.3R. Moreover, when >> I am using fwcontrol -R, I cannot use "fwcontrol" with no option. >> When I used FreeBSD6.3R, I can see the result from fwcontrol, because >> fwcontrol outputs: >> fwcontrol: main: Error opening firewire controller #0 /dev/fw0.0: Device busy >> That is the another reason why I use fwcontrol implemented in FreeBSD >> 6.3R, though the operating system is FreeBSD7.2R. > > If I understand correctly, you are using the FBSD 6.3 fwcontrol on a > FBSD 7.2 system to use your cameras. Your understanding of the binary is correct. I used two video capture boxes from firewire. > The fact that the 7.2 system does not work correctly *may* be easier to > fix than the 6.3R panic with a 7.2R binary. I will attempt to debug > this problem first and see if I can determine what's broken. > > Thank you for your patience. We'll get it working. Thank you for considering my problem. I will report results when my system crashes from "fwcontrol -R" again. Kazumaro From owner-freebsd-firewire@FreeBSD.ORG Sat Jan 16 18:14:45 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 4B264106566C for ; Sat, 16 Jan 2010 18:14:45 +0000 (UTC) (envelope-from ka@flu.if0.org) Received: from flu.if0.org (v112022.ppp.asahi-net.or.jp [124.155.112.22]) by mx1.freebsd.org (Postfix) with ESMTP id 065D48FC19 for ; Sat, 16 Jan 2010 18:14:44 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by flu.if0.org (8.14.3/8.14.3) with ESMTP id o0GIEgE0042170 for ; Sun, 17 Jan 2010 03:14:43 +0900 (JST) (envelope-from ka@flu.if0.org) Date: Sun, 17 Jan 2010 03:14:42 +0900 (JST) Message-Id: <20100117.031442.112571713.ka@flu.if0.org> To: freebsd-firewire@freebsd.org From: Kazumaro Aoki In-Reply-To: <20100112.001502.164372502.ka@flu.if0.org> References: <20100111.032824.208936614.ka@flu.if0.org> <1263152838.8632.48.camel@home-lappy> <20100112.001502.164372502.ka@flu.if0.org> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: reset with fwcontrol -R 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, 16 Jan 2010 18:14:45 -0000 From: Kazumaro Aoki Subject: Re: reset with fwcontrol -R Date: Tue, 12 Jan 2010 00:15:02 +0900 (JST) > I changed /etc/syslog.conf to log all information on the console to a > file. I already changed the syslog.conf, but any additional information are not logged to the file. Does firewire driver directly write to console? > I will report results when my system crashes from "fwcontrol -R" > again. The system crashed January 12, but it fails to make a crash dump. I did not get any useful information. According to my past experience, the system can dump with probability about a half. Kazumaro