<div class="gmail_quote">2012/2/15 David Watkins <span dir="ltr"><<a href="mailto:watkinshome@gmail.com">watkinshome@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 15 February 2012 11:53, ganassa <<a href="mailto:ganassa@gmail.com">ganassa@gmail.com</a>> wrote:<br>
> I turned off NTPD because it's the only known "element" on my BE/FE - as far<br>
> as I know - that is able to change date/time settings on my BE/FE.<br>
> I really don't know how time could change with this behaviour.<br>
><br>
> What is happening know is:<br>
> - sometimes the BE is waking up 2 hours earlier comparing to what's<br>
> scheduled - reporting in log 1 hour earlier - , then turning off before the<br>
> recording and, after that, it will never wake up again.<br>
<br>
</div>I had problems like this once. It was a long time ago but I think it<br>
was related to localtime vs UTC. Doesn't ACPI use UTC (which is<br>
esentially the same as GMT)? Anyway I remember I modified the<br>
shutdown script to log the wakeup time that it was setting and with<br>
that information I was able to work out what was going on.<br></blockquote><div><br></div><div>ACPI should use UTC, I did all the check suggests in the Wiki (see the first post of this thread) and everything should be ok, my BIOS is UTC-compatible</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
<br>
> - other times the BE is waking up correctly. This happens always when I'm at<br>
> home and looking at it :)<br>
<br>
</div>Is it conceivable that it's waking up two hours early for a *later*<br>
recording, and coincidentally getting the correct time for the current<br>
one?<br></blockquote><div><br></div><div>That's what I can remember at now:</div><div>- during the initial tests, made with some recording scheduled in ~30 minutes, everything went ok</div><div>- the day after I've scheduled 3 programs:</div>
<div>the first at 12.30 - BE woke up and recorded</div><div>the second at 16.30 - BE didn't wake up</div><div>the third at 19.00 - BE didn't wake up</div><div><br></div><div>it stopped waking up. After I woke up manually, it shuts down and later woke up and recorded a further scheduling made for 21.30.</div>
<div>So, it looked like that: after the 1st wake up, it didn't scheduler correctly anymore</div><div><br></div><div>- the third day, I realized there was some problems. I tried disabling NTPD, made some early-tests and then, at 00:41 I let him shut down. I've checked the wake-up scheduling - by logging the setwakeup.sh parameter in mythbackend.log (see previous mail) - and it was set up for 12.30. Instead, as said, it woke up at 10.30, telling (in the syslog) that it was 11.30, and shutdown about 11.20.</div>
<div><br></div><div>This thing is getting me mad :)</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br>