From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Alan Jenkins <sourcejedi.lkml@googlemail.com>,
Mel Gorman <mel@csn.ul.ie>,
hugh.dickins@tiscali.co.uk, Pavel Machek <pavel@ucw.cz>,
pm list <linux-pm@lists.linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: s2disk hang update
Date: Wed, 24 Feb 2010 10:20:37 +0900 [thread overview]
Message-ID: <20100224102037.2cca4f83.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <201002232213.56455.rjw@sisk.pl>
On Tue, 23 Feb 2010 22:13:56 +0100
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> Well, it still looks like we're waiting for create_workqueue_thread() to
> return, which probably is trying to allocate memory for the thread
> structure.
>
> My guess is that the preallocated memory pages freed by
> free_unnecessary_pages() go into a place from where they cannot be taken for
> subsequent NOIO allocations. I have no idea why that happens though.
>
> To test that theory you can try to change GFP_IOFS to GFP_KERNEL in the
> calls to clear_gfp_allowed_mask() in kernel/power/hibernate.c (and in
> kernel/power/suspend.c for completness).
>
If allocation of kernel threads for stop_machine_run() is the problem,
What happens when
1. use CONIFG_4KSTACK
or
2. make use of stop_machine_create(), stop_machine_destroy().
A new interface added by this commit.
http://git.kernel.org/?p=linux/kernel/git/torvalds/ linux-2.6.git;a=commit;h=9ea09af3bd3090e8349ca2899ca2011bd94cda85
You can do no-fail stop_machine_run().
Thanks,
-Kame
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-02-24 1:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9b2b86521001020703v23152d0cy3ba2c08df88c0a79@mail.gmail.com>
[not found] ` <201002222017.55588.rjw@sisk.pl>
[not found] ` <9b2b86521002230624g20661564mc35093ee0423ff77@mail.gmail.com>
2010-02-23 21:13 ` Rafael J. Wysocki
2010-02-24 1:20 ` KAMEZAWA Hiroyuki [this message]
2010-02-24 20:19 ` Alan Jenkins
2010-02-24 20:36 ` Rafael J. Wysocki
2010-02-24 16:23 ` Alan Jenkins
2010-02-24 20:52 ` Rafael J. Wysocki
2010-02-25 13:10 ` Alan Jenkins
2010-02-25 20:04 ` Rafael J. Wysocki
2010-02-26 9:26 ` Alan Jenkins
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=20100224102037.2cca4f83.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=hugh.dickins@tiscali.co.uk \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mel@csn.ul.ie \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=sourcejedi.lkml@googlemail.com \
/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