From: Antti Palosaari <crope@iki.fi>
To: Jim Darby <uberscubajim@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Possible regression in 3.2 kernel with PCTV Nanostick T2 (em28xx, cxd2820r and tda18271)
Date: Wed, 11 Jan 2012 03:05:04 +0200 [thread overview]
Message-ID: <4F0CE040.7020904@iki.fi> (raw)
In-Reply-To: <4F0C3D1B.2010904@gmail.com>
On 01/10/2012 03:28 PM, Jim Darby wrote:
> I've been using a PCTV Nanostick T2 USB DVB-T2 receiver (one of the few
> that supports DVB-T2) for over six months with a 3.0 kernel with no
> problems.
>
> The key drivers in use are em28xx, cxd2820r and tda18271.
>
> Seeing the 3.2 kernel I thought I'd upgrade and now I seem to have hit a
> problem.
Do you have possibility to test Kernel 3.1?
Also latest LinuxTV.org devel could be interesting to see. There is one
patch that changes em28xx driver endpoint configuration. But as that
patch is going for 3.3 it should not be cause of issue, but I wonder if
it could fix... Use media_build.git if possible.
> The Nanostick works fine for between 5 and 25 minutes and then without
> any error messages cuts out. The TS drops to a tiny stream of non-TS
> data. It seems to contain a lot of 0x00s and 0xffs.
>
> It looks like the problem of many years ago when the frontends would be
> shut down if they were closed for more than a few minutes. However, it
> would appear that the frontend fds are still open (according to fuser).
>
> Some more system details:
>
> This is running on a 32-bit system.
>
> Everything works fine if I boot with the 3.0.0 kernel.
>
> The user-land application is kaffeine.
>
> There is a PCI DVB-T card in the system which operates fine even when
> the Nanostick stops producing the correct output.
Which is that card? I wonder if there is same drivers used like tda18271...
> I'm more than happy to build kernels and add debugging. I'm basically
> just trying to find the maintainer for these modules so we can figure
> out what's going wrong and fix it before 3.2 escapes into several
> distros and we have this problem on a larger scale.
I am maintainer of the cxd2820r. Mike knows tda18271 and maybe Mauro
em28xx...
> Many thanks for your help,
>
> Jim.
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2012-01-11 1:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 13:28 Possible regression in 3.2 kernel with PCTV Nanostick T2 (em28xx, cxd2820r and tda18271) Jim Darby
2012-01-10 13:54 ` Steven Toth
2012-01-10 23:22 ` Jim Darby
2012-01-11 0:01 ` Steven Toth
2012-01-11 0:34 ` Andy Walls
2012-01-11 1:05 ` Antti Palosaari [this message]
2012-01-11 11:30 ` Jim Darby
2012-01-11 19:19 ` Jim Darby
2012-01-12 16:22 ` Gianluca Gennari
2012-01-12 16:35 ` Jim Darby
2012-01-12 17:13 ` Simon Jones
2012-01-12 17:34 ` Gianluca Gennari
2012-01-13 11:21 ` Mauro Carvalho Chehab
2012-01-13 11:45 ` Gianluca Gennari
2012-01-13 13:50 ` [PATCH] [media] dvb-core: preserve the delivery system at cache clear Mauro Carvalho Chehab
2012-01-13 16:04 ` Gianluca Gennari
2012-01-14 0:00 ` Jim Darby
2012-01-14 14:51 ` Mauro Carvalho Chehab
2012-01-13 13:09 ` Possible regression in 3.2 kernel with PCTV Nanostick T2 (em28xx, cxd2820r and tda18271) Jim Darby
2012-01-13 14:24 ` Gianluca Gennari
2012-01-12 14:29 ` Simon Jones
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=4F0CE040.7020904@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=uberscubajim@gmail.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).