From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-media@vger.kernel.org
Subject: hvr-1600 records one, fails recording the other on an mplex
Date: Sat, 27 Oct 2012 17:34:10 -0400 [thread overview]
Message-ID: <k6hk0s$63g$1@ger.gmane.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1750 bytes --]
Hi,
As I wrote about a number (3-4) of weeks ago, I am still having a
problem with my HVR-1600 failing on multiple digital recordings. At the
time I reported this previously, there was a question of whether my
current version of MythTV was to blame.
To that end, I updated my MythTV to the latest (at the time) on the
0.25-fixes branch. I also, at the same time, switched my primary
digital tuner to my HVR-950Q. I ran in that configuration for a couple
of weeks without a single failed recording.
A week ago, I switched back to having my HVR-1600 as the primary device
to determine if it was the HVR-950Q switch or the MythTV update that
gave me such success and sure enough, on a particularly busy evening of
recording (but no busier than the same evening the prior two weeks where
the HVR-950Q worked flawlessly) one recording on a given multiplex
failed while another on the same multiplex, at the same time, was
successful.
Unsurprisingly "femon" reported "FE_HAS_LOCK" for the entire time period
of the failed recording. I say unsurprisingly because as I mentioned
prior, another recording on the HVR-1600 at the same time was successful.
Additionally, many, many times during the last week more than one
recording on a given multiplex on this HVR-1600 worked so this problem
is most definitely intermittent, but my experience for the last 3-4
weeks I think proves that it's a problem with the HVR-1600 and not
MythTV given that it's something that happens only with the HVR-1600 and
not with the HVR-950Q.
Unfortunately, there was nothing on the kernel log at the time of the
failed recording.
How can I gather further information on what might be going on which is
causing this failure?
b.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
reply other threads:[~2012-10-27 21:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='k6hk0s$63g$1@ger.gmane.org' \
--to=brian@interlinx.bc.ca \
--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).