Re: sorta solved: "AVC Status: Unknown state" on recent kernels

PreScriptum: is it acceptable on kino-dev@ or should I subscribe
to another ML? (what's lucky for me might be spam for others as
the issue at hand doesn't relate to kino as has been shown)


On Mon, Oct 31, 2011 at 01:05:16PM +0100, Stefan Richter wrote:
> > It's Canon MVX-25i;
> Reviews on the web indicate that this is a model from 2004.  I
> have got a Canon MV5i MC which appears to be a model from 2002.
[...]
> All in all it looks very similar to what you describe.

Yup; well at least there's the locally reproducible case.

> > dmesg:
> So that looks pretty standard for this sort of device.
> On one out of six occasions I had "created device fw9:
> GUID 00008500005c16a7, S100, 1 config ROM retries" like yours.

Hm, this one seems to differ:

$ dmesg | grep firewire
[    7.822220] firewire_ohci 0000:01:07.0: PCI INT A -> Link[APC2] -> GSI 17 (level, low) -> IRQ 17
[    7.884112] firewire_ohci: Added fw-ohci device 0000:01:07.0, OHCI v1.0, 4 IR + 8 IT contexts, quirks 0x11
[    7.884359] firewire_ohci 0000:01:0e.0: PCI INT A -> Link[APC3] -> GSI 18 (level, low) -> IRQ 18
[    7.940124] firewire_ohci: Added fw-ohci device 0000:01:0e.0, OHCI v1.10, 4 IR + 8 IT contexts, quirks 0x2
[    8.384212] firewire_core: created device fw0: GUID 4d5a900003000000, S400
[    8.440203] firewire_core: created device fw1: GUID 000fea000060c6e6, S400
[  210.747460] firewire_core: skipped bus generations, destroying all nodes
[  211.244078] firewire_core: rediscovered device fw1
[  211.244090] firewire_core: giving up on config rom for node id ffc0
[  214.383938] firewire_core: skipped bus generations, destroying all nodes
[  214.880083] firewire_core: rediscovered device fw1
[  214.880101] firewire_core: phy config: card 1, new root=ffc1, gap_count=5
[  219.907652] firewire_core: created device fw2: GUID 0000850000a1eb41, S100, 1 config ROM retries
[ 2880.652123] firewire_core: skipped bus generations, destroying all nodes
[ 2881.152093] firewire_core: rediscovered device fw1
[ 2881.152116] firewire_core: giving up on config rom for node id ffc1
[ 2884.290444] firewire_core: skipped bus generations, destroying all nodes
[ 2884.788047] firewire_core: rediscovered device fw1
[ 2884.788063] firewire_core: phy config: card 1, new root=ffc1, gap_count=5
[ 2889.819376] firewire_core: created device fw2: GUID 0000850000a1eb41, S100, 1 config ROM retries
[ 5006.824883] firewire_core: skipped bus generations, destroying all nodes
[ 5007.324110] firewire_core: rediscovered device fw1
[ 5007.324132] firewire_core: giving up on config rom for node id ffc1

> Said said, I suppose I should tag a new release sometime soon.
> But before that, I still want to look into some old issue
> reports and old proposed patches and commit the low-hanging
> fruit (if there are ones among them).

Of course!  Postponing the known things for the chance to
bundle not-quite-diagnosed problem fixes isn't that effective,
and I'm more than willing to test git builds.

> Also I need to see whether I can reinstate the libraw1394
> repository and tarball http/ftp download directory at
> kernel.org (a) in a reasonable time frame and (b) at the very
> same URLs as before the kernel.org compromise and downtime.

Seems like it's a "not-quite-predictable" thing so far.

> OK, so you and I can look into that independently.  For example,
> firewire-ohci's debug logging might perhaps show something interesting
> (echo 3 > /sys/module/firewire_ohci/parameters/debug).

Thanks, I'll try to get back to this as the hardware's back.

> > Is the "giving up on config rom" appearing above the definite
> > sign of the problem described in aaff120?  That is, what's up
> > with that message followed by kino being able to capture?
> In this case it is only a temporary glitch:  The camcorder
> signals by its self-identification packet that its link layer
> is ready, so the kernel begins to probe it; but in fact isn't
> ready.  When the camcorder brought everything up for real three
> seconds later, it issues another bus reset and the kernel
> succeeds to probe the camcorder's config ROM now, evident by
> the "created device" message and /dev/fw* showing up in the
> filesystem.

Thank you for the explanation.  I used to solder my own stuff
some twenty years ago but that was purely analog one...

-- 
 ---- WBR, Michael Shigorin <[email protected]>
  ------ Linux.Kiev http://www.linux.kiev.ua/

------------------------------------------------------------------------------
Get your Android app more play: Bring it to the BlackBerry PlayBook 
in minutes. BlackBerry App World&#153; now supports Android&#153; Apps 
for the BlackBerry&reg; PlayBook&#153;. Discover just how easy and simple 
it is! http://p.sf.net/sfu/android-dev2dev