From: Brad Campbell <brad@wasp.net.au>
To: linux-pm@lists.linux-foundation.org
Subject: Linux 3.0-rc4 intermittent failure to resume
Date: Thu, 23 Jun 2011 08:21:07 +0800 [thread overview]
Message-ID: <4E0286F3.6030003@wasp.net.au> (raw)
G'day all,
I've recently moved from tuxonice to mainline uswsusp. I'm getting intermittent failure to resume
problems. No message in dmesg that I can find, it just boots clean. Is there something I can do to
get some debug info on this? It's really, really annoying.
About 75% of the time it works perfectly, and I can find no rhyme or reason to why it suddenly just
decides to ignore the saved state.
32 bit userspace with a statically linked 64 bit s2disk, s2both & resume. 64 bit kernel.
Brad
--
Dolphins are so intelligent that within a few weeks they can
train Americans to stand at the edge of the pool and throw them
fish.
next reply other threads:[~2011-06-23 0:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 0:21 Brad Campbell [this message]
2011-06-23 12:02 ` Linux 3.0-rc4 intermittent failure to resume Rafael J. Wysocki
2011-06-24 2:41 ` Brad Campbell
2011-06-28 2:39 ` Brad Campbell
2011-06-29 5:34 ` Brad Campbell
2011-06-29 13:23 ` Brad Campbell
2011-06-29 19:34 ` Rafael J. Wysocki
2011-06-30 0:21 ` Brad Campbell
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=4E0286F3.6030003@wasp.net.au \
--to=brad@wasp.net.au \
--cc=linux-pm@lists.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