Current finding is that the wakelock puts the system back to suspend again after resume. Look at the end of wakelock.c:suspend function, it checks the entry_event_num. I did not see anyone else changed the value of entry_event_num beside wake_lock_internal. Now, my hard drive is screwed up by a hard power recycle, so I will need to wait until the fscan is completed in order to continue on the debugging.
On Thu, 2009-05-07 at 01:45 -0700, Chih-Wei wrote: > I noticed a more serious problem. > The EeePC will become suspend for a period of time, > and cannot resume back. > Actually when I pressed the power button, > it tried to resume (can see some console messages), > but then enter suspend mode immediately again. > > On 5月7日, 下午2時29分, Chih-Wei <cwhu...@linux.org.tw> wrote: > > Hi Yi, > > Indeed I took that configuration (plus some additional drivers). > > The following options are enabled: > > CONFIG_INPUT_MOUSE=y > > CONFIG_MOUSE_PS2=y > > CONFIG_MOUSE_PS2_ALPS=y > > CONFIG_MOUSE_PS2_LOGIPS2PP=y > > CONFIG_MOUSE_PS2_SYNAPTICS=y > > CONFIG_MOUSE_PS2_LIFEBOOK=y > > CONFIG_MOUSE_PS2_TRACKPOINT=y > > CONFIG_MOUSE_PS2_TOUCHKIT=y > > CONFIG_MOUSE_SERIAL=y > > ... > > I just tested it on EeePC 1000, with the same kernel image I tested on > > 701. > > Amazingly, the touchpad works. > > So... what's the problem? > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
