<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
> If I had to guess, I would say resource conflict, most likely IRQ's. If<br>
> the sound card was sharing an IRQ with the LCD device (serial port?)...<br>
> it could have caused a hiccup like this.<br>
<br>
</div>I had the problem with a serial LCD and also with my newer USB LCD.<br>
<br>
I had it with my old hardware and with my new hardware (only the sound<br>
card was the same with these 2 PCs).<br>
<br>
It started with MythTV 0.22, if I see it right in my old logs.<br>
<br>
I was thinking, it maybe is a CPU resource/multithreading conflict<br>
inside mythfrontend, because I can also provoke it on my desktop (2nd<br>
frontend) when I do heavy work while watching TV.<br>
<br>
Also, I think the frequency of the incidents changed after I switched<br>
from logging to NFS to logging to RAM disk.</blockquote><div><br></div><div style>Was just a guess... it could be so many different things really. I only guessed IRQ's because I have seen similar issues, especially on older equipment. </div>
<div style><br></div><div style>Hell, I remember the days when you would need to optimize IRQ allocation for damn near every device in your computer or stuff just wouldn't work. With only 16 IRQ's available, most of which were used, you would sometimes hit an impossible. Sometimes devices could share, if they weren't used at the same time, but that would mean no using COM2 while online using a modem on COM4, or no printing on LPT2, while listening to music on your sound card. Stupid crap like that.</div>
</div></div></div>