<br><br><div><span class="gmail_quote">On 7/26/07, <b class="gmail_sendername">Brad DerManouelian</b> <<a href="mailto:myth@dermanouelian.com">myth@dermanouelian.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Jul 26, 2007, at 10:09 AM, Phil Figgins wrote:<br><br>> David,<br>> No dice here. It can go for a week without a crash, but sometimes<br>> as little<br>> as 15 minutes in between them. It seems that no one has an answer,
<br>> and I<br>> simply don't know enough about Linux to figure it out. My plan is<br>> to build a<br>> temporary backend out of some older hardware to replace this one<br>> and then<br>> rebuild this one. I'd be glad to hear from anyone with ideas before
<br>> I waste<br>> time building 2 systems.<br>><br>> My current "fix" when the wife & kids say "the tv's broke again" is<br>> to fire<br>> up TeraTerm and run "/etc/init.d/mythbackend restart". The stop of the
<br>> mythbackend service fails each time since it's already dead. So I<br>> think the<br>> errors we see in our logs are just building up to whatever is<br>> killing the<br>> service. That might explain why it's not the same error every time.
<br>> It seems<br>> like the failure to connect to itself is the beginning of things going<br>> downhill.<br>><br>> FYI - I'm running MythDora 3.2 on more than capable hardware.<br>><br>> Phil<br>
<br>My AMD64 x86_64 system was very unstable when I was using EIT data<br>collection. I turned it off and it's been great ever since. I still<br>get crashes once in a while when watching LiveTV in HD and it starts<br>
to record something with the same tuner or when two HD shows record<br>one after the other on the HD tuner, but only sometimes. Most of my<br>recording is SD so I just deal with it when it happens.<br>_______________________________________________
<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
</a><br></blockquote></div><br>I'm experiencing the same type of backend crashes - what caught my eye in this post was the lines from Phil's post:<br><p>[mpeg2video @ 0x2b7ca24]ac-tex damaged at 25 29</p>
<p>[mpeg2video @ 0x2b7ca24]Warning MVs not available</p>
Each time in the backend log, the message about the connection to the backend server timing out is preceded by these mpeg2video codec error messages. In addition, I see:<br><br>[mpeg2video @ 0x2b7064d97fd0]invalid mb type in I Frame at 22 22
<br>and<br>[mpeg2video @ 0x2b7064d97fd0]mb incr damaged<br>as well.<br><br>I've searched the mailing list for these errors, and have seen several comments that they are "normal". Has anyone else seen them associated with the crashes? If they represent a "normal" state, why would they be written as warnings to the log?
<br clear="all"><br>-- <br>________________________<br>"It's easy enough to name those who would piss themselves with joy over the prospect of a One World corporate state, with billions of people begging to work for their 1,500 calories a day and an xBox chip in their necks."