<div dir="ltr"><div style>Hey James,</div><br><div class="gmail_extra"><div class="gmail_quote">On Mon, Feb 4, 2013 at 5:32 AM, James Cameron <span dir="ltr"><<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">On Mon, Feb 04, 2013 at 12:58:47AM +0200, Christoph Derndorfer wrote:<br>
> (1) on Friday while looking at one of the XO-1s which didn't show<br>
> anything on the display (even with a display which was known to<br>
> work) with the serial adapter I saw the attached output.<br>
<br>
</div>Reviewed, thanks.</blockquote><div><br></div><div>thanks a lot for the quick reply.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">
> Looking at the wiki now and given the number of "invalid system<br>
> date" issues we saw on other machines I assume this is a case of the<br>
> "page fault" message situation described on<br>
> <a href="http://wiki.laptop.org/go/Fix_Clock#" target="_blank">http://wiki.laptop.org/go/Fix_Clock#</a> If_the_screen_does_not_turn_on.<br>
<br>
</div>Yes, this is likely.<br></blockquote><div><br></div><div style>Turns out this was indeed the issue and I now fixed it.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="im">
> Or are there any other issues which could produce such an output?<br>
<br>
</div>There might be, but if you have a version before Q2D05 which was<br>
released in 2007, there's almost no chance of anybody remembering<br>
anything useful. It has been more than five years!<br>
<br>
To verify that the Page Fault is happening because of the known<br>
problem (ticket #5391, svn 752), please use the Open Firmware ok<br>
prompt to display the values in the real-time clock, using the .clock<br>
command:<br>
<br>
ok .clock<br>
<br>
If the month is invalid, then the Page Fault is most likely to be the<br>
one expected.<br>
<br>
Another method would be to take an XO-1 with Q2D06 or earlier, remove<br>
the clock battery, force the problem again, and see if the serial log<br>
looks the same. I expect it will.<br>
<br>
There are other methods to diagnose, but these require immediate<br>
collaboration with a firmware engineer, and I don't think it is worth<br>
doing that yet.<br>
<div class="im"><br>
> (2) Mike sent me a bunch of ML 1220 batteries as replacements for<br>
> the XO-1 units which showed the "invalid system date"<br>
> messages. However even with the new batteries in-place, after<br>
> verifying that the (old) battery holders looked okay and having set<br>
> the current time on the command-line the system date reverted back<br>
> to 2000-01-01 00:00:00 after every reboot (and hence the "invalid<br>
> system date" message kept coming up again). Any suggestions on what<br>
> to do in such a situation?<br>
<br>
</div>Charge the battery before the power cycle test. On the XO-1, "it will<br>
recharge from the main power source while the laptop is powered on and<br>
fully awake (not suspended)."<br>
<br>
"When recharging an empty battery, it is expected that the battery<br>
will reach normal voltage levels after around 30 minutes of charging,<br>
but will require potentially 24 hours for a complete recharge."<br>
<br>
<a href="http://wiki.laptop.org/go/Fix_Clock#RTC_power_dynamic" target="_blank">http://wiki.laptop.org/go/Fix_Clock#RTC_power_dynamic</a> has the above<br>
text.<br></blockquote><div><br></div><div style>Thanks a lot for that information, I had somehow managed to miss it.</div><div style><br></div><div style>I'm now charging the four XO-1s which are here in the office and still displaying the "invalid system date" error. Let's see whether it works out.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Check that the battery voltage is reasonable.<br>
<br>
Check that the connector is passing the voltage properly to the<br>
circuit board.<br></blockquote><div><br></div><div style>Unfortunately I don't have any measuring equipment here so I can't do that.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Also, please make sure you upgrade the firmware as soon as you can, so<br>
that you aren't impacted by this problem any further.</blockquote><div><br></div><div style>All of the concerned XO-1s which have this problem are running firmware Q2F12 (and 12.1.0).</div><div style><br></div><div style>
Cheers,</div><div style>Christoph</div></div><div><br></div>-- <br>Christoph Derndorfer<div><br></div><div><div>volunteer, OLPC (Austria) [<a href="http://www.olpc.at/" target="_blank">www.olpc.at</a>]<br><div>editor, OLPC News [<a href="http://www.olpcnews.com/" target="_blank">www.olpcnews.com</a>]<br>
contributor, TechnikBasteln [<a href="http://www.technikbasteln.net/" target="_blank">www.technikbasteln.net</a>]</div></div><div><br></div><div>e-mail: <a href="mailto:christoph@derndorfer.eu" target="_blank">christoph@derndorfer.eu</a></div>
<div><br></div></div>
</div></div>