[OPIE 0000139]: IPAQ : qpe of opie uses 70%user and 30%kernel load

A BUGNOTE has been added to this bug.
=======================================================================
http://131.152.105.154/mantis/view_bug_page.php?f_id=0000139
=======================================================================
Reporter: Werner
Handler: sandman
=======================================================================
Project: OPIE
Bug ID: 0000139
Category: Core
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
=======================================================================
Date Submitted: 07-27-02 12:10 CEST
Last Modified: 08-04-02 20:28 CEST
=======================================================================
Summary: IPAQ : qpe of opie uses 70%user and 30%kernel load
Description:
I observed, that opie takes a lot of power from my batteries. This is
definitely qpe itself (all other apps
stopped and detected by uptime).
=======================================================================

-----------------------------------------------------------------------
 ofels - 07-30-02 08:13 CEST
-----------------------------------------------------------------------
I can not reproduce this. I have almost 0/0 % cpu load when opie is running
with the latest feed.
Are you refering to CPU or battery load ? Your statement is not clear
regarding this.

-----------------------------------------------------------------------
 sandman - 07-30-02 11:28 CEST
-----------------------------------------------------------------------
It would help if you could test this without your network card in the
jacket, since I can not reproduce this here without a nic.

-----------------------------------------------------------------------
 Werner - 07-30-02 19:25 CEST
-----------------------------------------------------------------------
It happend with the opie unstable feed.

Today I tried to reinstall that (had installed qpe for tests again), but
had
no success (libuuid1 missing ind task-opie). So I installed from the
handhelds
feed and was not able to produce the problem again.

So when is the unstable feed installable again ? I will try that
then again.

Werner

-----------------------------------------------------------------------
 ofels - 07-31-02 08:33 CEST
-----------------------------------------------------------------------
The libuuid is a separate package as of familiar 0.6-pre1.
As 0.6-pre1 is considered unstable we can not set an appropriate dependency
as most people are not willing to follow the bleeding edge paradigm.
Install the e2fstools meanwhile and it will work again.

OPIE _is_ installable in the unstable feed and the cpu load symptom you
mentioned does not occur on most devices.

Please try to remove the nic as suggested and clear your /root directory to
make sure you have a clean installation.

-----------------------------------------------------------------------
 ofels - 08-01-02 09:37 CEST
-----------------------------------------------------------------------
I am afraid we are unable to duplicate it so this can't be fixed

-----------------------------------------------------------------------
 sandman - 08-04-02 04:13 CEST
-----------------------------------------------------------------------
I redesigned the suspend/resume -- could you please test again

-----------------------------------------------------------------------
 Werner - 08-04-02 08:06 CEST
-----------------------------------------------------------------------
My actual installation is familiar 0.5.3 stable. task-opie requires
libuuid
and I read that e2fsprogs has that. e2fsprogs (1.25-1) is installed on my
system, but there is still the libuuid dependenc problem. Could you give me
a
advise how to get around this to be able to install task-opie to test it
out?

-----------------------------------------------------------------------
 Werner - 08-04-02 11:56 CEST
-----------------------------------------------------------------------
got around the libuid problem by patching the suautus file :)

The tests show the same thing. Though opie seems to be more stable
now the system goes to the state 70%user and 30%cpu time after e.g. 50
ON/OFF
cycles. It happend more often before, I think.

If the ipaq is in that state, only a reboot helps.

I tried it also without the sleeve and it happens too. So it has nothing to
do with the sleeve and the network card.

-----------------------------------------------------------------------
 sandman - 08-04-02 13:52 CEST
-----------------------------------------------------------------------
Have you tested this with the CVS Version from Sunday morning (MEST) ?
The feed will probably be rebuilt on monday.

-----------------------------------------------------------------------
 Werner - 08-04-02 20:28 CEST
-----------------------------------------------------------------------
Tried it with the CVS this evening. It does still happen under the same
conditions than this morning. The suspend behaviour went worse this time.

By fast switching between suspend and on, you can get a blinking
backlight
in ON mode. Restarting opie helps.

The 70%userMode 30%CPUMode state can also be canceled restarting opie. So
you
dont have to reboot the ipaq.
Received on Sun Aug 04 19:10:07 2002