[mythtv-users] mythtv-users Digest, Vol 54, Issue 12
joe.borne at gmail.com
Tue Sep 4 15:12:47 UTC 2007
> From: Martin Turner <xmode at westnet.com.au>
> Subject: [mythtv-users] Unusual problem
> To: Discussion about mythtv <mythtv-users at mythtv.org>
> Message-ID: <46DD33FE.2090205 at westnet.com.au>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Hi MythList,
> This isn't strictly a Myth question, but only my master Myth backend is
> doing this so I thought I'd ask here. The box its self has been running
> more or less fine for about 2 years now except that recently (the last 2
> weeks) it has developed a stutter.. Now I say stutter because it
> sounds/looks like it gets stuck in a second loop for about 4-6 seconds
> then continues on fine like nothing ever happened. I don't have anything
> in the logs (myth or syslog) to indicate what is going on and im
> basically stuck.. As you can imagining its extremely annoying having it
> do this at random..
> This is what I have observed/done so far..
> - Seems to be at random. Doesn't coincide with any regular running task
> or recordings in myth. Can do it while myth is recording or not.
> - Nothing is logged. If myth is recording I get a log about "
> cx88_wakeup: 31 buffers handled (should be 1)" but after investigation
> im putting that down to the cards internal buffers filling up during the
> stutter then all being read at once rather than it being the error thats
> causing this.
> - New kernel didn't fix the fault (gentoo system, roll my own kernel)
> neither did changing the kernels tick timer or making it a tickless
> kernel. Also, the problem didn't start after a kernel change.
> - Seems to have started after the 0.20.2 upgrade but that may just be
> coincidence. Is it safe to roll back to test?
> - The clock in the system actually stops for the time its stuttering and
> needs to re-sync. NTP fixes this fairly quickly, but interesting..
> Any help would be great, I'm happy to post more info about my system if
> its needed.
My first guess would be that it's a disk seek issue. Use your distros tools
to look into IO response times and possibly disk fragmentation. Try
defragging even if it's only slightly fragged. If it persists with no
explanation, try replacing the drive with a newer, higher speed drive with a
larger cache. I have done so in the past using dd to image it over. Failing
drives often leave no log evidence of their impending doom.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users