Thread: kernel hangs when powering up DV-camera
Brought to you by:
aeb,
bencollins
From: Marcel J. <mph...@ho...> - 2001-02-05 20:57:38
|
Hi, This is my first try with ieee1394 and I seem to get my card going. My card is a Texas Instruments OHCI campliant one and I use kernel 2.4.0 with the CVS fix (05-02-2001). When I leave the camera switched off, the modules load fine. When I power up the camera, my whole box hangs (no mouse/keyboard/network etc). No matter if I first load the modules and power up the camera afterwards or the other way round. I've got no idea where to start looking for a solution. Since my box locks immediately after switching on the camera, I have no report to my log files. I included the kernel log of my modules (when camera switched off) at the bottom of this mail. My camera is a sony DCR-PC5E. Can the use of devfs be a problem ? thanks, Marcel Janssen Feb 5 19:00:44 korgull kernel: ieee1394: registered ohci1394 driver, initializing now Feb 5 19:00:44 korgull kernel: ohci1394: looking for Ohci1394 cards Feb 5 19:00:44 korgull kernel: PCI: Found IRQ 9 for device 00:0a.0 Feb 5 19:00:44 korgull kernel: ohci1394_0: remapped memory spaces reg 0xcd8d0000 Feb 5 19:00:44 korgull kernel: ohci1394_0: allocated interrupt 9 Feb 5 19:00:44 korgull kernel: ohci1394_0: soft reset finished Feb 5 19:00:44 korgull kernel: ohci1394_0: max packet size = 2048 bytes Feb 5 19:00:44 korgull kernel: ohci1394_0: 4 iso receive contexts available Feb 5 19:00:44 korgull kernel: ohci1394_0: 8 iso transmit contexts available Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=0 initialized Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=1 initialized Feb 5 19:00:44 korgull kernel: ohci1394_0: AT dma ctx=0 initialized Feb 5 19:00:44 korgull kernel: ohci1394_0: AT dma ctx=1 initialized Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=2 initialized Feb 5 19:00:44 korgull kernel: ohci1394_0: resetting bus on request Feb 5 19:00:44 korgull kernel: ieee1394: detected 1 ohci1394 adapter Feb 5 19:00:44 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, root) Feb 5 19:00:44 korgull kernel: ohci1394_0: selfid packet 0x807f8c56 rcvd Feb 5 19:00:44 korgull kernel: ohci1394_0: This node self-id is 0x807f8c56 Feb 5 19:00:44 korgull kernel: ohci1394_0: calling self-id complete Feb 5 19:00:44 korgull kernel: ohci1394_0: Got phy packet ctx=0 ... discarded Feb 5 19:00:56 korgull kernel: devfs: devfs_register(): device already registered: "raw1394" Feb 5 19:00:56 korgull kernel: raw1394: /dev/raw1394 device initialized Feb 5 19:01:00 korgull CROND[6021]: (root) CMD (run-parts /etc/cron.hourly) Feb 5 19:01:01 korgull kernel: ohci1394_0: Bus reset Feb 5 19:01:01 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, not root) Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x807f8c94 rcvd Feb 5 19:01:01 korgull kernel: ohci1394_0: This node self-id is 0x807f8c94 Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x813f08c2 rcvd Feb 5 19:01:01 korgull kernel: ohci1394_0: calling self-id complete Feb 5 19:01:01 korgull kernel: ohci1394_0: Bus reset Feb 5 19:01:01 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, not root) Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x807f8c94 rcvd Feb 5 19:01:01 korgull kernel: ohci1394_0: This node self-id is 0x807f8c94 Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x813f08c2 rcvd Feb 5 19:01:01 korgull kernel: ohci1394_0: calling self-id complete Feb 5 19:01:01 korgull kernel: ohci1394_0: Got phy packet ctx=0 ... discarded |
From: Dan D. <dde...@co...> - 2001-02-06 06:16:17
|
With the camera off, obviously, pager /proc/ohci1394 and what is the node count? It should be 1 for the host adapter itself. If it is zero, then your card is not operating properly on the PCI bus. Have you disabled PnP OS in the BIOS? Turn that off if you have not. You still have PnP, but it will be controlled by BIOS and not the OS. Marcel Janssen wrote: > > Hi, > > This is my first try with ieee1394 and I seem to get my card going. > My card is a Texas Instruments OHCI campliant one and I use kernel 2.4.0 with > the CVS fix (05-02-2001). > > When I leave the camera switched off, the modules load fine. When I power up > the camera, my whole box hangs (no mouse/keyboard/network etc). No matter if > I first load the modules and power up the camera afterwards or the other way > round. > > I've got no idea where to start looking for a solution. Since my box locks > immediately after switching on the camera, I have no report to my log files. > > I included the kernel log of my modules (when camera switched off) at the > bottom of this mail. > > My camera is a sony DCR-PC5E. > > Can the use of devfs be a problem ? > > thanks, > Marcel Janssen > > Feb 5 19:00:44 korgull kernel: ieee1394: registered ohci1394 driver, > initializing now > Feb 5 19:00:44 korgull kernel: ohci1394: looking for Ohci1394 cards > Feb 5 19:00:44 korgull kernel: PCI: Found IRQ 9 for device 00:0a.0 > Feb 5 19:00:44 korgull kernel: ohci1394_0: remapped memory spaces reg > 0xcd8d0000 > Feb 5 19:00:44 korgull kernel: ohci1394_0: allocated interrupt 9 > Feb 5 19:00:44 korgull kernel: ohci1394_0: soft reset finished > Feb 5 19:00:44 korgull kernel: ohci1394_0: max packet size = 2048 bytes > Feb 5 19:00:44 korgull kernel: ohci1394_0: 4 iso receive contexts available > Feb 5 19:00:44 korgull kernel: ohci1394_0: 8 iso transmit contexts available > Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=0 initialized > Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=1 initialized > Feb 5 19:00:44 korgull kernel: ohci1394_0: AT dma ctx=0 initialized > Feb 5 19:00:44 korgull kernel: ohci1394_0: AT dma ctx=1 initialized > Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=2 initialized > Feb 5 19:00:44 korgull kernel: ohci1394_0: resetting bus on request > Feb 5 19:00:44 korgull kernel: ieee1394: detected 1 ohci1394 adapter > Feb 5 19:00:44 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, > root) > Feb 5 19:00:44 korgull kernel: ohci1394_0: selfid packet 0x807f8c56 rcvd > Feb 5 19:00:44 korgull kernel: ohci1394_0: This node self-id is 0x807f8c56 > Feb 5 19:00:44 korgull kernel: ohci1394_0: calling self-id complete > Feb 5 19:00:44 korgull kernel: ohci1394_0: Got phy packet ctx=0 ... discarded > Feb 5 19:00:56 korgull kernel: devfs: devfs_register(): device already > registered: "raw1394" > Feb 5 19:00:56 korgull kernel: raw1394: /dev/raw1394 device initialized > Feb 5 19:01:00 korgull CROND[6021]: (root) CMD (run-parts /etc/cron.hourly) > Feb 5 19:01:01 korgull kernel: ohci1394_0: Bus reset > Feb 5 19:01:01 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, > not root) > Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x807f8c94 rcvd > Feb 5 19:01:01 korgull kernel: ohci1394_0: This node self-id is 0x807f8c94 > Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x813f08c2 rcvd > Feb 5 19:01:01 korgull kernel: ohci1394_0: calling self-id complete > Feb 5 19:01:01 korgull kernel: ohci1394_0: Bus reset > Feb 5 19:01:01 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, > not root) > Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x807f8c94 rcvd > Feb 5 19:01:01 korgull kernel: ohci1394_0: This node self-id is 0x807f8c94 > Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x813f08c2 rcvd > Feb 5 19:01:01 korgull kernel: ohci1394_0: calling self-id complete > Feb 5 19:01:01 korgull kernel: ohci1394_0: Got phy packet ctx=0 ... discarded > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Marcel J. <mph...@ho...> - 2001-02-06 07:06:23
|
On Tuesday 06 February 2001 07:26, Dan Dennedy wrote: > With the camera off, obviously, pager /proc/ohci1394 and what is the > node count? It should be 1 for the host adapter itself. If it is zero, > then your card is not operating properly on the PCI bus. > > Have you disabled PnP OS in the BIOS? Turn that off if you have not. You > still have PnP, but it will be controlled by BIOS and not the OS. I had PnP OS disabled in the BIOS. I've attached the output of /proc/ohci1394, note count is 1. thanks, Marcel Janssen [root@korgull libraw1394-0.8.2]# cat /proc/ohci1394 IEEE-1394 OHCI Driver status report: bus number: 0x3ff Node ID: 0x0 ### Host data ### node_count: 1 node_id : 0000FFC0 irm_id : 0000FFC0 busmgr_id : 0000FFC0 initialized root iso_res_mgr bus_mgr ---Iso Receive DMA--- Current buf: 0 offset: 0 ---Async Receive DMA--- Ar req current buf: 0 offset: 16 AR resp current buf: 0 offset: 0 ---Async Transmit DMA--- AT req prg: 0 sent: 0 free: 32 branchAddrPtr: 00000000 AT req queue: first: 00000000 last: 00000000 AR resp prg: 0 sent: 0 free: 32 branchAddrPtr: 00000000 AT resp queue: first: 00000000 last: 00000000 ### HC Register dump ### Version : 01010000 GUID_ROM : 00000000 ATRetries : 00000822 CSRData : 00000000 CSRCompData : 00000000 CSRControl : 80000000 ConfigROMhdr: 04040bd7 BusID : 31333934 BusOptions : f07da002 GUIDHi : 00506256 GUIDLo : 00008e43 ConfigROMmap: 07311000 PtdWrAddrLo : 00000000 PtdWrAddrHi : 00000000 VendorID : 00000000 HCControl : 000e0000 SelfIDBuffer: 0a084000 SelfIDCount : 0001000c IRMuChMaskHi: 00000000 IRMuChMaskLo: 00000000 IntEvent : 00100000 IntMask : 840300ff IsoXmIntEvnt: 00000000 IsoXmIntMask: 00000000 IsoRcvIntEvt: 00000000 IsoRcvIntMsk: 00000001 FairnessCtrl: 00000000 LinkControl : 00300200 NodeID : c000ffc0 PhyControl : 0000017f IsoCyclTimer: 2302b8b6 AsRqFilterHi: ffffffff AsRqFilterLo: ffffffff PhyReqFiltHi: ffffffff PhyReqFiltLo: ffffffff PhyUpperBnd : 00000000 AsRqTrCxtCtl: 00000000 AsRqTrCmdPtr: 00000000 AsRsTrCtxCtl: 00000000 AsRsTrCmdPtr: 00000000 AsRqRvCtxCtl: 00008409 AsRqRvCmdPtr: 0739b001 AsRsRvCtxCtl: 00008400 AsRsRvCmdPtr: 081d3001 IntEvent : 00100000 IsoRCtxCtl00: d0008400 IsoRCmdPtr00: 014c2001 IsoRCxtMch00: f0000000 IsoRCtxCtl01: 00000000 IsoRCmdPtr01: 00000000 IsoRCxtMch01: 00000000 IsoRCtxCtl02: 00000000 IsoRCmdPtr02: 00000000 IsoRCxtMch02: 00000000 IsoRCtxCtl03: 00000000 IsoRCmdPtr03: 00000000 IsoRCxtMch03: 00000000 IsoTCtxCtl00: 00000000 IsoTCmdPtr00: 00000000 IsoTCtxCtl01: 00000000 IsoTCmdPtr01: 00000000 IsoTCtxCtl02: 00000000 IsoTCmdPtr02: 00000000 IsoTCtxCtl03: 00000000 IsoTCmdPtr03: 00000000 IsoTCtxCtl04: 00000000 IsoTCmdPtr04: 00000000 IsoTCtxCtl05: 00000000 IsoTCmdPtr05: 00000000 IsoTCtxCtl06: 00000000 IsoTCmdPtr06: 00000000 IsoTCtxCtl07: 00000000 IsoTCmdPtr07: 00000000 [root@korgull libraw1394-0.8.2]# |
From: Tom B. <tb...@ba...> - 2001-02-06 07:15:48
|
On Tue, 6 Feb 2001, Marcel Janssen wrote: > On Tuesday 06 February 2001 07:26, Dan Dennedy wrote: > > With the camera off, obviously, pager /proc/ohci1394 and what is the > > node count? It should be 1 for the host adapter itself. If it is zero, > > then your card is not operating properly on the PCI bus. > > > > Have you disabled PnP OS in the BIOS? Turn that off if you have not. You > > still have PnP, but it will be controlled by BIOS and not the OS. > > I had PnP OS disabled in the BIOS. I've attached the output of > /proc/ohci1394, note count is 1. > > thanks, > Marcel Janssen > > > [root@korgull libraw1394-0.8.2]# cat /proc/ohci1394 > IEEE-1394 OHCI Driver status report: > bus number: 0x3ff Node ID: 0x0 > > ### Host data ### > node_count: 1 node_id : 0000FFC0 > irm_id : 0000FFC0 busmgr_id : 0000FFC0 > initialized > root iso_res_mgr bus_mgr can someone explain what the above flags are? my similar system (2.2.16 kernel though) has similar symptoms (locks up), except that I recover control when the the camera is turned off or disconnected... and I don't have the bus_mgr flags, and the busmgr_id is ffff ### Host data ### node_count: 1 node_id : 0000FFC0 irm_id : 0000FFFF busmgr_id : 0000FFFF initialized root is that just something new? my data is from late december... I was thinking that it was just that the Dlink DFW-500 card was bad, but someone reported success with it just recently... -Tom |
From: Marcel J. <mph...@ho...> - 2001-02-06 18:57:37
|
Hi, I'm still stuck with the same problem. After being busy for about 5 hours, I still get my box to lock completely and get real sick of fsck :-( I would like to know wether anyone tried the latest code with kernel 2.4.0 with any succes. And, how about the latest 2.4.1 kernel (?), is the code in there ok ? -- Marcel Janssen |
From: Dan D. <dde...@co...> - 2001-02-06 20:21:38
|
I am using a CVS snapshot from Jan 22 with kernel 2.4.0. There has only been changes to the Makefile and a change in one line in ieee1394_core.c since then. Everything is working great for me. (I know you wanted to hear that ;-) 2.4.1 does not include the latest stable code because evidently the submissions by our project master have been overlooked by the kernel maintainers. ----- Original Message ----- From: "Marcel Janssen" <mph...@ho...> To: <lin...@li...> Sent: Tuesday, February 06, 2001 1:49 PM Subject: Re: kernel hangs when powering up DV-camera > Hi, > > I'm still stuck with the same problem. After being busy for about 5 hours, I > still get my box to lock completely and get real sick of fsck :-( > I would like to know wether anyone tried the latest code with kernel 2.4.0 > with any succes. And, how about the latest 2.4.1 kernel (?), is the code in > there ok ? > > -- > Marcel Janssen > > > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Dan D. <dde...@co...> - 2001-02-06 20:23:05
|
I am using a CVS snapshot from Jan 22 with kernel 2.4.0. There has only been changes to the Makefile and a change in one line in ieee1394_core.c since then. Everything is working great for me. (I know you wanted to hear that ;-) 2.4.1 does not include the latest stable code because evidently the submissions by our project master have been overlooked by the kernel maintainers. ----- Original Message ----- From: "Marcel Janssen" <mph...@ho...> To: <lin...@li...> Sent: Tuesday, February 06, 2001 1:49 PM Subject: Re: kernel hangs when powering up DV-camera > Hi, > > I'm still stuck with the same problem. After being busy for about 5 hours, I > still get my box to lock completely and get real sick of fsck :-( > I would like to know wether anyone tried the latest code with kernel 2.4.0 > with any succes. And, how about the latest 2.4.1 kernel (?), is the code in > there ok ? > > -- > Marcel Janssen > > > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Marcel J. <mph...@ho...> - 2001-02-06 20:25:42
|
HI, I've got things running with the 2.4.0 kernel. I downloaded the patch at : http://www.schirmacher.de/arne/kino/index_e.html Probably it's different from the current CVS, I haven't checked yet. -- Marcel Janssen |