From: "Toralf Förster" <toralf.foerster@gmx.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3.5-rcX: wakeup after s2ram doesn't work after a longer sleep time
Date: Mon, 16 Jul 2012 15:50:22 +0200 [thread overview]
Message-ID: <50041C1E.8070203@gmx.de> (raw)
In-Reply-To: <201207152221.48232.rjw@sisk.pl>
On 07/15/2012 10:21 PM, Rafael J. Wysocki wrote:
> On Sunday, July 15, 2012, Toralf Förster wrote:
>> My ThinkPad T400 (Gentoo Linux booted from an external USB drive) does
>> not wake up after s2ram, if the sleep time was longer than about 1 hour.
>> I'm unsure whether this started after 3.5-rc5, at least with -rc7 I
>> observed this now several times. Unfortunately it is not 100% reproduceable.
>>
>> 3.4.x works flawlessly.
>>
>> Any idea whether a particular commit could be the culprit ? (Bisecting
>> such an issue is a night mare)
>
> Please check
>
> commit 5baefd6d84163443215f4a99f6a20f054ef11236
> Author: John Stultz <johnstul@us.ibm.com>
> Date: Tue Jul 10 18:43:25 2012 -0400
>
> hrtimer: Update hrtimer base offsets each hrtimer_interrupt
>
> Thanks,
> Rafael
>
No,
reverting doesn#t help.
I can r2ram several times in a row w/o problems, if the sleep time as
within seconds.
After 20 min however the system doesn't came back (the internal hard
disk spins up, but the sleep-state-led is still on).
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
next prev parent reply other threads:[~2012-07-16 14:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 19:28 3.5-rcX: wakeup after s2ram doesn't work after a longer sleep time Toralf Förster
2012-07-15 20:21 ` Rafael J. Wysocki
2012-07-16 13:50 ` Toralf Förster [this message]
2012-07-16 17:47 ` Rafael J. Wysocki
2012-07-16 18:39 ` Toralf Förster
2012-07-16 19:42 ` Rafael J. Wysocki
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=50041C1E.8070203@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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