On Sat, 2011-10-08 at 15:13 +0200, Josu Lazkano wrote:
> 2011/10/8 Jason Hecker <jwhec...@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.

--
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

Reply via email to