From: Andy Furniss <adf.lists@gmail.com>
To: Rainer Dorsch <ml@bokomoko.de>
Cc: linux-media@vger.kernel.org
Subject: Re: Pinnacle PCTV DVB-S2 Stick (461e) - HD Streams with artefacts
Date: Sun, 17 Jan 2016 10:27:15 +0000 [thread overview]
Message-ID: <569B6C83.5080104@gmail.com> (raw)
In-Reply-To: <2761448.7zDNhWqk2x@blackbox>
Rainer Dorsch wrote:
>>> Certainly any hint how to solve this issue is welcome.
>>
>> I added a comment on the tvh forum - will paste here as well in
>> case anyone is interested -
>>
>> You could try spinning up you cpu(s) with
>>
>> nice -19 dd if=/dev/urandom of=/dev/null
>
> I added four of these, but if at all then there was only a minor
> impact.
Oh, OK it was worth a try.
>> If you have multiple cores maybe start more than one.
>>
>> I have a couple of DVB-T2 PCTV sticks and got some usb/power
>> save/xhci issues on my h/w.
>>
>> Above would mostly fix. Rather than do that I found that the issue
>> was far less if I disabled USB3 in bios to avoid using the xhci
>> driver.
>
> The cubox-i has no USB 3 port and no bios :-/
Ahh, quite different h/w then. Mine was a quad core baytrail DC board.
>> Of course your issue may be totally different - but it's worth a
>> try.
>
>> Your symptoms do point to ts packet loss - which I know from my
>> experience can be at usb level. There are posts on here from the
>> past where people with PCIE cards also had to do similar.
>
> Sounds reasonable. Can I enable logs which would make these drops
> explicit?
Not that I know of at kernel level. The only way really is to infer loss
from the continuity counters, which TVH already logs.
next prev parent reply other threads:[~2016-01-17 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-16 22:03 Pinnacle PCTV DVB-S2 Stick (461e) - HD Streams with artefacts Rainer Dorsch
2016-01-16 23:16 ` Andy Furniss
2016-01-16 23:43 ` Rainer Dorsch
2016-01-17 10:27 ` Andy Furniss [this message]
2016-01-17 22:12 ` Rainer Dorsch
2016-01-17 23:07 ` Andy Furniss
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=569B6C83.5080104@gmail.com \
--to=adf.lists@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=ml@bokomoko.de \
/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.