<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [mythtv-users] Help debugging XvMC
freezes</title></head><body>
<blockquote type="cite" cite>On Tue, Apr 22, 2008 at 5:03 PM, Misty P
<<a href="mailto:mistyp@thekorn.net">mistyp@thekorn.net</a>>
wrote:<br>
<blockquote>I have a fully working mythtv frontend/backend combination
running on an<br>
nvidia 7300LE. Running myth version 16838 . Viewing
content using xv, it's<br>
solid as a ROCK! No, *really*, so far (2 months in) it's never
failed.<br>
<br>
Since I had a decent GPU, I decided to try playing with XvMC. I
installed<br>
envy, had it upgrade my nvidia drivers, and all was well. I
added another<br>
playback config with XvMC, and it worked! The OSD was in black
and white,<br>
but that was an acceptable trade off to me.<br>
<br>
<br>
EXCEPT that now the front end will randomly freeze while playing
back<br>
content. It doesn't matter if I'm watching Live TV or something
recorded.<br>
I'll be watching something, and the screen will just freeze on that
frame.<br>
Sometimes I'll be watching for twenty minutes, sometimes it'll be for
two.<br>
There's no rhyme or reason as to when the freezes happen.<br>
<br>
Once frozen, the front end is *completely* dead. If I SSH into
the machine,<br>
I can kill the front end and restart it OK. If I then go and
view the same<br>
recording at the same point, it will NOT crash again. (i.e. this
isn't a<br>
"bad content" issue.)<br>
<br>
What's throwing me is that there is absolutely NOTHING interesting in
the<br>
log files. Just the standard "switching from none to live
TV" and "using<br>
XvMC" type messages that you normally see. No warnings, no
errors, nothing<br>
"interesting". I've also checked the nvidia core
temperature via nvclock,<br>
and when the frontend freezes the GPU is sitting around 55C.
(It's *always*<br>
at that temperature, whether using xv or XvMC.) So I don't think
it's a GPU<br>
overheating issue, either.<br>
<br>
<br>
<br>
Where/how do I begin debugging this?<br>
<br>
(Note that if I switch the playback profile back to the xv profile,
the<br>
system goes back to being stable as a rock. So I have a work
around, but<br>
I'd like to use XvMC if I can get it working reliably.)<br>
</blockquote>
</blockquote>
<blockquote type="cite" cite> </blockquote>
<blockquote type="cite" cite>It is likely a hardware driver issue.
Myth can't cause your machine to lock like that, only something at a
very low level like a driver. I'd back down the nvidia version
to something less recent and see if that helps (or even your previous
version)</blockquote>
<blockquote type="cite" cite> </blockquote>
<div><br></div>
<div>humm 7300LE, that's similar to the 7300 is in the AppleTV. I
would experience random freezes and green blocky video corruption
using XvMC until I under-clocked the gpu. See
http://code.google.com/p/atv-bootloader/wiki/UpdateNvidiaDriver for
details.</div>
<div><br></div>
</body>
</html>