On Thu, 2012-11-29 at 12:29 -0300, Ezequiel Garcia wrote:
> Hi Brian,
>
> See my comments below.
>
> On Wed, Nov 28, 2012 at 8:19 PM, Brian J. Murrell <br...@interlinx.bc.ca>
> wrote:
> > 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?
> >
>
> 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
> ---
>
> And from 15:00 to 18:00 recording fails?
>
> Perhaps it would make sense to restart application upon driver failure,
> now that output is more verbose.
Hi Ezequiel,
Nope. IIRC, that's just MythTV timing-out, closing the device node, and
reopening the device node, in attempt to make things work again.
Hi Brian,
I haven't checked the log you provided yet, but you'll likely need to
set the module debug flags a little more verbose.
/sbin/modinfo ivtv | less
[...]
parm: debug:Debug level (bitmask). Default: 0
1/0x0001: warning
2/0x0002: info
4/0x0004: mailbox
8/0x0008: ioctl
16/0x0010: file
32/0x0020: dma
64/0x0040: irq
128/0x0080: decoder
256/0x0100: yuv
512/0x0200: i2c
1024/0x0400: high volume
[..]
So maybe as root
# echo 0x07f > /sys/module/ivtv/parameters/debug
until the problem appears. Then once you experience the problem change
it to high volume
# echo 0x47f > /sys/module/ivtv/parameters/debug
You may want to also get a baseline of what a good capture looks like
using high volume debugging. Be aware that high volume debugging will
fill up your logs and degrade performance a little, so you don't want to
normally use high volume debugging.
> Regards,
>
> Ezequiel
>
> PS: Please don't drop linux-media list from Cc
+1
The ideas or interest of one individual often spurs that of others.
Regards,
Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
