XO keeps staring at its own belly button

[Ixo X oxI]

I should also add another case.

I have a customized install of firefox (download tarball, alias to run out
of /home/olpc).  Sometimes when I run Firefox, and forget about the limited
memory size...  after about 6 tabs of pages, the whole systems "molasses
effect"... I suspect due to memory swapping madly to keep up.  Soon after it
starts to bog down, sugar kills the activity and I see a suddent speed
increase. :)

I haven't tried this with the newer firefox.xo activity (with FireFox 3.x).

-iXo

On Thu, Aug 7, 2008 at 20:20, Ixo X oxI <ixo at myna.ws> wrote:

> Some more 2 1/2 cents.....
>
> Sometimes when the storage is full (or near full), response time is down.
> (check in Terminal with 'df' and see how much free disk space you have.)  If
> downloading large amounts of data, or in process of updating, could also be
> the cause.
>
> Frequently, when I see such un-responsiveness..  likely I have clicked on
> an activity icon twice by habit, they are both competing to start up.
>
> Hmmmm...  maybe this could be a feature request for 8.2.0 ?  If you try to
> start an activity while it is still already in 'loading' phase...  prompt
> with 'Do you want to run duplicate activities ?'  or if the second click is
> 'close too' the first click.. ignore.. :)
>
> While in Terminal, also check 'top' or 'ps' for running process...
> 'uptime' to see the load averages.  See if there's a different between
> times..
>
> Good Luck,
> -iXo
>
>
> On Thu, Aug 7, 2008 at 17:05, John Gilmore <gnu at toad.com> wrote:
>
>> > For instance - the XO has been sitting there for a minute or more
>> > (in Terminal).  I want to key in a command, so I start typing.
>> > Nothing changes.  I do *NOT* know if my XO is alive or dead.
>> > Suddenly (after one or more seconds) the typed character appears on
>> > the screen.  My XO is alive, after all !!
>> > [I have 'suspend' turned off.  Using Q2E12f, firmware 5.110.22.p17.]
>>
>> This looks a *lot* like how an XO acts when Suspend is on.  See if the
>> power LED has gone off and just blinks occasionally -- that's how you
>> really
>> tell whether you are in suspend.  Power LED on steadily = no suspend.
>> Power LED off most of the time, blinking on = you're suspended.
>>
>> You have to look BEFORE you start typing.  The first key you hit will
>> wake it up again, but it takes the kernel about a second of powered-on
>> time before it becomes responsive again.  (We hope to reduce that
>> significantly, but it's hard work.)
>>
>>        John
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.laptop.org
>> http://lists.laptop.org/listinfo/devel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.laptop.org/pipermail/devel/attachments/20080808/4196271e/attachment.html>