Hi, I'm speculating a bit here..
-16 is EBUSY, so since you already know that someone is setting the alarms, the next thing would be to look for who is using it. It does look like it is not a kernel problem. You can set the alarms from Alarmmanagerservice. Perhaps, you can dump the service from the shell and check who is setting the alarms. "adb shell dumpsys alarm" You can see an Alarm Stats section where the number of wakeups and such are printed. The user whose wakeup count has increased after a short interval is probably the one setting the alarm. On Jul 26, 8:21 pm, rao <venubyravar...@gmail.com> wrote: > Hi all, > I'm debugging suspend failure of honeycomb on a proprietary target > board. > I was seeing below print on my target board and getting woke up from > already started suspend process. > "PM: Device alarm failed to suspend: error -16" > After adding few prints in the alarm-dev.c I found that alarm_ioctl > function receives ANDROID_ALARM_SET for each and every minute. > Once that time is reached, alarm will be cleared and again set for > next minute. > I really did not understand why this code is needed and also from > where is it done? > Can some one plz help me? > thanks, > Venu -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
