<br><br><div class="gmail_quote">On Fri, Oct 15, 2010 at 12:00 AM, David Shay <span dir="ltr"><<a href="mailto:davideshay@gmail.com">davideshay@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br><div class="gmail_quote"><div><div class="h5"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br></blockquote></div></div><div>Any update on this Khanh? I get the exact same thing around starting/stopping running 23-fixes. Turned off real-time commflagging but that didn't fix it. At one point several weeks ago I tried trunk and got the same errors if not worse, so I'm a bit reluctant to try that again, particularly with the downgrade hassles. I have lots of logs from slave and master backends, but I've not run with those options, not done a GDB yet. If this is fixed in trunk, I'll gladly do that as well.</div>
<div><br></div></div><br></blockquote><div><br>I wound up going back to r24996, setting the three tuners in my MBE to higher priority, and the one tuner in my SBE to the lowest. This way, my SBE almost never records. Additionally, I went back to compiling with --enable-proc-opt and disabling other options I don't use (like dvb and iptv). I won't say that I've NEVER seen the "MYTH_PROTO_VERSION was empty" error, but I've only seen it once in about three or four weeks.<br>
<br>I don't really know which of these actually is "helping", but I'm much more stable now.<br></div></div>