From owner-freebsd-firewire@FreeBSD.ORG Sun Jan 3 13:40:11 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 89F86106576F; Sun, 3 Jan 2010 13:40:11 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 61EA78FC12; Sun, 3 Jan 2010 13:40:11 +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 o03DeBng050154; Sun, 3 Jan 2010 13:40:11 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o03DeB1n050145; Sun, 3 Jan 2010 13:40:11 GMT (envelope-from gavin) Date: Sun, 3 Jan 2010 13:40:11 GMT Message-Id: <201001031340.o03DeB1n050145@freefall.freebsd.org> To: gavin@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-firewire@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: bin/128277: [patch] improvements for fwcontrol(8) utility 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, 03 Jan 2010 13:40:11 -0000 Synopsis: [patch] improvements for fwcontrol(8) utility Responsible-Changed-From-To: freebsd-bugs->freebsd-firewire Responsible-Changed-By: gavin Responsible-Changed-When: Sun Jan 3 13:39:31 UTC 2010 Responsible-Changed-Why: Over to maintainer(s). Apart from a couple of style issues, the patch looks good to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=128277 From owner-freebsd-firewire@FreeBSD.ORG Sun Jan 3 15:06:16 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 24E2F1065692; Sun, 3 Jan 2010 15:06:16 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F10EC8FC0C; Sun, 3 Jan 2010 15:06:15 +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 o03F6FUI051462; Sun, 3 Jan 2010 15:06:15 GMT (envelope-from gavin@freefall.freebsd.org) Received: (from gavin@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o03F6F4o051458; Sun, 3 Jan 2010 15:06:15 GMT (envelope-from gavin) Date: Sun, 3 Jan 2010 15:06:15 GMT Message-Id: <201001031506.o03F6F4o051458@freefall.freebsd.org> To: freebsd@sopwith.solgatos.com, gavin@FreeBSD.org, freebsd-firewire@FreeBSD.org From: gavin@FreeBSD.org Cc: Subject: Re: bin/128277: [patch] improvements for fwcontrol(8) utility 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, 03 Jan 2010 15:06:16 -0000 Synopsis: [patch] improvements for fwcontrol(8) utility State-Changed-From-To: open->closed State-Changed-By: gavin State-Changed-When: Sun Jan 3 15:05:19 UTC 2010 State-Changed-Why: Turns out this was already committed in r185996 and merged to 6.x http://www.freebsd.org/cgi/query-pr.cgi?pr=128277 From owner-freebsd-firewire@FreeBSD.ORG Mon Jan 4 10:01:39 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 5C355106568F for ; Mon, 4 Jan 2010 10:01:39 +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 283628FC19 for ; Mon, 4 Jan 2010 10:01:38 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by flu.if0.org (8.14.3/8.14.3) with ESMTP id o04A171Z055888 for ; Mon, 4 Jan 2010 19:01:20 +0900 (JST) (envelope-from ka@flu.if0.org) Date: Mon, 04 Jan 2010 19:01:07 +0900 (JST) Message-Id: <20100104.190107.74684647.ka@flu.if0.org> To: freebsd-firewire@freebsd.org From: Kazumaro Aoki In-Reply-To: <20091228.001440.71123742.ka@flu.if0.org> References: <20091228.001440.71123742.ka@flu.if0.org> X-Mailer: Mew version 6.2 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: Mon, 04 Jan 2010 10:01:39 -0000 From: Kazumaro Aoki Subject: reset with fwcontrol -R Date: Mon, 28 Dec 2009 00:14:40 +0900 (JST) > 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. Usually, the system reboots but the system was halted at that time. The console shows as follows: ============================================================ instruction pointer = 0x20:0xc05f6d8a stack pointer = 0x28:0xe5c38c2c frame pointer = 0x28:0xe5c30c9c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 42 (fw0_taskq) trap number = 12 1panick: eprangeel ftarwalpt 2 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 3; apic id = 03 fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0818efe stack pointer = 0x28:0xc5376b54 frame pointer = 0x28:0xc5376b74 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 3 (g_up) trap number = 12 ============================================================ At the time, I did not set up for the crash dump. Now, I added the setup to rc.conf to make a crash dump. The following is the part of start up message that may relate to the problem. CPU: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz (2833.03-MHz 686-class CPU) real memory = 2110455808 (2012 MB) FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs fwohci0: port 0xd000-0xd07f mem 0xe2505000-0xe25057ff irq 19 at device 1.0 on pci4 fwohci0: [FILTER] fwohci0: OHCI version 1.0 (ROM=1) fwohci0: No. of Isochronous channels is 8. fwohci0: EUI64 00:a0:b0:0a:00:00:53:f8 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:a0:b0:00:53:f8 fwe0: Ethernet address: 02:a0:b0:00:53:f8 fwip0: on firewire0 fwip0: Firewire address: 00:a0:b0:0a:00:00:53:f8 @ 0xfffe00000000, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x1310000 fwohci0: Initiate bus reset fwohci0: BUS reset fwohci0: node_id=0xc800ffc1, gen=1, CYCLEMASTER mode fwohci1: mem 0xe2504000-0xe25047ff,0xe2500000-0xe2503fff irq 23 at device 7.0 on pci4 fwohci1: [FILTER] fwohci1: OHCI version 1.10 (ROM=0) fwohci1: No. of Isochronous channels is 4. fwohci1: EUI64 00:e2:ec:cc:00:00:24:1d fwohci1: Phy 1394a available S400, 3 ports. fwohci1: Link S400, max_rec 2048 bytes. firewire1: on fwohci1 fwe1: on firewire1 if_fwe1: Fake Ethernet address: 02:e2:ec:00:24:1d fwe1: Ethernet address: 02:e2:ec:00:24:1d fwip1: on firewire1 fwip1: Firewire address: 00:e2:ec:cc:00:00:24:1d @ 0xfffe00000000, S400, maxrec 2048 sbp1: on firewire1 dcons_crom1: on firewire1 dcons_crom1: bus_addr 0x1310000 dcons_crom1: dcons_paddr is already set fwohci1: Initiate bus reset fwohci1: BUS reset fwohci1: node_id=0xc800ffc1, gen=1, CYCLEMASTER mode firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire0: bus manager 1 (me) firewire1: 2 nodes, maxhop <= 1, cable IRM = 1 (me) firewire1: bus manager 1 (me) firewire0: New S400 device ID:00a0b0210001a733 firewire1: New S400 device ID:00a0b02100015512 Kazumaro From owner-freebsd-firewire@FreeBSD.ORG Mon Jan 4 11:06:55 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 B5482106568B for ; Mon, 4 Jan 2010 11:06:55 +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 A3DAA8FC19 for ; Mon, 4 Jan 2010 11:06:55 +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 o04B6tww064863 for ; Mon, 4 Jan 2010 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id o04B6t7W064861 for freebsd-firewire@FreeBSD.org; Mon, 4 Jan 2010 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Jan 2010 11:06:55 GMT Message-Id: <201001041106.o04B6t7W064861@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, 04 Jan 2010 11:06:55 -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 Mon Jan 4 21:16:23 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 E870B106566B for ; Mon, 4 Jan 2010 21:16:23 +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 C52728FC08 for ; Mon, 4 Jan 2010 21:16:23 +0000 (UTC) Received: (qmail 4876 invoked from network); 4 Jan 2010 13:16:21 -0800 Received: from 069-064-235-060.pdx.net (HELO ?192.168.1.53?) (69.64.235.60) by iron2.pdx.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Jan 2010 13:16:20 -0800 From: Sean Bruno To: Kazumaro Aoki In-Reply-To: <20100104.190107.74684647.ka@flu.if0.org> References: <20091228.001440.71123742.ka@flu.if0.org> <20100104.190107.74684647.ka@flu.if0.org> Content-Type: text/plain; charset="UTF-8" Date: Mon, 04 Jan 2010 13:16:22 -0800 Message-ID: <1262639782.2209.305.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: Mon, 04 Jan 2010 21:16:24 -0000 On Mon, 2010-01-04 at 19:01 +0900, Kazumaro Aoki wrote: > From: Kazumaro Aoki > Subject: reset with fwcontrol -R > Date: Mon, 28 Dec 2009 00:14:40 +0900 (JST) > > > 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. > Usually, the system reboots but the system was halted at that time. > The console shows as follows: > ============================================================ > instruction pointer = 0x20:0xc05f6d8a > stack pointer = 0x28:0xe5c38c2c > frame pointer = 0x28:0xe5c30c9c > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 42 (fw0_taskq) > trap number = 12 > 1panick: eprangeel ftarwalpt > 2 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > cpuid = 3; apic id = 03 > fault virtual address = 0x14 > fault code = supervisor read, page not present > instruction pointer = 0x20:0xc0818efe > stack pointer = 0x28:0xc5376b54 > frame pointer = 0x28:0xc5376b74 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 3 (g_up) > trap number = 12 > ============================================================ > At the time, I did not set up for the crash dump. > Now, I added the setup to rc.conf to make a crash dump. > > > The following is the part of start up message that may relate to the problem. > > CPU: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz (2833.03-MHz 686-class CPU) > real memory = 2110455808 (2012 MB) > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > fwohci0: port 0xd000-0xd07f mem 0xe2505000-0xe25057ff irq 19 at device 1.0 on pci4 > fwohci0: [FILTER] > fwohci0: OHCI version 1.0 (ROM=1) > fwohci0: No. of Isochronous channels is 8. > fwohci0: EUI64 00:a0:b0:0a:00:00:53:f8 > fwohci0: Phy 1394a available S400, 3 ports. > fwohci0: Link S400, max_rec 2048 bytes. > firewire0: on fwohci0 > fwe0: on firewire0 > if_fwe0: Fake Ethernet address: 02:a0:b0:00:53:f8 > fwe0: Ethernet address: 02:a0:b0:00:53:f8 > fwip0: on firewire0 > fwip0: Firewire address: 00:a0:b0:0a:00:00:53:f8 @ 0xfffe00000000, S400, maxrec 2048 > sbp0: on firewire0 > dcons_crom0: on firewire0 > dcons_crom0: bus_addr 0x1310000 > fwohci0: Initiate bus reset > fwohci0: BUS reset > fwohci0: node_id=0xc800ffc1, gen=1, CYCLEMASTER mode > fwohci1: mem 0xe2504000-0xe25047ff,0xe2500000-0xe2503fff irq 23 at device 7.0 on pci4 > fwohci1: [FILTER] > fwohci1: OHCI version 1.10 (ROM=0) > fwohci1: No. of Isochronous channels is 4. > fwohci1: EUI64 00:e2:ec:cc:00:00:24:1d > fwohci1: Phy 1394a available S400, 3 ports. > fwohci1: Link S400, max_rec 2048 bytes. > firewire1: on fwohci1 > fwe1: on firewire1 > if_fwe1: Fake Ethernet address: 02:e2:ec:00:24:1d > fwe1: Ethernet address: 02:e2:ec:00:24:1d > fwip1: on firewire1 > fwip1: Firewire address: 00:e2:ec:cc:00:00:24:1d @ 0xfffe00000000, S400, maxrec 2048 > sbp1: on firewire1 > dcons_crom1: on firewire1 > dcons_crom1: bus_addr 0x1310000 > dcons_crom1: dcons_paddr is already set > fwohci1: Initiate bus reset > fwohci1: BUS reset > fwohci1: node_id=0xc800ffc1, gen=1, CYCLEMASTER mode > firewire0: 2 nodes, maxhop <= 1, cable IRM = 1 (me) > firewire0: bus manager 1 (me) > firewire1: 2 nodes, maxhop <= 1, cable IRM = 1 (me) > firewire1: bus manager 1 (me) > firewire0: New S400 device ID:00a0b0210001a733 > firewire1: New S400 device ID:00a0b02100015512 > > Kazumaro > _______________________________________________ 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. Can you try setting the firewire debug to 3 and testing? sysctl debug.firewire_debug=3 Sean