From: "Zdenek Kabelac" <zdenek.kabelac@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Suspend to memory is freezing my machine
Date: Tue, 3 Jun 2008 10:10:10 +0200 [thread overview]
Message-ID: <c4e36d110806030110t3e4f406fy4d3afe6c74362501@mail.gmail.com> (raw)
In-Reply-To: <c4e36d110805262344r16c64f3dweb127c7fd0fc8f36@mail.gmail.com>
2008/5/27 Zdenek Kabelac <zdenek.kabelac@gmail.com>:
> 2008/5/25 Rafael J. Wysocki <rjw@sisk.pl>:
>> On Sunday, 25 of May 2008, Zdenek Kabelac wrote:
>>> 2008/5/24 Rafael J. Wysocki <rjw@sisk.pl>:
>>> > On Thursday, 22 of May 2008, Zdenek Kabelac wrote:
>>> >> Hello Rafael
>>> >>
>>> >>
>>
>> If you use s2ram, please check if "echo mem > /sys/power/state" works instead.
>
> The problem occurs also with plain echo 'mem' - I've already checked before.
> Just resently I've discovered that actually I've had some serious
> problem with CONFIG_DEBUG_PAGEALLOC option. Unsure if this thing could
> be related to my deadlocking problem during suspend - I'll watch, if
> the freeze will be still ocurring even without this option.
>
> I'll make probably a separate post about my debug option problem.
Hello
It looks like from the time I've disabled CONFIG_DEBUG_PAGEALLOC
option I've not seen a single freeze during the suspend - I'll
continue to watch this - but I guess it's the key part of my problem.
Zdenek
next prev parent reply other threads:[~2008-06-03 8:10 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 7:37 Zdenek Kabelac
2008-05-04 10:40 ` Rafael J. Wysocki
2008-05-04 12:32 ` Jacek Luczak
2008-05-04 21:02 ` Zdenek Kabelac
2008-05-22 9:40 ` Zdenek Kabelac
2008-05-24 21:01 ` Rafael J. Wysocki
2008-05-25 8:56 ` Zdenek Kabelac
2008-05-25 8:59 ` Zdenek Kabelac
2008-05-25 12:24 ` Rafael J. Wysocki
2008-05-27 6:44 ` Zdenek Kabelac
2008-06-03 8:10 ` Zdenek Kabelac [this message]
2008-05-05 14:10 ` Pavel Machek
2008-05-06 9:15 ` Zdenek Kabelac
2008-05-07 14:33 ` Andrea Arcangeli
2008-05-07 14:43 ` Zdenek Kabelac
[not found] <fa.4esVkXHbwOL+Pzatd+lYSGawfns@ifi.uio.no>
[not found] ` <fa.zsdi5UBi6URzBaRSfFXIc6F7kHk@ifi.uio.no>
[not found] ` <fa.plXIUcQIe19WMbpH4aKYo6JX1RQ@ifi.uio.no>
2008-05-04 17:36 ` Robert Hancock
2008-05-04 17:42 ` Jacek Luczak
2008-05-04 18:01 ` Robert Hancock
2008-05-04 18:52 ` Jacek Luczak
2008-05-04 19:44 ` Jacek Luczak
2008-05-04 21:06 ` Robert Hancock
2008-05-07 20:29 ` Jacek Luczak
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=c4e36d110806030110t3e4f406fy4d3afe6c74362501@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--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
all inboxes | Powered by JetHome®