On Wednesday 10 September 2008, Frans Pop wrote: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 --
| Greg Kroah-Hartman | [PATCH 004/196] Chinese: add translation of SubmittingPatches |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Laurent Riffard | Re: 2.6.25-rc2-mm1: WARNING at arch/x86/mm/ioremap.c:129 |
| Alan Cox | Re: x86: 4kstacks default |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 34/37] dccp: Auto-load (when supported) CCID plugins for negotiation |
| Maciej W. Rozycki | Re: [PATCH] PHYLIB: IRQ event workqueue handling fixes |
| John P Poet | Realtek 8111C transmit timed out |
git: | |
