<br><br><div class="gmail_quote">On Fri, Aug 24, 2012 at 12:42 PM, Joseph Fry <span dir="ltr"><<a href="mailto:joe@thefrys.com" target="_blank">joe@thefrys.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br><div class="gmail_quote">On Fri, Aug 24, 2012 at 3:31 PM, Ross Boylan <span dir="ltr"><<a href="mailto:rossboylan@stanfordalumni.org" target="_blank">rossboylan@stanfordalumni.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I attempted to ssh in, but did not get a connection until the system got itself unstuck. (for both hangs).</blockquote></div><br></div><div>Ahh... so the system isn't truely hung... it eventually recovers.</div></blockquote>
<div>Yes. Though it takes about 15 minutes. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br></div>
<div>There was a lot of discussion recently regarding the leap-second bug causing extremely high CPU utilization. Doubt that's it, but it's possible I suppose.</div></blockquote><div>I've rebooted since experiencing the hangs; my understanding is that will take care of the leap second bug. Also, I was experiencing similar problems with 0.24.2 before the leap second. <br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br></div><div>Either way, something is thrashing your system... and swapping is a likely candidate.</div>
<div><br></div><div>Try copying some files around and see what kind of impact it has on the CPU... perhaps your not using DMA or something silly like that.</div></blockquote><div>I regularly rsync large files. It has some impact on performance and responsiveness, but nothing like what I saw with the problem reported earlier. The copy doesn't spike the CPU, which I think it might if it didn't use DMA.<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br></div><div>I wouldn't think so, but perhaps there is some overhead associated with using the chroot?</div>
<div><br></div><div>Anyway, nothing that mythtv is doing should push your system load to 60! I suspect you had some major iowait going on.</div></blockquote><div>Before the first failure (while watching a video, as opposed to the second failure apparently from transcoding) there were lots of delays and stutters, and lots of complaints from the front end about things taking too long (sorry, don't have the messages available any more).<br>
<br>The system is heavily loaded and uses a fair amount of swap. Maybe the swapping is slowing IO responses, and things kind of cascade from there...<br>Ross <br></div><br></div>