From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
Linux Kernel M/L <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] what should 'uptime' be on suspend?
Date: Sat, 21 Jul 2007 17:29:29 +0100 [thread overview]
Message-ID: <20070721162929.GA13232@deepthought> (raw)
In-Reply-To: <46A2101D.5020400@tmr.com>
On Sat, Jul 21, 2007 at 09:54:37AM -0400, Bill Davidsen wrote:
>
> So is setting it to a random number considered correct behavior? Any of
> the first three values I mentioned would make sense, but the value I see
> is neither time since resume, time since power-on to do the resume, or
> any of the logical uptime values. That was the whole point of the
> original post, the uptime reported makes no sense at all.
>
I assumed you had booted for a short time, suspended, resumed, and
then noticed the uptime was longer than time since resume.
If you think there is a bug it might help to do a cold boot, at
some point note uptime and then immediately suspend, resume some time
later, immediately note uptime (including local time), keep it
running, and later monitor uptime against local time (i.e. the local
time will let you know the change you expect to see in uptime). You
might also want to confirm that the local time is maintained
correctly.
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
next prev parent reply other threads:[~2007-07-21 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 2:42 [RFC] what should 'uptime' be on suspend? Bill Davidsen
2007-07-20 17:17 ` Ken Moffat
2007-07-20 17:42 ` Randy Dunlap
2007-07-20 17:57 ` Ken Moffat
2007-07-20 21:49 ` Rafael J. Wysocki
2007-07-21 13:54 ` Bill Davidsen
2007-07-21 16:29 ` Ken Moffat [this message]
2007-07-23 15:44 ` Bill Davidsen
2007-07-25 14:02 ` Pavel Machek
2007-07-25 13:59 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070721162929.GA13232@deepthought \
--to=zarniwhoop@ntlworld.com \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).