OZ 3.3.6-pre1, stuff on sd. Can\'t resume after suspend...

[bluey]

Anyone which has stuff on sd mounted or linked to /usr, /opt, etc, had ever had any problem with suspending?

Sometimes it goes down normally, and at a certain speed. It resumes well.

Other times it goes down faster, and it does not resume after... A soft reset is needed.


Thanks!


Greetings,

bluey


(About 3rd OOO newsletter: Nice job Mickeyl, nice to read that things are going better with OE! Good luck for your (yours and the rest of the team) work!  )

[Mickeyl]

Sounds like a race condition or so. The whole sdmgr stuff seems pretty flaky anyway. Sharp surely did lots of hacks and workarounds to get it that stable as it is in the original ROM. Nothing much we can do about that without the sources

[bluey]

Makes any sense it happens after using ekonsole? It seems the Z is on but the screen is turned off, since the battery gets drained...


Greetings


[EDIT]
Actually, it seems something to do with Opie unstable. I reflashed to 3.3.6 and removed opie, then installed basic Opie stuff to root from the unstable feed. Then installed some more apps to SD (just to remove the possibility of problems related to mounted SD and stuff), and it happens too... It seems to be when I run apps from opie (those linked to quicklauncher?)...


Is there any way of tracking the problem to issue it as a possible bug? Is it just SD stuff fault?


OR


Is there a place where a TODO for OZ 3.5.1 is well defined with explicit tasks? :|

[bluey]

I notice that during normal usage, by something I can\'t track, the battery applet stops saying the percentage and goes to Good kind of report (something happen to apm?), and it is after that that things stop working well, as in, suspend not resuming.

[bluey]

I carefully run a few apps to see what was going wrong, and noticed that when I run the light and power app, after a few time it stops working, syslog is reporting that it can\'t write to apm.conf.new, and battery applet is showing status as sharp rom did (good bad etc) instead of percentage. Apm on the konsole reports the percentage, though. I noticed with the clock app too (and giving the error with Launcher.conf.new if remember)...

Could it be something with a new lib version? Anyone using Opie unstable (1.1.3?) noticed any of this behaviour? Posting /var/log/messages would help anything?

[wylbur]

I\'m using a SL-5600 (pxa250, from Amazon in the last month) with OZ 3.3.6-0pre1 and mostly all opie 1.1.3. I\'ve got a few apps on the kingston 256mb SD card, but mostly everything is in flash & ram. I find that _any_ user app (whether on the sd or not) left running before the suspend prevents resume: the screen comes on dimly but hung. I\'m working on a more careful diagnosis.

this said, opie 1.1.3 _rocks_. It\'s gorgeous, responsive, and has great apps. thanks for the work, OZ folks.

-- wylbur

[wylbur]

when I resume the Z and opie hangs, I can still ssh into it from my desktop and work from there.  At that point, linux/bash are alive, and I can restart opie.

When I restart opie, the system clock resets and opie acts a little flaky, with weird lagged responses to screen taps, partial repaints. This situation continues until a full reboot (when I need to reset the system time again). If I run ntpdate -u clock.myserver.com from the command line, opie apps (but not opie itself) tend to crash. The crashing app I notice most is the calendar which I\'ve usually got on fastload, so it\'s always running.

Are there tests I could do at that point to identify the issues?

more as I figure it out. -- wylbur