From: Frans Pop <elendil@planet.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Time travel experiment?
Date: Wed, 10 Sep 2008 18:56:24 +0200 [thread overview]
Message-ID: <200809101856.24997.elendil@planet.nl> (raw)
In-Reply-To: <200809101825.29276.elendil@planet.nl>
On Wednesday 10 September 2008, Frans Pop wrote:
> On Wednesday 10 September 2008, Frans Pop wrote:
> > > > $ date
> > > > Wed Jul 3 23:09:23 CEST 2024
Aaah, hmmm.
I'm trying to trace a problem with resume. Once in every 5-10 times resume
fails with dead display even though most times it resumes perfectly. So I
was trying the suggestion in Documentation/power/s2ram.txt and am doing
'echo 1 > /sys/power/pm_trace' before suspending.
Just now I find [1] which mentions that the trace info is saved in the
RTC, which I guess could well explain the jump. If that's what behind
this, wouldn't it make sense to mention that fact in s2ram.txt?
But I would not expect the RTC to get changed when the resume is
successful. Or does it just get updated with every resume step without a
reset to the pre-trace value on completion?
[1]https://lists.linux-foundation.org/pipermail/linux-pm/2006-June/008470.html
next prev parent reply other threads:[~2008-09-10 16:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 14:58 Time travel experiment? Frans Pop
2008-09-10 14:29 ` Alan Cox
2008-09-10 15:55 ` Frans Pop
2008-09-10 16:25 ` Frans Pop
2008-09-10 16:56 ` Frans Pop [this message]
2008-09-10 17:02 ` Linus Torvalds
2008-09-10 18:07 ` [patch] Document use of RTC in pm_trace Frans Pop
2008-09-13 11:20 ` Pavel Machek
2008-09-10 21:28 ` Time travel experiment? Willy Tarreau
2008-09-10 20:47 ` Geert Uytterhoeven
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=200809101856.24997.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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