From: Keith Pyle <kpyle@austin.rr.com>
To: "David Röthlisberger" <david@rothlis.net>
Cc: Jonathan <jonathan.625266@earthlink.net>,
linux-media@vger.kernel.org, will@williammanley.net
Subject: Re: HD-PVR fails consistently on Linux, works on Windows
Date: Sat, 13 Oct 2012 15:11:09 -0500 [thread overview]
Message-ID: <5079CADD.8020409@austin.rr.com> (raw)
In-Reply-To: <F8199D50-FE9B-4F1E-B04A-1B7E8D216A5D@rothlis.net>
On 10/13/12 14:17, David Röthlisberger wrote:
> On Wed, 26 Sep 2012 21:42:32 -0500
> Keith Pyle <kpyle@austin.rr.com> wrote:
>> I recently purchased a Hauppauge HD-PVR (the 1212 version, label on
>> bottom 49001LF, Rev F2). I have consistent capture failures on Linux
>> where data from the device simply stops, generally within a few minutes
>> of starting a capture.
>>
>> [...]
>>
>> Sep 21 17:01:01 mythbe kernel: [535043.703947] hdpvr 9-1:1.0: firmware
>> version 0x15 dated Jun 17 2010 09:26:53
> When we contacted Hauppauge regarding the stability issue, they
> recommended upgrading to the latest firmware dated Mar 26 2012.
> We *think* this has improved stability, but it certainly hasn't
> fixed it completely.
>
> Upgrading the firmware requires a Windows PC -- see
> http://www.hauppauge.com/site/support/support_hdpvr.html
The Mar 26, 2012 firmware is the 1.7.1.30059 version that shows as 0x1e
in the kernel messages. In my case, I've tried both 0x1e and 0x15 with
no discernible difference in stability. That is, both hang reliably and
repeatedly on Linux but not when using a Windows system.
>
> On 13 Oct 2012, at 16:28, Jonathan wrote:
>
>> It may be a coincidence but I since I started using irqbalance (
>> https://code.google.com/p/irqbalance/ ) my HD-PVR has been completely
>> stable. Before that I was experiencing daily lockups.
> Interesting. You definitely didn't upgrade the firmware around the same
> time?
>
> We think the stability is worse when the Linux PC is heavily loaded: We
> do real-time image processing on the video stream from the HD PVR, so
> the CPUs are maxed out, and we get frequent lock-ups. We also think the
> lock-ups are more frequent when we have several HD PVRs connected to the
> same PC, all running at the same time. I'll have to try this irqbalance.
>
> --Dave.
>
All of my tests have been using only one HD-PVR on otherwise nearly idle
systems with *lots* of system resources available. One test system is
an Intel Core 2 Quad Q9400 (2.66 GHz) and the other is an Intel i7 950
(3.0 GHz). CPU loads are low during captures - not anywhere near having
any core at 100%. While system load could certainly be a factor for
some, I do not believe it is in my tests.
Keith
next prev parent reply other threads:[~2012-10-13 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 2:42 HD-PVR fails consistently on Linux, works on Windows Keith Pyle
2012-10-13 15:28 ` Jonathan
2012-10-13 19:17 ` David Röthlisberger
2012-10-13 20:11 ` Keith Pyle [this message]
2012-10-14 12:27 ` Jonathan
2012-10-17 17:54 ` Keith Pyle
2012-12-27 14:03 ` David Röthlisberger
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=5079CADD.8020409@austin.rr.com \
--to=kpyle@austin.rr.com \
--cc=david@rothlis.net \
--cc=jonathan.625266@earthlink.net \
--cc=linux-media@vger.kernel.org \
--cc=will@williammanley.net \
/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).