On Monday, March 11, 2013 04:51:30 PM John Stultz wrote:
> On 03/07/2013 11:24 PM, Laxman Dewangan wrote:
> > On Friday 08 March 2013 04:46 AM, Greg KH wrote:
> >> On Fri, Mar 08, 2013 at 12:57:37AM +0530, Laxman Dewangan wrote:
> >>> The alramtimer suspend failed when nearest alarm wakeup time is
On 03/07/2013 11:24 PM, Laxman Dewangan wrote:
On Friday 08 March 2013 04:46 AM, Greg KH wrote:
On Fri, Mar 08, 2013 at 12:57:37AM +0530, Laxman Dewangan wrote:
The alramtimer suspend failed when nearest alarm wakeup time is
less than 2 sec or rtc timer can not start.
In suspend/resume stress
On Friday 08 March 2013 04:46 AM, Greg KH wrote:
On Fri, Mar 08, 2013 at 12:57:37AM +0530, Laxman Dewangan wrote:
The alramtimer suspend failed when nearest alarm wakeup time is
less than 2 sec or rtc timer can not start.
In suspend/resume stress testing, we found that sometimes alramtimer
fail
On Fri, Mar 08, 2013 at 12:57:37AM +0530, Laxman Dewangan wrote:
> The alramtimer suspend failed when nearest alarm wakeup time is
> less than 2 sec or rtc timer can not start.
>
> In suspend/resume stress testing, we found that sometimes alramtimer
> failed to suspend and hence it cancel the susp
The alramtimer suspend failed when nearest alarm wakeup time is
less than 2 sec or rtc timer can not start.
In suspend/resume stress testing, we found that sometimes alramtimer
failed to suspend and hence it cancel the suspend ops. Add error prints
in suspend failure to provide more info when fail
5 matches
Mail list logo