linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Darby <uberscubajim@gmail.com>
To: linux-media@vger.kernel.org
Cc: uberscubajim@gmail.com, stoth@kernellabs.com
Subject: Re: Possible regression in 3.2 kernel with PCTV Nanostick T2 (em28xx, cxd2820r and tda18271)
Date: Tue, 10 Jan 2012 23:22:02 +0000	[thread overview]
Message-ID: <4F0CC81A.6010301@gmail.com> (raw)
In-Reply-To: <CALzAhNVo4Aar7YbF1f6BU7Fp9Uceb5Nq5-JSb2tP0aNYiEra6A@mail.gmail.com>

On 10/01/12 13:54, Steven Toth wrote:
>> 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.
> What does femon show for demodulator statistics?
>
Well... I downloaded the latest dvb-apps via mecurial from linuxtv.org 
and the following happened at the start while it was working:

status SCVYL | signal ffff | snr 00ef | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00f1 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00ee | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00f0 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00f2 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00ee | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK
status SCVYL | signal ffff | snr 00f0 | ber 00000000 | unc 00000000 | 
FE_HAS_LOCK

and when it stopped working, this time an hour later, nothing had 
changed. In fact, it looks like the driver keeps lock even when it's not 
recording at all.

Any ideas anyone? Looks like the tuner is OK....

The thing that's really confusing me is the totally random amounts of 
time it takes before it fails. This time it was over an hour. For 
reference though this was the first time I'd tried it with standard 
definition transmissions. Not only lower data rate but also DVB-T rather 
than DVB-T2.

Many thanks,

Jim.

  reply	other threads:[~2012-01-10 23:29 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 [this message]
2012-01-11  0:01     ` Steven Toth
2012-01-11  0:34       ` Andy Walls
2012-01-11  1:05 ` Antti Palosaari
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=4F0CC81A.6010301@gmail.com \
    --to=uberscubajim@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=stoth@kernellabs.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).