On Wednesday 24 February 2010, KAMEZAWA Hiroyuki wrote: > On Tue, 23 Feb 2010 22:13:56 +0100 > "Rafael J. Wysocki" <rjw@xxxxxxx> 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(). Well, that would probably help in this particular case, but the root cause seems to be that the (theoretically) freed memory cannot be used for NOIO allocations for some reason, which is shown by the Alan's testing. Generally speaking, we use __free_page() to release some pages preallocated for the hibernation image, but the memory subsystem refuses to use these pages for NOIO allocations made later. However, it evidently is able to use them is __GFP_WAIT is unset in the mask. Is this behavior intentional? Rafael -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
