From: Malcolm Priestley <tvboxspy@gmail.com>
To: Josu Lazkano <josu.lazkano@gmail.com>
Cc: Jason Hecker <jwhecker@gmail.com>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] af9013 Extended monitoring in set_frontend.
Date: Sat, 08 Oct 2011 14:26:02 +0100 [thread overview]
Message-ID: <4e904f71.ce66e30a.69f3.ffff9870@mx.google.com> (raw)
In-Reply-To: <CAL9G6WWMw3npqjt0WHGhyjaW5Mu=1jA5Y_QduSr3KudZTKLgBw@mail.gmail.com>
On Sat, 2011-10-08 at 15:13 +0200, Josu Lazkano wrote:
> 2011/10/8 Jason Hecker <jwhecker@gmail.com>:
> >> Try this patch, it should stop start up corruption on the same frontend.
> >
> > Thanks. I'll try it today.
> >
> > Have you been able to reproduce any of the corruption issues I and
> > others are having?
> >
> > I noticed last night some recordings on the same card had different
> > levels of corruption depending on the order of tuning
> >
> > Tuner A then tuner B : Tuner A was heavily corrupted. Tuner B was a fine.
> > Tuner B then tuner A: Tuner A had a small corruption every few seconds
> > and the show was watchable, Tuner B was fine.
> >
>
> Thanks again, I try the patch and it works well last nigh. This
> morning one tuner is getting pixeled images and the other can not
> LOCK.
>
> This is the kernel messages:
>
> # tail /var/log/messages
> Oct 8 14:16:06 htpc kernel: [45025.328902] mxl5005s I2C write failed
> Oct 8 14:16:06 htpc kernel: [45025.333147] mxl5005s I2C write failed
> Oct 8 14:16:06 htpc kernel: [45025.333637] mxl5005s I2C write failed
> Oct 8 14:16:06 htpc kernel: [45025.490524] mxl5005s I2C write failed
> Oct 8 14:16:06 htpc kernel: [45025.491014] mxl5005s I2C write failed
> Oct 8 14:16:08 htpc kernel: [45027.642858] mxl5005s I2C write failed
> Oct 8 14:16:08 htpc kernel: [45027.647477] mxl5005s I2C write failed
> Oct 8 14:16:08 htpc kernel: [45027.647970] mxl5005s I2C write failed
> Oct 8 14:16:09 htpc kernel: [45027.806477] mxl5005s I2C write failed
> Oct 8 14:16:09 htpc kernel: [45027.806969] mxl5005s I2C write failed
>
> I try to increase the signal timeout from 1000 to 2000 ms and the
> tuning timeout from 3000 to 6000 ms on mythbackend.
>
I have left these at the default settings
Which kernels are you all running?
uname -rv
I think replicate your systems on my test pc.
next prev parent reply other threads:[~2011-10-08 13:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4e83369f.5d6de30a.485b.ffffdc29@mx.google.com>
2011-10-04 19:28 ` [PATCH] af9013 frontend tuner bus lock Josu Lazkano
2011-10-04 20:44 ` Jason Hecker
2011-10-04 21:54 ` Malcolm Priestley
2011-10-04 22:10 ` Jason Hecker
2011-10-05 11:40 ` Josu Lazkano
2011-10-05 22:19 ` Jason Hecker
2011-10-05 23:12 ` Josu Lazkano
2011-10-06 2:39 ` Jason Hecker
2011-10-06 20:07 ` dave cunningham
2011-10-06 21:48 ` Josu Lazkano
2011-10-06 22:34 ` Jason Hecker
2011-10-06 21:13 ` Malcolm Priestley
2011-10-07 21:11 ` [PATCH] af9013 Extended monitoring in set_frontend Malcolm Priestley
2011-10-07 22:46 ` Jason Hecker
2011-10-08 13:10 ` Malcolm Priestley
2011-10-08 13:13 ` Josu Lazkano
2011-10-08 13:26 ` Malcolm Priestley [this message]
2011-10-08 13:42 ` Josu Lazkano
2011-10-08 14:06 ` Antti Palosaari
2011-10-08 20:05 ` Jason Hecker
2011-10-10 19:31 ` Antti Palosaari
2011-10-10 20:27 ` Malcolm Priestley
2011-10-10 21:06 ` Jason Hecker
2011-10-16 20:26 ` Malcolm Priestley
2011-10-16 21:18 ` Jason Hecker
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=4e904f71.ce66e30a.69f3.ffff9870@mx.google.com \
--to=tvboxspy@gmail.com \
--cc=josu.lazkano@gmail.com \
--cc=jwhecker@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 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.