From: Jim Darby <uberscubajim@gmail.com>
To: 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 11:30:57 +0000 [thread overview]
Message-ID: <4F0D72F1.8070806@gmail.com> (raw)
In-Reply-To: <4F0CE040.7020904@iki.fi>
I thought I'd batch all the answers together.
Andy suggested something about transfer buffers being dropped out of
rotation. I'm not sure exactly what this is but if it's anything like
ethernet buffering it would explain it. It would also explain why it
lasts longer on the lower bit rate standard definition TV rather than HDTV.
In response to Antti's question, I have indeed tested kernel 3.1.6. This
was where I originally noticed the problem. I upgraded to 3.2.0 to see
if had been fixed and when I found that it hadn't posted here.
I pulled the LinuxTV.org v4l-dvb from mercurial but it looks more like a
patch than a full kernel (the previous one I pulled seven months ago was
a complete kernel). For reference the 3.0.0+ kernel that came from
LinuxTV.org v4l-dvb seven months ago has functioned flawlessly ever since.
I've just downloaded the media_build.git stuff, installed the extra
packages it needed and it's be building now.
The other card in the system is a very old Nova-T. It's got a LSI L64781
frontend on it.
Finally Steven said that it might be signal, hardware or heat related.
I'm unsure of this because if I boot the machine with the 3.0.0+ kernel
with exactly the same user-land everything it functions perfectly and
has done for months.
I'll report back on my adventures with the media_build changes to the
3.2 kernel.
Best regards,
Jim.
next prev parent reply other threads:[~2012-01-11 11:30 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
2012-01-11 11:30 ` Jim Darby [this message]
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=4F0D72F1.8070806@gmail.com \
--to=uberscubajim@gmail.com \
--cc=linux-media@vger.kernel.org \
/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).