From: Stefan Seyfried <seife@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, barryn@pobox.com,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [Bug 4298] swsusp fails to suspend if CONFIG_DEBUG_PAGEALLOC is also enabled
Date: Mon, 07 Mar 2005 09:01:47 +0100 [thread overview]
Message-ID: <422C0A6B.1060700@suse.de> (raw)
In-Reply-To: <20050306195954.6d13cff9.akpm@osdl.org>
Andrew Morton wrote:
> Pavel Machek <pavel@ucw.cz> wrote:
>> Okay, that is because low-level assembly requires PSE (4mb pages for
>> kernel) and DEBUG_PAGEALLOC disables that capability.
>>
>> If you feel like rewriting assembly code to turn off paging (and thus
>> working with PSE), go ahead, but I do not think it is worth the
>> trouble.
>>
>> OTOH we should at least tell people what went wrong, some people seen
>> same problem on VIA cpus... Please apply,
>>
>
> Isn't some Kconfig solution appropriate here?
Yes, but only for the CONFIG_DEBUG_PAGEALLOC case, it does not solve the
"cpu has no PSE" case for VIA CPUs. So the Kconfig solution is an extra
bonus.
Stefan
next prev parent reply other threads:[~2005-03-07 8:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050306030852.23eb59db.akpm@osdl.org>
2005-03-06 22:57 ` [Bug 4298] swsusp fails to suspend if CONFIG_DEBUG_PAGEALLOC is also enabled Pavel Machek
2005-03-07 3:59 ` Andrew Morton
2005-03-07 5:12 ` [PATCH] kconfig: DEBUG_PAGEALLOC and SOFTWARE_SUSPEND are incompatible on i386 Barry K. Nathan
2005-03-07 9:14 ` Pavel Machek
2005-03-07 8:01 ` Stefan Seyfried [this message]
2005-03-07 8:41 ` [Bug 4298] swsusp fails to suspend if CONFIG_DEBUG_PAGEALLOC is also enabled Nigel Cunningham
2005-03-07 9:22 ` Barry K. Nathan
2005-03-07 9:35 ` Pavel Machek
2005-03-07 17:58 ` Barry K. Nathan
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=422C0A6B.1060700@suse.de \
--to=seife@suse.de \
--cc=akpm@osdl.org \
--cc=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.