Hi *,
I'm using tvheadend on a raspberry pi with both a DVB-T (rtl28xxu based) as well as a DVB-S (DVBSky S2¹) device.
I tried the latest kernel (3.16.0-2 at the time) and found that both DVB-T as well as DVB-S are unusable/unwatchable since there are lots of Continuity Errors reported (and also visible glitches and dropouts en masse). The problem is not weak signal/bad hardware, since using kernel 3.12 (3.12.26-1 as of now) doesn't show the problem - with that kernel both adapters give flawless stream without errors.
My assumption is that buffers cannot be read fast enough from the driver, i.e. while the driver/hardware does receive the packets, they're not passed down to the client application properly.
As both DVB-T as well as DVB-S are affected, I exclude a problem with the DVBSky driver that is partially binary-only - the rtl28xxu one is one of the most common chips I think. And as the only difference between working and non-working, some changes in the kernel are to blame.
But of course the big question is how to narrow this down to get some usable bug-report? Do other users suffer the same problem/is it limited to the raspberry maybe?)
[1] driver from here http://www.dvbsky.net/Support.html - sit2.o for <strike>arch</strike> arm quickly received after mailing support
Edit: sit2.o for *arm*