On Wednesday 10 September 2008, Frans Pop wrote:

quoted text
> 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

--

unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

the body of a message to majordomo@vger.kernel.org

More majordomo info at  http://vger.kernel.org/majordomo-info.html

Please read the FAQ at  http://www.tux.org/lkml/