On Wednesday 23 July 2008 19:13:58 Andy Green wrote: > > This used to work, I have done it myself... I think it can be related to > the not coming back from GSM wake issue maybe.
I'm not certain that it goes to sleep. > | off" for setting usb current during suspend/resume? > > Not 100% certain what you're asking, but I think we want to leave USB > limit like it is in suspend, so we can charge. I have a neo in this state now: console: [ 7482.665000] Syncing filesystems ... done. [ 7482.665000] PM: Preparing system for mem sleep [ 7483.245000] Freezing user space processes ... (elapsed 0.09 seconds) done. [ 7483.345000] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done. [ 7483.345000] PM: Entering mem sleep [ 7483.350000] Suspending console(s) inserting/removing usb cable makes usb0 come and go..ping works... openocd/gdb say (assuming I'm not sitting in the bootloader): (gdb) bt #0 s3c24xx_default_idle () at include/asm/arch/system.h:41 #1 0xc002980c in default_idle () at include/asm/arch/system.h:56 #2 0xc00295ec in cpu_idle () at arch/arm/kernel/process.c:170 #3 0xc02c0714 in rest_init () at init/main.c:453 #4 0xc0008c18 in start_kernel () at init/main.c:648 #5 0x30008034 in ?? () So user space has been halted, we sleep somewhere... :) no idea if that is the state I initially reported... let me continue to dig... I will probably not end up in the office tomorrow.. z.
