[Bug 788] Starting or stopping gsmd completely locks up the Neo

bugzilla-daemon at bugzilla.openmoko.org bugzilla-daemon at bugzilla.openmoko.org
Tue Nov 13 04:36:13 CET 2007


------- Additional Comments From tick at openmoko.com  2007-11-13 04:36 -------
In my opinion. Both Mickey and Mike are right.
In the point of view of robust, phone service device should has a watchdog
scheme to monitor if gsmd is still working.
In the point of view of finding root cause, it's obviously something wrong in
kernel. And we should find out the root cause and release a kernel patch.

However, in the point of view of making  whole project runs well, I think we
should put the Neo into a safe area, which let Neo can work well and that
further develop can go on, if we can, and mark all the bugs we found. Enlarge
the safe area step by step by solving each bug.

I think we can solving the issue with the following steps. 

1. Since we know pull down the power pin will crash the system, we shall not
pull down this pin in the script.  (For Neo's stability)  (For not blocking
non-gsmd developers)
2. Phone service daemon shall monitor if gsmd is still alive. 
3. Let gsmd work for the first initialization
4. Gsmd introduces timeout and error detection (handling) scheme. (For stability
and robust)
5. Fix the system hang bug from kernel.  (For Kernel and GSMD developers)
6. Adding the pull pin scheme back to script if needed. (Enlarge the safe area)

All the error detection and handling schemes shall be left there, but warnings
and errors should be reported so that we have clues to solve them.

I may be wrong, it's just my opinion and proposal. How you guys think?  
We can improve this together. 

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

More information about the buglog mailing list