From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-media@vger.kernel.org
Subject: Re: ivtv driver inputs randomly "block"
Date: Wed, 28 Nov 2012 18:19:36 -0500 [thread overview]
Message-ID: <50B69C08.7050401@interlinx.bc.ca> (raw)
In-Reply-To: <CALF0-+UHOJDh471aa7URKr1-xbggrbDdg_nDijv2FOUpo=3zaw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
On 12-11-28 08:13 AM, Ezequiel Garcia wrote:
>
> Try again with
> modprobe ivtv ivtv_debug=10
OK. Happened again. The kernel log for the whole day since starting
the module with debug this morning can be found at
http://brian.interlinx.bc.ca/ivtv-dmesg.txt.bz2.
Associated with that log there was a successful recording from 09:00:00
until 10:00:00 then another successful recording from 14:00:00 until
15:00:00 and then failed recordings starting at 15:00:00 until 18:00:00.
The log cuts off just short of 18:00:00 but there's nothing different
about the pattern from the end of the log until 18:00:04 from the
previous 3 hours or so.
It seems that the problem lies in amongst the start of these lines from
the log, as my best guess:
Nov 28 15:00:05 cmurrell kernel: [868297.536049] ivtv0 encoder MPG: VIDIOC_ENCODER_CMD cmd=0, flags=0
Nov 28 15:00:07 cmurrell kernel: [868300.039324] ivtv0: ioctl: V4L2_ENC_CMD_STOP
Nov 28 15:00:07 cmurrell kernel: [868300.039330] ivtv0: info: close stopping capture
Nov 28 15:00:07 cmurrell kernel: [868300.039334] ivtv0: info: Stop Capture
Nov 28 15:00:09 cmurrell kernel: [868302.140151] ivtv0 encoder MPG: VIDIOC_ENCODER_CMD cmd=1, flags=1
Nov 28 15:00:09 cmurrell kernel: [868302.148093] ivtv0: ioctl: V4L2_ENC_CMD_START
Nov 28 15:00:09 cmurrell kernel: [868302.148101] ivtv0: info: Start encoder stream encoder MPG
Nov 28 15:00:09 cmurrell kernel: [868302.188580] ivtv0: info: Setup VBI API header 0x0000bd03 pkts 1 buffs 4 ln 24 sz 1456
Nov 28 15:00:09 cmurrell kernel: [868302.188655] ivtv0: info: Setup VBI start 0x002fea04 frames 4 fpi 1
Nov 28 15:00:09 cmurrell kernel: [868302.191952] ivtv0: info: PGM Index at 0x00180150 with 400 elements
Nov 28 15:00:10 cmurrell kernel: [868302.544052] ivtv0 encoder MPG: VIDIOC_ENCODER_CMD cmd=0, flags=0
Nov 28 15:00:12 cmurrell kernel: [868305.047260] ivtv0: ioctl: V4L2_ENC_CMD_STOP
Nov 28 15:00:12 cmurrell kernel: [868305.047265] ivtv0: info: close stopping capture
Nov 28 15:00:12 cmurrell kernel: [868305.047270] ivtv0: info: Stop Capture
...
FWIW, the recording software here is MythTV completely up to date on the
0.25-fixes branch.
Thoughts?
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next prev parent reply other threads:[~2012-11-28 23:19 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 [this message]
[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
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=50B69C08.7050401@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 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.