All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15685] Kernel 2.6.33 fails to suspend (bisected)
Date: Wed, 7 Apr 2010 19:43:42 GMT	[thread overview]
Message-ID: <201004071943.o37Jhgah029119@demeter.kernel.org> (raw)
In-Reply-To: <bug-15685-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=15685





--- Comment #12 from Nix <nix@esperi.org.uk>  2010-04-07 19:25:49 ---
Er, how do I suspend without tuxonice? I've never used the in-tree swsusp
successfully (last time I tried I didn't just get a crash but massive
filesystem corruption, so I sort of haven't dared: reporting it would have
meant reproducing it, and I didn't want to touch it with a bargepole after
*that*).

Ideal would be a way to kick off the freezer and then just unfreeze without
suspending: that'd be pretty much risk-free...

--- Comment #13 from Rafael J. Wysocki <rjw@sisk.pl>  2010-04-07 19:43:32 ---
(In reply to comment #12)
> Er, how do I suspend without tuxonice? I've never used the in-tree swsusp
> successfully (last time I tried I didn't just get a crash but massive
> filesystem corruption, so I sort of haven't dared: reporting it would have
> meant reproducing it, and I didn't want to touch it with a bargepole after
> *that*).

It's kind of strange given that quite a few people use it daily, including
everyone using hibernation in the default openSUSE setup.

Anyway,

> Ideal would be a way to kick off the freezer and then just unfreeze without
> suspending: that'd be pretty much risk-free...

# echo core > /sys/power/pm_test
# echo disk > /sys/power/state

should do the trick.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--

  parent reply	other threads:[~2010-04-07 19:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-02 19:21 [Bug 15685] New: Kernel 2.6.33 fails to suspend (bisected) bugzilla-daemon
2010-04-02 19:30 ` [Bug 15685] " bugzilla-daemon
2010-04-02 20:26 ` bugzilla-daemon
2010-04-02 20:55 ` bugzilla-daemon
2010-04-02 21:02 ` bugzilla-daemon
2010-04-03 11:06 ` bugzilla-daemon
2010-04-03 18:29 ` bugzilla-daemon
2010-04-05 11:38 ` bugzilla-daemon
2010-04-05 11:40 ` bugzilla-daemon
2010-04-05 21:25 ` bugzilla-daemon
2010-04-07 13:40 ` bugzilla-daemon
2010-04-07 19:43 ` bugzilla-daemon [this message]
2010-04-07 23:17 ` bugzilla-daemon
2010-04-08  6:42 ` bugzilla-daemon
2010-04-08 18:39 ` bugzilla-daemon
2010-04-08 19:02 ` [Bug 15685] Kernel 2.6.33 w/ TuxOnIce " bugzilla-daemon

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=201004071943.o37Jhgah029119@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.