Re: reset with fwcontrol -R

On Mon, 2010-01-04 at 19:01 +0900, Kazumaro Aoki wrote:
> From: Kazumaro Aoki <[email protected]>
> 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: <VIA Fire II (VT6306)> 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: <IEEE1394(FireWire) bus> on fwohci0
> fwe0: <Ethernet over FireWire> on firewire0
> if_fwe0: Fake Ethernet address: 02:a0:b0:00:53:f8
> fwe0: Ethernet address: 02:a0:b0:00:53:f8
> fwip0: <IP over FireWire> on firewire0
> fwip0: Firewire address: 00:a0:b0:0a:00:00:53:f8 @ 0xfffe00000000, S400, maxrec 2048
> sbp0: <SBP-2/SCSI over FireWire> on firewire0
> dcons_crom0: <dcons configuration ROM> on firewire0
> dcons_crom0: bus_addr 0x1310000
> fwohci0: Initiate bus reset
> fwohci0: BUS reset
> fwohci0: node_id=0xc800ffc1, gen=1, CYCLEMASTER mode
> fwohci1: <Texas Instruments TSB43AB23> 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: <IEEE1394(FireWire) bus> on fwohci1
> fwe1: <Ethernet over FireWire> on firewire1
> if_fwe1: Fake Ethernet address: 02:e2:ec:00:24:1d
> fwe1: Ethernet address: 02:e2:ec:00:24:1d
> fwip1: <IP over FireWire> on firewire1
> fwip1: Firewire address: 00:e2:ec:cc:00:00:24:1d @ 0xfffe00000000, S400, maxrec 2048
> sbp1: <SBP-2/SCSI over FireWire> on firewire1
> dcons_crom1: <dcons configuration ROM> 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



_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-firewire
To unsubscribe, send any mail to "[email protected]"