Re: [libdv-dev] Continuous "audio block/sample failure" with JVC DV camera

[Marko <mar...@hu...>]

On Thu, Dec 02, 2004 at 12:07:47PM +0200, Marko M=E4kel=E4 wrote:
> On Thu, Dec 02, 2004 at 01:04:51AM -0500, Nathan Kidd wrote:
> > Marko M=E4kel=E4 wrote:
> > >I have a JVC GR-DVL9600 (PAL), and audio has worked for me, except f=
or some
> > >occasional glitches, probably due to errors on the tape.  I've been =
using
> > >libdv with the 2.4 kernel since 2.4.21 or so.
> >=20
> > My motherboard only is supported by 2.6, so I unfortunately can't try=
=20
> > 2.4.  But it's good to know it's not a universal JVC thing.  Maybe it=
's=20
> > just my model. That would figure. :)
>=20
> Well, the GR-DVL9600 is pretty old, apparently from early 2000.  It eve=
n
> features a JLIP connector (RS-232) for importing still pictures.  It wa=
s
> a display model that I bought around March 2003.
>=20
> When I last tried the 2.6 kernel in Debian GNU/Linux unstable, I got so=
me
> trouble with the loading of modules.  Maybe the support has been improv=
ed
> by now.  I could give it a try within the next week.  My IEEE-1394 inte=
rface
> is a cheap PCI card based on VIA 6306, if I remember correctly.

I'm sorry for the delay, but I didn't get around to this immediately, and
I also had to do some surgery to the camera after it dropped about 1 mete=
r
to the ground.  Only the case was damaged, but I had to disassemble the w=
hole
camera in order to fix the strap holder that broke off.  While doing that=
,
I of course had to break the locking mechanism of one tiny 51-pin connect=
or
inside the camera.

I just tested Kino with kernel 2.6.11.1 on a OHCI1394 compliant PCMCIA
Firewire adapter that has worked with kernel 2.4.x.  When I plug it in,
I get this:

ohci1394: $Rev: 1223 $ Ben Collins <bco...@de...>
PCI: Enabling device 0000:03:00.0 (0000 -> 0002)
ACPI: PCI interrupt 0000:03:00.0[A] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:03:00.0 to 64
ohci1394: fw-host0: Unexpected PCI resource length of 1000!
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=3D[11]  MMIO=3D[10800000-108=
007ff]  Max Packet=3D[2048]
uhci_hcd 0000:00:1d.0: suspend_hc
uhci_hcd 0000:00:1d.1: suspend_hc
uhci_hcd 0000:00:1d.2: suspend_hc
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00004c020000002d]

Capture in Kino apparently works, but pressing the AV/C button (which wor=
ked
with kernel 2.4.x) hangs the whole Kino process and makes it unkillable u=
ntil
I turn the camera off.

"cardctl eject" makes the kernel try dereferencing a NULL pointer.  That
was also the case for 2.6.10, but I didn't even try Kino there.  Here are
the rest of the dmesg entries related to firewire.  I guess that the firs=
t
few entries are related to turning the camera on and trying the AV/C cont=
rols
in Kino.

ieee1394: Error parsing configrom for node 0-00:1023
ieee1394: Error parsing configrom for node 0-01:1023
ieee1394: The root node is not cycle master capable; selecting a new root=
 node and resetting...
ieee1394: Node added: ID:BUS[0-00:1023]  GUID[0080880000f134e6]
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
ieee1394: raw1394: /dev/raw1394 device initialized
ohci1394: fw-host0: AT dma reset ctx=3D0, aborting transmission
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node suspended: ID:BUS[0-00:1023]  GUID[0080880000f134e6]
ieee1394: Node removed: ID:BUS[0-00:1023]  GUID[00004c020000002d]
ieee1394: Node removed: ID:BUS[0-00:1023]  GUID[0080880000f134e6]
Unable to handle kernel NULL pointer dereference at virtual address 00000=
000
 printing eip:
d0a03bdb
*pde =3D 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in: raw1394 dv1394 joydev evdev ohci1394 ieee1394 ehci_hcd=
 uhci_hcd rtc parport_pc parport
CPU:    0
EIP:    0060:[<d0a03bdb>]    Not tainted VLI
EFLAGS: 00010296   (2.6.11.1)
EIP is at dv1394_remove_host+0x1b/0xe0 [dv1394]
eax: d092b688   ebx: 00000000   ecx: 00000000   edx: d0a03bc0
esi: 00000000   edi: d0a0459d   ebp: cf231e84   esp: ce9c7e6c
ds: 007b   es: 007b   ss: 0068
Process cardctl (pid: 3459, threadinfo=3Dce9c7000 task=3Dcb9ee550)
Stack: cf6698d4 d0a06040 cf230000 cf230000 cf231e84 d0915331 00000000 cf2=
31e84
       d0914df0 00000000 d0a06040 d0a06040 cf230000 d092b6bc cf231e84 d09=
15d7b
       cf230000 c1377044 d08de4c8 d0914c98 c1377000 d08da3a3 c0316aca cf2=
31d2c
Call Trace:
 [<d0915331>] __unregister_host+0xd1/0xe0 [ieee1394]
 [<d0914df0>] hl_get_hostinfo+0x70/0x90 [ieee1394]
 [<d0915d7b>] highlevel_remove_host+0x3b/0x70 [ieee1394]
 [<d0914c98>] hpsb_remove_host+0x38/0x60 [ieee1394]
 [<d08da3a3>] ohci1394_pci_remove+0x53/0x210 [ohci1394]
 [<c01b6548>] pci_device_remove+0x28/0x30
 [<c021a7a4>] device_release_driver+0x74/0x80
 [<c021a9e4>] bus_remove_device+0x54/0x90
 [<c02198ca>] device_del+0x5a/0xa0
 [<c0219918>] device_unregister+0x8/0x10
 [<c01b42f7>] pci_destroy_dev+0x17/0x90
 [<c01b4478>] pci_remove_behind_bridge+0x28/0x40
 [<c0251428>] shutdown_socket+0x58/0xa0
 [<c01228af>] msleep+0x2f/0x40
 [<c02515bb>] socket_shutdown+0x1b/0x30
 [<c0251a98>] socket_remove+0x8/0x70
 [<c0253652>] pcmcia_eject_card+0x62/0x70
 [<c0257a64>] ds_ioctl+0x224/0x590
 [<c01638ca>] do_ioctl+0x6a/0x90
 [<c0163afe>] vfs_ioctl+0x5e/0x1d0
 [<c0163cad>] sys_ioctl+0x3d/0x70
 [<c010306f>] syscall_call+0x7/0xb
Code: 3c 92 73 ef 8b 5c 24 38 83 c4 3c c3 8d 74 26 00 55 57 bf 9d 45 a0 d=
0 56 53 83 ec 04 8b 98 28 1d 00 00 8b 80 20 1d 00 00 8b 70 04 <ac> ae 75 =
08 84 c0 75 f8 31 c0 eb 04 19 c0 0c 01 85 c0 0f 85 7e

Please let me know if you would like to have further tests.  If I remembe=
r
correctly, I got that "cardctl eject" failure with 2.6.10 even without
plugging in the camera.

Best regards,

	Marko