From: Hans Verkuil <hverkuil@xs4all.nl>
To: James Harper <james@ejbdigital.com.au>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: buffer delivery stops with cx23885
Date: Mon, 22 Sep 2014 11:52:42 +0200 [thread overview]
Message-ID: <541FF16A.9060902@xs4all.nl> (raw)
In-Reply-To: <01776abac53640498b8fc87ac8d36fd1@HKXPR04MB295.apcprd04.prod.outlook.com>
On 09/22/2014 11:46 AM, James Harper wrote:
>>
>>>
>>> Any hints on what I can do to figure out what layer it's stalling at?
>>
>> I have no idea. I would do a git bisect to try and narrow it down.
>>
>
> Problem with the bisect is that I can't be sure what version it actually worked on. It certainly predates when my patch for my card was committed.
>
> I have a hunch that it might be the two tuners stomping on each other, possibly in the i2c code. Sometimes recording just stops, other times I get i2c errors.
Is that two tuners in the same device, or two tuners in different devices?
Hans
>
> With one tuner disabled in MythTV I can't seem to reproduce the problem anymore. I haven't let it run for long enough to be sure, but it normally would have crashed by now.
>
> James
next prev parent reply other threads:[~2014-09-22 9:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 3:32 buffer delivery stops with cx23885 James Harper
2014-09-20 9:19 ` Hans Verkuil
2014-09-20 9:26 ` James Harper
2014-09-20 10:03 ` Mauro Carvalho Chehab
2014-09-20 10:08 ` Hans Verkuil
2014-09-20 10:30 ` James Harper
2014-09-20 10:54 ` Hans Verkuil
2014-09-20 11:05 ` James Harper
2014-09-20 11:15 ` Hans Verkuil
2014-09-20 11:36 ` James Harper
2014-09-21 8:15 ` James Harper
2014-09-22 8:30 ` James Harper
2014-09-22 8:37 ` Hans Verkuil
2014-09-22 9:46 ` James Harper
2014-09-22 9:52 ` Hans Verkuil [this message]
2014-09-22 9:58 ` James Harper
2014-09-22 10:03 ` Hans Verkuil
2014-09-22 12:01 ` James Harper
2014-09-29 9:06 ` James Harper
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=541FF16A.9060902@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=james@ejbdigital.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.