From: Pavel Machek <pavel@ucw.cz>
To: Marcus Better <marcus@better.se>
Cc: linux-pm@lists.osdl.org
Subject: Re: spontaneous second suspend-to-RAM
Date: Sat, 9 Jun 2007 15:14:33 +0200 [thread overview]
Message-ID: <20070609131431.GA3397@elf.ucw.cz> (raw)
In-Reply-To: <f48tuv$q57$1@sea.gmane.org>
Hi!
> I'm experiencing a spontaneous suspend to RAM occasionally. It happens about
> thirty seconds after resuming from RAM. It happened a few times today. I'm
> not sure if it's a kernel problem or something else, possibly kpowersave
> which I use to suspend, but I haven't upgraded that in a while. (kpowersave
> uses s2ram.)
>
> This is kernel 2.6.22-rc4 (x86_64) with Debian on a Thinkpad R60, Intel Core
> 2 Duo, and uswsusp.
Try reproducing it in init=/bin/bash to see if it is userspace or
kernel problem. Or just kill -9 -1 after resume ;-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2007-06-09 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 12:33 spontaneous second suspend-to-RAM Marcus Better
2007-06-09 13:14 ` Pavel Machek [this message]
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=20070609131431.GA3397@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-pm@lists.osdl.org \
--cc=marcus@better.se \
/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