[mythtv-users] OT: System clock running very slow
jheizermythtv at gmail.com
Mon Jan 18 22:12:12 UTC 2010
My system was getting way off a few months ago. I ended up getting help
on the IRC channel that led to clocksource=acpi_pm being added to my
kernel boot line. You can see the chat history from that day at
http://mythtv.beirdo.ca/ircLog/channel/1/2009-10-19 Towards the bottom,
look for me (jheizer) asking for help and you can read through what we
did. After that day all was well.
On 01/18/2010 03:44 PM, Nick Rout wrote:
> On Tue, Jan 19, 2010 at 10:03 AM, Ian Newby<ian at codex.org.uk> wrote:
>> Hi Folks,
>> My combined frontend/backend mythtv box (running 0.21 on Ubuntu 8.04) has
>> been working now for about 3 years with no problems (not caused by me).
>> However, since Christmas, the system clock has become very inaccurate. Its
>> now so inaccurate that ntpd cannot keep it up to date.
>> My current estimate is that it is loosing about 4 hours in a 48 hour period,
>> which makes recording very difficult. I've sidestepped the problem by
>> disabling ntpd and running ntpdate very 15 minutes from cron.
>> Anyone have any ideas as to what is causing the clock to slow so much. I may
>> have done package updates which could have caused this. Anyone else having a
>> similar problem?
> possibly your ntp.drift file has garbage in it. Have a look and see
> what the value is. In *buntu its /var/lib/ntp/ntp.drift. IIRC its safe
> to clear the contents and restart ntpd.
> mythtv-users mailing list
> mythtv-users at mythtv.org
More information about the mythtv-users