<br><br><div class="gmail_quote">On Tue, Aug 28, 2012 at 2:24 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>On Mon, Aug 27, 2012 at 08:21:33AM -0400, Kevin Gordon wrote:<br>
> On Mon, Aug 27, 2012 at 1:42 AM, James Cameron <<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>> wrote:<br>
> > Q2F12 added support for automatic power down if lid is closed<br>
> > while at ok prompt, per ticket #11095, svn 2991. If you have been<br>
> > using previous firmware, you may never have seen this message.<br>
> ><br>
> > It has been a feature of XO-1.5 and XO-1.75 already.<br>
> ><br>
> > On XO-1, the lid switch is wired to the CS5536 companion chip, as<br>
> > well as to the the embedded controller. Open Firmware is reading<br>
> > from the GPIO pin array in the CS5536. Hal observed a confused<br>
> > embedded controller or battery error may trigger this issue.<br>
> ><br>
> > Kevin, Robert, please remove the external power, and the main<br>
> > battery, wait ten seconds, then reinsert both, and see if the<br>
> > problem persists.<br>
><br>
> Problem persists.<br>
<br>
</div>Thanks. That test excludes insanity of the embedded controller as a<br>
cause.<br>
<div><br>
> Just a reminder this lid message only appears upon entering firmware<br>
> after a reboot from linux. Doesn't happen on entering "reboot" from<br>
> firmware or a cold start.<br>
<br>
</div>Interesting, thanks. It suggests the fault is in how Linux reboots,<br>
or that Linux has changed the embedded controller behaviour.<br></blockquote><div><br></div><div>I believe you have something here. Something is wrong with the Linux reboots. Perhaps it isnt shutting down 'deep enough' before starting up again anymore. I have a theory that some of the other discussions about date saving and the hwclock behaviour might also be related to what is happening on a Linux reboot. I cannot get the date change to persist to the hw clock on these XO 1.0s without explicitly issuing the hwclock command before then doing an explicit shutdown on these machines. A reboot doesnt work. I will increase the testing of this to other builds and architectures on the other 'date' thread.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
When you say "cold start", do you mean removal of main battery and<br>
external power, or do you mean pressing the power button when the<br>
power LED is off?<br></blockquote><div><br></div><div>Either. I only ever see this spurious lid message when booting into firmware fimmediately upon doing a restart or reboot from Linux on an XO-1 with 12.1.0 and Q2F12. Happens every time on every XO 1.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
> Noted one other "symptom": when I do the reboot from firmware, I do<br>
> hear a little 'click' as the battery LED flashes, I don't hear that<br>
> click on the reboot from Linux. It occurs whether doing a restart<br>
> from the GUI on Linux or entering "reboot" from terminal.<br>
<br>
</div>Not interesting, but thanks. Neither the speakers nor the battery LED<br>
have any direct connection to the lid switch.<br></blockquote><div><br></div><div>Again, not doing any lid-switch testing at all, just mentioning any differences when rebooting into firmware from a linux reboot/restart. This is one other thing that is 'different' from a cold restart or a reboot command from firmware.</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
> > If it does, please get to the ok prompt, type lid-off and press<br>
> > enter (to stop the timer), then test the lid switch like this:<br>
> ><br>
> > ok lid? . cr d# 500 ms many<br>
><br>
> After rebooting from Linux seeing the symptom and entering lid-off<br>
> after entering the above command, saw<br>
><br>
> fffffff<br>
> fffffff<br>
> fffffff<br>
> fffffff<br>
> .<br>
> .<br>
><br>
><br>
> After rebooting from firmware, and not seeing the symprom, and<br>
> entering teh above command, saw<br>
> 0<br>
> 0<br>
> 0<br>
> 0<br>
><br>
> At no time during this whole process was the lid ever closed.<br>
<br>
</div>Thanks. This suggests a pullup resistor is missing, or that the<br>
embedded controller is not managing the signal correctly.<br>
<br>
How many units are affected?<br></blockquote><div><br></div><div>All XO 1's at 12.1.0 and firmware Q2F12/13 </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
How many units are unaffected?<br></blockquote><div><br></div><div>Any XO 11.3.1 or earlier with Q2E45 or earlier do not exhibit this message </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
If there are some unaffected units, please provide a unit serial<br>
number of an affected and unaffected unit, thanks.<br>
<div><br>
On Mon, Aug 27, 2012 at 08:49:55AM -0400, Kevin Gordon wrote:<br>
> At the risk of too much info. I have also noticed that the lid-off<br>
> message when entering firmware does not ever happen on the XO 1.5.<br></div></blockquote><div><br></div><div><br></div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>
<br>
</div>Really? It should! If you close the lid or use a magnet.<br></blockquote><div> </div><div>Sorry, I was unclear, I dont see it on the XO 1.5 because I wasn't actually testing the lid switch, I think it works fine. :-) I'm trying to explain when I see the spurious lid switch message when entering firmware - i.e. it wouldnt actually be 'spurious' if I closed the lid or used a magnet. I do not see the spurious message on any install on the 1.5 when I do a Linux reboot/restart, ever.
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><br>
> Consistently on all machines, whether I do a shut-down or a restart<br>
> from Linux the screen goes to text console, (last message ; dcon<br>
> freeze) then goes to the warning screen, then goes blank.<br>
><br>
> Then on the 1.5 whether doing restart/reboot from Linux or doing a<br>
> shut-down, the power light blinks multiple times before strating up<br>
> again.<br>
<br>
</div>The multiple power indicator blink is an intentional time it takes for<br>
the internal microSD or eMMC to reach a shutdown voltage. It is not<br>
done on XO-1.<br>
<div><br>
> However, on the XO 1.0 when doing a shut-down, the power light<br>
> blinks before turning completely off, but when doing a Linux<br>
> restart, the power light does not blink at any point in the restart<br>
> process.<br>
<br>
</div>Yes, I see that now, I have reproduced it. #12068.<br></blockquote><div><br></div><div>Thanks, </div><div><br></div><div>KG</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><br>
--<br>
James Cameron<br>
<a href="http://quozl.linux.org.au/" target="_blank">http://quozl.linux.org.au/</a><br>
</div></div></blockquote></div><br>