[mythtv-users] New to the list--Myth problem
David Ellis
david at ellisonline.ca
Tue Aug 23 14:37:16 UTC 2005
MythTV 0.18.1 will die if the signal loses lock while the backend is
accessing it. I believe this is one of the bugs currently being worked on in
the newest SVN release.
In the meantime I've found one workaround that while not 100% greatly
reduces the frequency of crashing. In mythsetup, goto the advanced tab on
the capture card definition and change it "Open on Demand" (wording may be
different been a while since I looked at it). This will cause the card to be
opened when accessed, and closed otherwise. The default Myth behavior is
keep the card/stream opened at all times.
David
-----Original Message-----
From: mythtv-users-bounces at mythtv.org
[mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Patrick Szalapski
Sent: Tuesday, August 23, 2005 10:29 AM
To: mythtv-users at mythtv.org
Cc: skoch at equuscs.com
Subject: [mythtv-users] New to the list--Myth problem
Hello all,
Just dropped in for a quick question--I've been searching the net and can't
find a single idea.
I am experiencing a mythbackend crash and I cannot find the cause. I have
myth .18.1 on Gentoo Linux 2.6.12. I am using a pcHDTV-3000 capture card
and an nVidia GeForce 4 4200 for DVI-out to my HDTV. TV records well and
plays back well now, but every day or so mythbackend crashes at seemingly
random times--usually when I am not using the PC.
When I start mythbackend from a console, the only dump I get from it when
it crashes hours later is "Killed". No seg fault or other error:
=======
root ~% mythbackend --logfile mythlog1.txt --verbose all
[.....many hours go by with normal functionality....]
Killed
root ~%
============
What could be causing it to die? Here is the end of the most recent
verbose log file (14 MB) I have. The only errors I seem to get are all
these mpeg2video errors. Are any of those fatal? Any ideas are
appreciated.
=======
root ~% tail -n 40 mythlog1.txt
[mpeg2video @ 0xb7706830]ac-tex damaged at 80 37
[mpeg2video @ 0xb7706830]concealing 45 DC, 45 AC, 45 MV errors
[mpeg2video @ 0xb7706830]00 motion_type at 69 40
[mpeg2video @ 0xb7706830]00 motion_type at 97 41
[mpeg2video @ 0xb7706830]00 motion_type at 118 44
[mpeg2video @ 0xb7706830]00 motion_type at 58 46
[mpeg2video @ 0xb7706830]concealing 371 DC, 371 AC, 371 MV errors
[mpeg2video @ 0xb7706830]ac-tex damaged at 71 25
[mpeg2video @ 0xb7706830]concealing 80 DC, 80 AC, 80 MV errors
[mpeg2video @ 0xb7706830]skiped MB in I frame at 65 33
[mpeg2video @ 0xb7706830]concealing 80 DC, 80 AC, 80 MV errors
[mpeg2video @ 0xb7706830]MPEG motion vector out of boundary
[mpeg2video @ 0xb7706830]concealing 25 DC, 25 AC, 25 MV errors
[mpeg2video @ 0xb7706830]00 motion_type at 89 45
[mpeg2video @ 0xb7706830]concealing 80 DC, 80 AC, 80 MV errors
[mpeg2video @ 0xb7706830]concealing 15 DC, 15 AC, 15 MV errors
[mpeg2video @ 0xb7706830]concealing 4 DC, 4 AC, 4 MV errors
[mpeg2video @ 0xb7706830]00 motion_type at 52 66
[mpeg2video @ 0xb7706830]concealing 80 DC, 80 AC, 80 MV errors
[mpeg2video @ 0xb7706830]slice mismatch
[mpeg2video @ 0xb7706830]00 motion_type at 114 47
[mpeg2video @ 0xb7706830]00 motion_type at 75 48
[mpeg2video @ 0xb7706830]slice mismatch
[mpeg2video @ 0xb7706830]00 motion_type at 93 50
[mpeg2video @ 0xb7706830]00 motion_type at 107 52
[mpeg2video @ 0xb7706830]concealing 498 DC, 498 AC, 498 MV errors
[mpeg2video @ 0xb7706830]00 motion_type at 79 56
[mpeg2video @ 0xb7706830]ac-tex damaged at 105 57
[mpeg2video @ 0xb7706830]concealing 170 DC, 170 AC, 170 MV errors
[mpeg2video @ 0xb7706830]00 motion_type at 83 15
[mpeg2video @ 0xb7706830]concealing 40 DC, 40 AC, 40 MV errors
[mpeg2video @ 0xb7706830]concealing 17 DC, 17 AC, 17 MV errors
[mpeg2video @ 0xb7706830]MPEG motion vector out of boundary
[mpeg2video @ 0xb7706830]MPEG motion vector out of boundary
[mpeg2video @ 0xb7706830]skiped MB in I frame at 20 12
[mpeg2video @ 0xb7706830]concealing 40 DC, 40 AC, 40 MV errors
[mpeg2video @ 0xb7706830]invalid mb type in P Frame at 82 41
[mpeg2video @ 0xb7706830]00 motion_type at 84 49
[mpeg2video @ 0xb7706830]concealing 80 DC, 80 AC, 80 MV errors
2005-08-17 02:58:28.040 Transcoding
/var/video/1008_20050815210000_20050815220000.nuv done
root ~%
=============
The only errors I seem to get are all those mpeg2video errors. Are any of
those fatal? I also filtered out the mpeg2video lines and the JobQueue
lines to see this:
======
root /var/log% grep -v mpeg2video mythtv/mythlog1.txt | grep -v JobQueue |
tail -n 40
2005-08-14 19:13:56.996 Found -1 episodes in recording profile 100 using
max expiration
[....many similar lines...]
2005-08-14 19:13:57.059 Found -1 episodes in recording profile 98 using max
expiration
2005-08-14 19:23:57.080 Found 13 record profiles using max episode
expiration
2005-08-14 19:23:57.081 - The Price Is Right
2005-08-14 19:23:57.081 - CSI: Miami
2005-08-14 19:23:57.082 - CSI: NY
2005-08-14 19:23:57.108 - CSI: Crime Scene Investigation
2005-08-14 19:23:57.108 - Hit Me Baby One More Time
2005-08-14 19:23:57.109 - Extreme Makeover: Home Edition
2005-08-14 19:23:57.109 - Jeopardy!
2005-08-14 19:23:57.109 - King of the Hill
2005-08-14 19:23:57.109 - House
2005-08-14 19:23:57.110 - Cops
2005-08-14 19:23:57.110 - Lighter Side of Sports
2005-08-14 19:23:57.110 - Saturday Night Live
2005-08-14 19:23:57.110 - Frasier
2005-08-14 19:23:57.111 Found -1 episodes in recording profile 100 using
max expiration
2005-08-14 19:23:57.112 Found -1 episodes in recording profile 101 using
max expiration
====================
Is my database pooched? What do those "Found -1 episodes" lines mean? Any
ideas are appreciated. How can I troubleshoot this? If I just figure it
out, HiDef MythTV will be working great. Thanks in advance,
P-Sz
More information about the mythtv-users
mailing list