public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Lord <kernel@teksavvy.com>
To: Andy Walls <awalls@radix.net>
Cc: Mark Lord <kernel@teksavvy.com>,
	Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media@vger.kernel.org, ivtv-devel@ivtvdriver.org
Subject: cx18: "missing audio" for analog recordings
Date: Sun, 14 Mar 2010 22:48:35 -0400	[thread overview]
Message-ID: <4B9DA003.90306@teksavvy.com> (raw)
In-Reply-To: <1267533630.3123.17.camel@palomino.walls.org>

On 03/02/10 07:40, Andy Walls wrote:
> Again, maybe dynamically allocating these work order objects from the
> kernel as needed, would be better from a small dynamically allocated
> pool for each card.  I was concerned that the interrupt handler was
> taking to long at the time I implemented the things the way they are
> now.
..

I haven't seen that particular issue again, with or without increasing
the work orders, so hopefully it won't recur.

But after updating to the tip of the v4l2-dvb git tree last week,
I've been hitting the "no audio" on analog recordings bug much more often.

Digging through google, it appears this problem has been around as long
as the cx18 driver has existed, with no clear resolution.  Lots of people
have reported it to you before, and nobody has found a silver bullet fix.

The problem is still there.

I have now spent a good many hours trying to isolate *when* it happens,
and have narrowed it down to module initialization.

Basically, if the audio is working after modprobe cx18, it then continues
to work from recording to recording until the next reboot.

If the audio is not working after modprobe, then simply doing rmmod/modprobe
in a loop (until working audio is achieved) is enough to cure it.

So for my Mythtv box here, I now have a script to check for missing audio
and do the rmmod/modprobe.  This is a good, effective workaround.

    http://rtr.ca/hvr1600/fix_hvr1600_audio.sh

That's a link to my script.

As for the actual underlying cause/bug, it's still not clear what is happening.
But the problem is a LOT more prevalent (for me, and for two other people I know)
with versions of the cx18 driver since spring 2009.

My suspicion is that the firmware download for the APU is somehow being corrupted,
and now that the driver downloads the firmware *twice* during init, it doubles the
odds of said corruption.  Just a theory, but it's the best fit so far.

I think we have some nasty i2c issues somewhere in the kernel.

Cheers

  parent reply	other threads:[~2010-03-15  2:48 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 16:07 cx18: Unable to find blank work order form to schedule incoming mailbox Mark Lord
2010-03-02  1:34 ` Andy Walls
2010-03-02  5:57   ` Mark Lord
2010-03-02 12:40     ` Andy Walls
2010-03-02 15:00       ` Mark Lord
2010-03-03  1:05         ` Andy Walls
2010-03-15  2:48       ` Mark Lord [this message]
2010-03-15 11:51         ` cx18: "missing audio" for analog recordings Andy Walls
2010-03-16  4:49           ` Mark Lord
2010-03-16 11:11             ` Andy Walls
2010-04-10 22:28           ` Mark Lord
2010-04-10 22:54             ` Andy Walls
2010-04-11  0:58               ` Andy Walls
2010-04-11  3:21               ` Mark Lord
2010-04-11  4:56                 ` Andy Walls
2010-04-11  5:03                   ` [ivtv-devel] " Andy Walls
2010-04-11 11:47                   ` Andy Walls
2010-04-11 13:24                     ` Mark Lord
2010-04-11 19:01                       ` Andy Walls
2010-04-11 20:52                         ` Mark Lord
2010-04-12 20:08                         ` Mark Lord
2010-04-12 21:17                           ` Andy Walls
2010-04-13  2:22                             ` Mark Lord
2010-04-13  2:30                               ` Mark Lord
2010-04-13  2:34                                 ` Mark Lord
2010-04-13 10:35                                   ` Andy Walls
2010-04-13 12:42                                     ` Mark Lord
2010-04-14  1:45                                       ` Andy Walls
2010-04-14  4:32                                         ` Mark Lord
2010-04-14  4:34                                           ` Mark Lord
2010-04-14 22:26                                           ` Mark Lord
2010-04-15  4:46                                             ` Andy Walls
2010-04-15  5:16                                               ` Mark Lord
2010-04-15 14:15                                                 ` Mark Lord
2010-04-17  4:43                                                   ` Andy Walls
2010-04-17 12:09                                                     ` Mark Lord
2010-04-17 13:01                                                       ` Mark Lord
2010-04-17 17:18                                                         ` Andy Walls
2010-04-17 17:03                                                       ` Andy Walls
2010-04-16 12:59                                                 ` Andy Walls
2010-04-17 12:18                                                   ` Mark Lord
2010-04-17 17:37                                                     ` Andy Walls
2010-04-16 13:15                                           ` Andy Walls
2010-04-16 13:29                                             ` Andy Walls
2010-04-11 19:49                   ` Darren Blaber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B9DA003.90306@teksavvy.com \
    --to=kernel@teksavvy.com \
    --cc=awalls@radix.net \
    --cc=hverkuil@xs4all.nl \
    --cc=ivtv-devel@ivtvdriver.org \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox