From: Mantas <grawity@gmail.com>
To: Srivatsa Bhat <srivatsasbhat@gmail.com>
Cc: maciej.rutecki@gmail.com, "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
suspend-devel@lists.sourceforge.net,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Subject: Re: 3.2-git - freeze during hibernation
Date: Sun, 22 Jan 2012 17:42:55 +0200 [thread overview]
Message-ID: <4F1C2E7F.1000902@gmail.com> (raw)
In-Reply-To: <CAE368AS+FjoTvtBT0A2Qa0RXrJYbgxNdv6OOvD3cnmsTrLsRyQ@mail.gmail.com>
On 2012-01-22 10:32, Srivatsa Bhat wrote:
> On Sun, Jan 22, 2012 at 1:35 PM, Maciej Rutecki
> <maciej.rutecki@gmail.com <mailto:maciej.rutecki@gmail.com>> wrote:
>
> (Add CC to Rafael)
>
> On piątek, 13 stycznia 2012 o 14:31:44 Mantas wrote:
> > Using uswsusp git-17789a0 and Linux git-v3.2-6540-g4c4d285, suspend to
> > disk freezes right before writing the memory to disk -- "Saving X
> image
> > data pages" appears, but the percentage does not, nor is there any
> disk
> > activity; all I can do is reboot using Alt+SysRq.
> >
> > Same version of uswsusp, both suspend to memory and disk, worked
> > perfectly with Linux v3.2 release and earlier versions. The device is
> > ASUS K52JT. Any hints?
>
>
> Hi,
>
> Could you please try the patch posted at:
> https://lkml.org/lkml/2012/1/19/177 ?
It does fix this particular issue; the suspend image is written correctly.
However, now it hangs at the "Suspending consoles" message -- sometimes
before writing image, sometimes after...
I will try the same patch against latest linux-git and see if there are
any changes.
--
Mantas M.
next prev parent reply other threads:[~2012-01-22 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-13 13:31 3.2-git - freeze during hibernation Mantas
2012-01-22 8:05 ` Maciej Rutecki
[not found] ` <CAE368AS+FjoTvtBT0A2Qa0RXrJYbgxNdv6OOvD3cnmsTrLsRyQ@mail.gmail.com>
2012-01-22 15:42 ` Mantas [this message]
2012-01-22 18:03 ` Mantas
2012-01-23 4:43 ` Srivatsa S. Bhat
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=4F1C2E7F.1000902@gmail.com \
--to=grawity@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=srivatsasbhat@gmail.com \
--cc=suspend-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.