Hi, I think those are the smsm states being printed in the logs. Do you see a timeout message just after these logs too? Like "timed out waiting for Modem's response ".
If so, you can check what is up with the modem at that time using some debug prints for dumping the smsm state. Im not sure if these prints are normal, because it could just be that the power collapse is suspended because of the wakelock. You can check the implementation in pm.c for details. smd-private.h has the defines for the smsm state. You can disable your app, and check what the values are in a normal case. What happens if you keep your usb cable connected? Do you still see these logs? On Dec 5, 4:20 am, Erik <erik.nordst...@gmail.com> wrote: > Hi, > > I am running a research experiment that uses wifi beaconing to detect > peers on the same network segment. The app I am using sends a "hello > message" every 5 seconds and therefore needs to run all the time. To > ensure the CPU is running, the app grabs a partial wake lock. > > While holding the wake lock I get the following error messages from > the kernel: > > <3>[16772.157226] msm_pm_wait_state(2, 0, 0, 0) failed 11001 > <6>[16772.157226] msm_sleep(): msm_pm_wait_state failed, 11001 > > I see these for the first three hours, but then they stop. At this > point the the battery consumption rate also increases significantly. > > If I run my experiment and release the wake lock for only a few > minutes every 30 minutes, I do not see this problem and the phone has > a much longer battery life that cannot be explained only by the > intermittent sleep times. > > Does anyone have an idea what the problem could be? > > Erik -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
