Date: Sun, 10 Jan 2010 11:47:18 -0800 From: Sean Bruno <sean.bruno@dsl-only.net> To: Kazumaro Aoki <ka@flu.if0.org> Cc: freebsd-firewire@freebsd.org Subject: Re: reset with fwcontrol -R Message-ID: <1263152838.8632.48.camel@home-lappy> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2010-01-11 at 03:28 +0900, Kazumaro Aoki wrote: > From: Sean Bruno <sean.bruno@dsl-only.net> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1263152838.8632.48.camel>