linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Hutchinson <jahutchinson99@googlemail.com>
To: linux-media@vger.kernel.org, crazycat69@narod.ru,
	mchehab@s-opensource.com
Subject: MyGica T230 dvb-t2 data corruption since commit 5fa8815
Date: Wed, 17 Jul 2019 08:44:33 +0100	[thread overview]
Message-ID: <CAD+OKUpCVHUO1=mEGCx8Mx7TJLc4rJZjV8+Rgd_fRFrwpBDExA@mail.gmail.com> (raw)

(trying again in plain text)...

I'm encountering invalid checksum errors randomly in tvheadend with my
MyGica T230 DVB-T2 tuner, straight after upgrading from Debian Stretch
(kernel 4.9.168) to Buster (kernel 4.19.37).

For example

2019-06-29 16:32:27.259 [   INFO]:subscription: 004B: "scan"
subscribing to mux "618.167MHz", weight: 6, adapter: "Silicon Labs
Si2168 #0 : DVB-T #0", network: "Freeview", service: "Raw PID
Subscription"
2019-06-29 16:32:27.769 [WARNING]:tbl-eit: uk_freeview: 618.167MHz in
Freeview: invalid checksum (len 1558, errors 1)
2019-06-29 16:32:27.770 [WARNING]:tbl-base: pat: 618.167MHz in
Freeview: invalid checksum (len 136, errors 1)
2019-06-29 16:32:27.967 [WARNING]:tbl-base: sdt: 618.167MHz in
Freeview: invalid checksum (len 971, errors 1)
2019-06-29 16:32:28.462 [WARNING]:tbl-base: pmt: 618.167MHz in
Freeview: invalid checksum (len 60, errors 1)
2019-06-29 16:32:28.463 [WARNING]:tbl-base: pmt: 618.167MHz in
Freeview: invalid checksum (len 46, errors 1)
2019-06-29 16:32:28.637 [WARNING]:tbl-base: pmt: 618.167MHz in
Freeview: invalid checksum (len 38, errors 1)
2019-06-29 16:32:32.258 [   INFO]:mpegts: 618.167MHz in Freeview scan complete
2019-06-29 16:32:32.258 [   INFO]:subscription: 004B: "scan" unsubscribing
2019-06-29 16:32:32.259 [   INFO]:mpegts: 642MHz in Freeview - tuning
on Silicon Labs Si2168 #0 : DVB-T #0
2019-06-29 16:32:32.259 [   INFO]:subscription: 004E: "scan"
subscribing to mux "642MHz", weight: 6, adapter: "Silicon Labs Si2168
#0 : DVB-T #0", network: "Freeview", service: "Raw PID Subscription"
2019-06-29 16:32:41.179 [   INFO]:mpegts: 642MHz in Freeview scan complete
2019-06-29 16:32:41.179 [   INFO]:subscription: 004E: "scan" unsubscribing
2019-06-29 16:32:41.180 [   INFO]:mpegts: 602MHz in Freeview - tuning
on Silicon Labs Si2168 #0 : DVB-T #0
2019-06-29 16:32:41.180 [   INFO]:subscription: 0052: "scan"
subscribing to mux "602MHz", weight: 6, adapter: "Silicon Labs Si2168
#0 : DVB-T #0", network: "Freeview", service: "Raw PID Subscription"
2019-06-29 16:32:41.835 [WARNING]:tbl-eit: uk_freeview: 602MHz in
Freeview: invalid checksum (len 320, errors 1)
2019-06-29 16:32:42.109 [WARNING]:tbl-base: sdt: 602MHz in Freeview:
invalid checksum (len 322, errors 1)
2019-06-29 16:32:42.314 [WARNING]:tbl-base: pmt: 602MHz in Freeview:
invalid checksum (len 84, errors 1)
2019-06-29 16:32:46.180 [   INFO]:mpegts: 602MHz in Freeview scan complete
2019-06-29 16:32:46.180 [   INFO]:subscription: 0052: "scan" unsubscribing

The issue is not specific to particular muxes, and happens entirely at
random. If I retune then the same mux will scan without issue. It also
causes data corruption when streaming with continuity counter errors
in the tvh log; again retuning often resolves the problem, but i never
had any such issues with kernel v4.9.x.

Heres the output of lsusb to confirm my hardware id:
0572:c688 Conexant Systems (Rockwell), Inc. Geniatech T230 DVB-T2 TV Stick

I've been testing various kernel versions in-between 4.9->4.19 and
quickly found that the issue was introduced somewhere between
4.9->4.10.

I therefore performed a (lengthy) git bisect to find out which of the
14,248 commits during the v4.10 development cycle introduced this
regression.

I have tracked this regression down to the following commit:
5fa8815: [media] dvb-usb-cxusb: Geniatech T230 - resync TS FIFO after lock

Indeed, if I revert that commit on an upto-date kernel, I now have a
stable MyGica T230 tuner once more.

Please note that i've tried the latest media_build drivers and have
also the 5.2 kernel; both of which have the issue, and both of which
can be fixed by reverting 5fa8815.

Regards,
James

             reply	other threads:[~2019-07-17  7:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17  7:44 James Hutchinson [this message]
2019-07-17 12:21 ` MyGica T230 dvb-t2 data corruption since commit 5fa8815 JP
2019-07-17 21:22 ` Thomas Hollstegge
2019-07-19 18:35 ` Jan Pieter van Woerkom
2019-07-21 18:29   ` Sean Young
2019-07-21 22:03     ` JP
     [not found]       ` <CAD+OKUre40kQiucuryJC0uYrvBSqL5M=pAkmi7QxgOoKUWt0bg@mail.gmail.com>
     [not found]         ` <70cb09ed-1ae4-6626-643d-c9e1c9ae47c6@jpvw.nl>
     [not found]           ` <CAD+OKUr-f_a8dcPVp24d4wPhRAE80tf10_kt5s3_WvVmfWu9JQ@mail.gmail.com>
2019-07-22 16:22             ` Jan Pieter van Woerkom
2019-07-23 16:02               ` James Hutchinson
2019-08-02 11:58                 ` James Hutchinson
2019-08-02 12:00   ` James Hutchinson
2019-08-13 13:46     ` JP
2019-08-15 10:14       ` Sean Young
2019-08-15 16:34         ` [PATCH 0/2] media: dvb-usb: move T230 to dvbsky Jan Pieter van Woerkom
2019-08-15 16:37           ` [PATCH 1/2] " Jan Pieter van Woerkom
2019-08-15 16:39           ` [PATCH 2a/2] " Jan Pieter van Woerkom
2019-08-15 16:41           ` [PATCH 2b/2] " Jan Pieter van Woerkom
2019-08-18 10:29       ` MyGica T230 dvb-t2 data corruption since commit 5fa8815 Sean Young
2019-08-20 19:25         ` JP

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='CAD+OKUpCVHUO1=mEGCx8Mx7TJLc4rJZjV8+Rgd_fRFrwpBDExA@mail.gmail.com' \
    --to=jahutchinson99@googlemail.com \
    --cc=crazycat69@narod.ru \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@s-opensource.com \
    /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).