From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-media@vger.kernel.org
Subject: Re: ivtv driver inputs randomly "block"
Date: Thu, 29 Nov 2012 10:53:32 -0500 [thread overview]
Message-ID: <50B784FC.1080904@interlinx.bc.ca> (raw)
In-Reply-To: <CALF0-+XStqJEiPaQjrBu74of9BYRJZS-9F6F7YzgE3LU6x+TVQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]
On 12-11-29 10:29 AM, Ezequiel Garcia wrote:
> Hi Brian,
Hi Garcia,
> Mmm, the log shows this repeating pattern:
>
> ---
> Nov 28 17:54:46 cmurrell kernel: [878779.229702] ivtv0: info: Setup
> VBI start 0x002fea04 frames 4 fpi 1
> Nov 28 17:54:46 cmurrell kernel: [878779.233129] ivtv0: info: PGM
> Index at 0x00180150 with 400 elements
> Nov 28 17:54:47 cmurrell kernel: [878779.556039] ivtv0 encoder MPG:
> VIDIOC_ENCODER_CMD cmd=0, flags=0
> Nov 28 17:54:49 cmurrell kernel: [878782.059204] ivtv0: ioctl:
> V4L2_ENC_CMD_STOP
> Nov 28 17:54:49 cmurrell kernel: [878782.059209] ivtv0: info: close
> stopping capture
> Nov 28 17:54:49 cmurrell kernel: [878782.059214] ivtv0: info: Stop Capture
> Nov 28 17:54:51 cmurrell kernel: [878784.156135] ivtv0 encoder MPG:
> VIDIOC_ENCODER_CMD cmd=1, flags=1
> Nov 28 17:54:51 cmurrell kernel: [878784.166157] ivtv0: ioctl:
> V4L2_ENC_CMD_START
> Nov 28 17:54:51 cmurrell kernel: [878784.166165] ivtv0: info: Start
> encoder stream encoder MPG
Yes, as I indicated.
> And from 15:00 to 18:00 recording fails?
Yes.
> Perhaps it would make sense to restart application upon driver failure,
> now that output is more verbose.
Meaning what exactly? Restart MythTV? How would I restart MythTV when
the failure occurs? Do you mean like having a daemon watching dmesg
that restarts MythTV when this happens? That's a very ugly hack-around
that will have negative side effects per below...
This failure doesn't necessarily affect all tuners at the same time so I
would potentially be restarting MythTV while other tuners are recording,
interrupting good recordings to fix one tuner which is having a problem.
I am sure you would agree that this is not really a suitable
work-around, yes?
> PS: Please don't drop linux-media list from Cc
I don't think I did. All of my messages have been copied to the list,
albeit I post them through gmane rather than posting to the list
directly since I read via gmane and am not a direct subscriber to the
list. Most lists will disallow postings by non-subscribers. I know
vger.kernel.org does allow posting by non-subscribers on at least some
of their lists but I am not aware of it being a site-wide policy or not
so to be on the safe side I just let gmane post it to the list.
Perhaps you got the copy I CC'd to you directly before you got the copy
that went to the list via gmane.
Cheers,
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next prev parent reply other threads:[~2012-11-29 15:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 3:20 ivtv driver inputs randomly "block" Brian J. Murrell
2012-11-28 13:08 ` Ezequiel Garcia
2012-11-28 13:10 ` Brian J. Murrell
2012-11-28 13:13 ` Ezequiel Garcia
2012-11-28 13:34 ` Brian J. Murrell
2012-11-28 23:19 ` Brian J. Murrell
[not found] ` <CALF0-+X0yyQEw+jJCxuQO18gDagtyX-RZW_kurMPS69RQHNPMA@mail.gmail.com>
2012-11-29 15:29 ` Ezequiel Garcia
2012-11-29 15:50 ` Andy Walls
2012-11-29 16:12 ` Brian J. Murrell
2012-11-29 19:47 ` Brian J. Murrell
2012-12-02 19:50 ` Brian J. Murrell
2012-12-05 14:12 ` Brian J. Murrell
2012-11-29 15:53 ` Brian J. Murrell [this message]
2012-11-29 16:40 ` Ezequiel Garcia
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=50B784FC.1080904@interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--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;
as well as URLs for NNTP newsgroup(s).