From: Thomas Hollstegge <thomas.hollstegge@gmail.com>
To: linux-media@vger.kernel.org, crazycat69@narod.ru,
mchehab@s-opensource.com,
James Hutchinson <jahutchinson99@googlemail.com>
Cc: JP <jp@jpvw.nl>
Subject: Re: MyGica T230 dvb-t2 data corruption since commit 5fa8815
Date: Wed, 17 Jul 2019 23:22:38 +0200 [thread overview]
Message-ID: <20190717212238.GA7654@googlemail.com> (raw)
In-Reply-To: <CAD+OKUpCVHUO1=mEGCx8Mx7TJLc4rJZjV8+Rgd_fRFrwpBDExA@mail.gmail.com>
Hi James,
I have both sticks (v1 and v2) and can confirm your observations. I
also pinned the problem down to the commit you specified. I am running
on a kernel with that commit reverted for some months now and didn't
observe any problems so far.
The easiest way to reproduce this issue was to force a complete
network scan in tvheadend. With that commit applied, the scan always
failed after ~50% of all muxes were scanned. And it was not just about
some continuity errors, but a complete loss of signal that could only
be resolved by rebooting.
After reverting the commit, everything runs fine.
Best regards
Thomas
next prev parent reply other threads:[~2019-07-17 21:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 7:44 MyGica T230 dvb-t2 data corruption since commit 5fa8815 James Hutchinson
2019-07-17 12:21 ` JP
2019-07-17 21:22 ` Thomas Hollstegge [this message]
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=20190717212238.GA7654@googlemail.com \
--to=thomas.hollstegge@gmail.com \
--cc=crazycat69@narod.ru \
--cc=jahutchinson99@googlemail.com \
--cc=jp@jpvw.nl \
--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 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.