From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: Andy Walls <awalls@md.metrocast.net>
Cc: Ezequiel Garcia <elezegarcia@gmail.com>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: ivtv driver inputs randomly "block"
Date: Thu, 29 Nov 2012 11:12:06 -0500 [thread overview]
Message-ID: <50B78956.1060101@interlinx.bc.ca> (raw)
In-Reply-To: <1354204218.2505.13.camel@palomino.walls.org>
[-- Attachment #1: Type: text/plain, Size: 2396 bytes --]
On 12-11-29 10:50 AM, Andy Walls wrote:
>
> 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.
Seems a very reasonable explanation.
> Hi Brian,
Hi Andy,
> I haven't checked the log you provided yet, but you'll likely need to
> set the module debug flags a little more verbose.
OK.
> /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
Will waiting for MythTV to report an error, such as:
MPEGRec(/dev/video1): Device error detected
be too late to turn up debugging or should that be sufficient enough timing?
Although, MythTV seems to report that error at the end of every
recording so I'm not sure how I will filter out the false reports --
unless I write a smarter (i.e. than a single line match) log watcher.
Anyway, that's my problem, not yours. :-)
> # 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.
Just did that. Reduced to 0x07f after about a minute and 23 seconds.
> 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.
Indeed, it's quite verbose.
> +1
>
> The ideas or interest of one individual often spurs that of others.
Indeed, I always keep list replies on list and as I mentioned to
Ezequiel (sorry Ezequiel, I got your name wrong on my previous post. my
apologies) and I am seeing the copies -- but through gmane. I don't see
the copies on the spincs.net archive. I suspect there is a lag at gmane
posting to the list.
In any case, I have CC'd this one directly to the list @vger.kernel.org
and will just hope it has an open posting policy.
Cheers and thanks much!
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next prev parent reply other threads:[~2012-11-29 16:12 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 [this message]
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=50B78956.1060101@interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--cc=awalls@md.metrocast.net \
--cc=elezegarcia@gmail.com \
--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).