From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
kernel list <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: CONFIG_NUMA breaks hibernation on x86-32 with PAE
Date: Tue, 11 Nov 2008 11:45:51 +0100 [thread overview]
Message-ID: <20081111104551.GE5464@elf.ucw.cz> (raw)
In-Reply-To: <200811101928.04565.rjw@sisk.pl>
On Mon 2008-11-10 19:28:03, Rafael J. Wysocki wrote:
> On Monday, 10 of November 2008, Andi Kleen wrote:
> > Ingo Molnar <mingo@elte.hu> writes:
> > >
> > > No good ideas - the bug description gives me the impression of memory
> > > maps save/restore hickup in the hibernation code - and memory maps are
> > > pretty much the only thing that are significantly different on NUMA.
> >
> > I assume the problem happened on a single node system.
> > On single node the memory map should be actually quite similar
> > to the UMA case.
>
> It is. However, the problem is 100% reproducible on any 32-bit single-node
> system with CONFIG_NUMA set, from what I can tell.
>
> It doesn't happen if the kernel is booted with highmem=0, so it looks like
> the code that saves highmem causes the problem to happen. However, this
> same code works well for all of the !CONFIG_NUMA cases and practically only
> the only non-open-coded it uses is kmap_atomic().
>
> > One possibility would be to bisect if it ever worked?
>
> Not sure it did, probably not. :-(
Well, interesting point would be just before this commit:
commit 8357376d3df21b7d6f857931a57ac50da9c66e26
tree daf2c369e9b79d24c1666323b3ae75189e482a4a
parent bf73bae6ba0dc4bd4f1e570feb34a06b72725af6
author Rafael J. Wysocki <rjw@sisk.pl> Wed, 06 Dec 2006 20:34:18 -0800
committer Linus Torvalds <torvalds@woody.osdl.org> Thu, 07 Dec 2006
08:39:27 -0800
[PATCH] swsusp: Improve handling of highmem
Currently swsusp saves the contents of highmem pages by copying
them to the
normal zone which is quite inefficient (eg. it requires two
normal pages
to be used for saving one highmem page). This may be improved by
using
highmem for saving the contents of saveable highmem pages.
...highmem handling was way simpler in those good old days ;-)
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-11-11 12:50 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 14:07 Pavel Machek
2008-11-10 7:52 ` Ingo Molnar
2008-11-10 7:55 ` Pavel Machek
2008-11-10 8:04 ` Ingo Molnar
2008-11-10 8:28 ` Pavel Machek
2008-11-10 12:53 ` Ingo Molnar
2008-11-10 18:05 ` Andi Kleen
2008-11-10 18:33 ` Rafael J. Wysocki
2008-11-10 19:07 ` Andi Kleen
2008-11-10 12:55 ` Andi Kleen
2008-11-10 18:28 ` Rafael J. Wysocki
2008-11-11 10:30 ` Pavel Machek
2008-11-11 14:17 ` Rafael J. Wysocki
2008-11-11 10:45 ` Pavel Machek [this message]
2008-11-11 14:20 ` Rafael J. Wysocki
2008-11-11 15:03 ` Pavel Machek
2008-11-11 16:47 ` Rafael J. Wysocki
2008-11-12 10:49 ` Pavel Machek
2008-11-12 21:57 ` Rafael J. Wysocki
2008-11-12 22:22 ` [PATCH] x86: Hibernate: Fix breakage on x86_32 with CONFIG_NUMA set (was: Re: CONFIG_NUMA breaks hibernation on x86-32 with PAE) Rafael J. Wysocki
2008-11-12 22:26 ` [PATCH] x86: Make NUMA on 32-bit depend on EXPERIMENTAL again Rafael J. Wysocki
2008-11-12 22:29 ` Ingo Molnar
2008-11-12 22:29 ` [PATCH] x86: Hibernate: Fix breakage on x86_32 with CONFIG_NUMA set (was: Re: CONFIG_NUMA breaks hibernation on x86-32 with PAE) Ingo Molnar
2008-11-10 8:24 ` CONFIG_NUMA breaks hibernation on x86-32 with PAE KAMEZAWA Hiroyuki
2008-11-10 8:27 ` Pavel Machek
2008-11-10 8:28 ` Ingo Molnar
2008-11-10 18:23 ` Rafael J. Wysocki
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=20081111104551.GE5464@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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®