Re: HV30 and grabbing in 3.16.0-31

[Stefan R. <st...@s5...>]

On Mar 02 Elias Aarnio wrote:
> After booting the machine with the PCMCIA card installed, removed it,
> plugged it in again:
> 
> Syslog:
> 
> Mar  2 12:14:19 nakka-ThinkPad-T60 kernel: [  322.780636] firewire_ohci 0000:16:00.0: removed fw-ohci device
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  325.952178] pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  325.952218] pci 0000:16:00.0: [1106:3044] type 00 class 0x0c0010
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  325.952258] pci 0000:16:00.0: reg 0x10: [mem 0x00000000-0x000007ff]
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  325.952278] pci 0000:16:00.0: reg 0x14: [io  0x0000-0x007f]
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  325.952297] pci 0000:16:00.0: reg 0x18: [mem 0x00000000-0x000000ff]
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  325.952415] pci 0000:16:00.0: supports D2
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  325.952422] pci 0000:16:00.0: PME# supported from D2 D3hot D3cold
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  325.952660] pci 0000:16:00.0: BAR 0: assigned [mem 0x84000000-0x840007ff]
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  325.952675] pci 0000:16:00.0: BAR 2: assigned [mem 0x84000800-0x840008ff]
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  325.952689] pci 0000:16:00.0: BAR 1: assigned [io  0xa000-0xa07f]
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  325.952829] firewire_ohci 0000:16:00.0: enabling device (0080 -> 0083)
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  326.016152] firewire_ohci 0000:16:00.0: added OHCI v1.10 device as card 4, 4 IR + 8 IT contexts, quirks 0x41
> Mar  2 12:14:23 nakka-ThinkPad-T60 kernel: [  326.516427] firewire_core 0000:16:00.0: created device fw0: GUID 00111666123403bc, S400

This appears to be the VT6306 card.

(I have a VT6306 based CardBus Card too but it is configured to OHCI 1.0
mode by the card manufacturer.  However OHCI 1.1 versus 1.0 is not of
importance to the matter at hand.)

> Then I plugged in the camera cable and switched camera on:
> 
> Mar  2 12:14:46 nakka-ThinkPad-T60 kernel: [  349.240209] firewire_core 0000:16:00.0: rediscovered device fw0
> Mar  2 12:14:47 nakka-ThinkPad-T60 kernel: [  350.556151] firewire_core 0000:16:00.0: rediscovered device fw0
> Mar  2 12:14:48 nakka-ThinkPad-T60 kernel: [  351.864169] firewire_core 0000:16:00.0: rediscovered device fw0
> 
> This last line keeps getting repeated once in a second, endlessly.
> 
> Any thoughts?

Normally, when a device is plugged in/ switched on, there are two or three
bus resets or so and then the bus becomes operational, firewire-core
queries the node for its type, and then higher-level software can take
over.

You however get a never ending series of bus resets.  These could be
caused by a hardware defect --- e.g. burnt out port or loose port at the
camcorder; worn out plug at the cable or broken wire or bad shielding of
the cable; worn out or desoldered port at the card; etc..

Or it could be firmware fighting against core driver:  firewire-core
assumes certain bus management duties, and these involve
software-initiated bus resets.  We had cases in the past where device
firmware undid the bus configurations that firewire-core attempted to
establish, and device and firewire-core repeatedly reset the bus.

In order to learn more whether it could be a firmware <-> driver issue,
please attempt again with some event logging switched on in firewire-ohci:
When firewire-ohci is already loaded, but before the camcorder is plugged
in/ switched on, issue the following command:

  sudo dd of=/sys/module/firewire_ohci/parameters/debug <<< 3

The plug in/ switch on the camcorder (shouldn't matter whether you first
plug it in and then switch it on, or the other way around; but you can of
course try both sequences), watch what is being logged in the kernel log,
and post the log here.

You can tell firewire-ohci to stop the debug logging any time by the same
command as above but with 0 as parameter.
-- 
Stefan Richter
-=====-===== --== ---=-
http://arcgraph.de/sr/