Mailing List Archive: MythTV: Dev

HDHR Error Messages

Index | Next | Previous | View Threaded

kenneth.emerson at gmail

Jul 12, 2009, 9:39 PM

Post #1 of 2 (603 views)
Permalink

HDHR Error Messages

I recently installed Ubunto 9.04 (previously using 6.10) which required me
to update my MythTV source to the latest trunk (previous version wouldn't
compile with the new libraries). After some painstaking work, I got
everything working again except that my log files are filling up with new
error mesages that I have never seen before. The most obtrusive one appears
to be related to my HDHomerun turners. I get the following type of message
as often as every 100ms during recording:

2009-07-12 10:28:06.689 HDHRSH(1013A1B7-1): RunTS(): data_length = 7896
remainder = 188

It occurs on both tuners but doesn't appear to affect the quality of the
recording. I have the most recent HDHR firmware (April 2009) installed.

The next error message seems to be related to my HVR1800. It appears about
every 6 minutes whether a recording is occuring or not (EIT related?):

2009-07-12 08:09:17.145 DVBSM(/dev/dvb/adapter0/frontend0), Warning: Can not
measure Signal Strength
eno: Invalid argument (22)

The last message I'm not sure what is triggering it, but it also comes
several times a second:

2009-07-12 20:08:36.142 Dec: DoFastForward(): desiredFrame(3421) >
last_frame(1042)
2009-07-12 20:08:36.143 Dec: DoFastForward(): Desired frame is way past the
end of the keyframe map!
Seeking to last keyframe instead.

Any help would be appreciated and I'd be happy to supply more information if
required.

Configuration:
Tuners: PVR-250, PVR-350, HVR1800, HDHR
QuadCore Intel processor, 4GB RAM
Ubuntu v9.04
MythTV trunk version 20788

Regards,

Ken Emerson

cizek at rcn

Jul 14, 2009, 12:21 PM

Post #2 of 2 (527 views)
Permalink

Re: HDHR Error Messages [In reply to]

> I recently installed Ubunto 9.04 (previously using 6.10) which
> required me to update my MythTV source to the latest trunk (previous
> version wouldn't compile with the new libraries). After some
> painstaking work, I got everything working again except that my log
> files are filling up with new error mesages that I have never seen
> before. The most obtrusive one appears to be related to my HDHomerun
> turners. I get the following type of message as often as every 100ms
> during recording:
>
> 2009-07-12 10:28:06.689 HDHRSH(1013A1B7-1): RunTS(): data_length =
> 7896 remainder = 188
>
> It occurs on both tuners but doesn't appear to affect the quality of
> the recording. I have the most recent HDHR firmware (April 2009)
> installed.
>

Ken,

I don't know what's up with that, but I've attached two patches that
might help.

First, if you just want to get rid of the error message use
"simplefix.patch". It changes the log message from IMPORTANT to RECORD
so it won't be printed out.

Second, if you're good with tools and want a better look at the
recording process, use "134-hdhr.recstats.trunk.9.patch". It logs the
HDHR statistics at the end of the recording. You'll get lines like this:

2009-07-14 11:23:30.801 HDHRRec(41): HDHR Stats: pkts=219453 hwm=215
KB Errors: net=0 trnsprt=0 seq=0 ovflow=0
2009-07-14 11:25:27.357 HDHRRec(43): HDHR Stats: pkts=122871 hwm=215
KB Errors: net=0 trnsprt=0 seq=0 ovflow=0

These stats are directly from the HDHR library and display counts of
net, transport and sequence errors, as well as internal buffer
overflows. I don't really know what they mean, but smaller number are
better (you should check the hdhomerun docs for specifics). Any
significant non-zero values generally mean missing or corrupt data,
either of which could result in your original error.

Two caveats. These stats don't work for liveTV, and I use fixes, so the
134 patch might be a little flaky but it should work and shouldn't hurt
anything.

-Bill

Attachments:

simplefix.patch (0.70 KB)

134-hdhr.recstats.trunk.9.patch (17.2 KB)

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads