From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Bojan Smojver" <bojan@rexursive.com>
Cc: linux-kernel@vger.kernel.org, Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v8]: Improve performance of LZO/plain hibernation
Date: Thu, 13 Oct 2011 23:26:01 +0200 [thread overview]
Message-ID: <201110132326.02041.rjw@sisk.pl> (raw)
In-Reply-To: <2409186928.1003010428@rexursive.com>
On Thursday, October 13, 2011, Bojan Smojver wrote:
> ------- Original message -------
> > From: Rafael J. Wysocki
>
> >> I get a kernel panic on a test box using a x86_64 kernel with this patch
> >> applied.
> >
> > The panic happens during late resume, when trying to switch to the
> > hibernated
> > kernel.
>
> In an effort to test this whole thing a bit more, I took today's kernel
> from Linus' repo and applied v11 of my patch. I compiled this on a single
> cpu machine this time, with 768 MB of memory (in today's terms, this laptop
> would not pass as a smartphone :-), running F-16 beta.. The system has
> radeon graphics (my other system, where I initially developed the patch,
> has intel). Also, this was a 32-bit box, as opposed to my other system,
> which is 64-bit.
>
> I was getting kernel trouble on repeated hibernate/thaw cycles on both
> systems when KMS was enabled. With nomodeset passed into the kernel, both
> systems would go through 50+ cycles (this was my test loop) with no
> trouble. Whether my patch was applied or not didn't matter - I was getting
> trouble with Fedora supplied kernels as well, after a few cycles.
>
> So, I don't know for sure, but it seems to me something is amiss in KMS
> when it comes to hibernation.
If your system is 64-bit, then the patch below may help.
Thanks,
Rafael
---
arch/x86/mm/init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/arch/x86/mm/init.c
===================================================================
--- linux.orig/arch/x86/mm/init.c
+++ linux/arch/x86/mm/init.c
@@ -63,9 +63,9 @@ static void __init find_early_table_spac
#ifdef CONFIG_X86_32
/* for fixmap */
tables += roundup(__end_of_fixed_addresses * sizeof(pte_t), PAGE_SIZE);
+#endif
good_end = max_pfn_mapped << PAGE_SHIFT;
-#endif
base = memblock_find_in_range(start, good_end, tables, PAGE_SIZE);
if (base == MEMBLOCK_ERROR)
next prev parent reply other threads:[~2011-10-13 21:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-30 0:27 Bojan Smojver
2011-10-04 22:07 ` Rafael J. Wysocki
2011-10-05 1:07 ` Bojan Smojver
2011-10-06 18:37 ` Rafael J. Wysocki
2011-10-06 18:45 ` Rafael J. Wysocki
2011-10-06 22:23 ` Bojan Smojver
2011-10-07 3:20 ` Bojan Smojver
2011-10-07 3:39 ` Bojan Smojver
2011-10-07 23:33 ` Bojan Smojver
2011-10-09 2:57 ` Bojan Smojver
2011-10-09 7:54 ` Bojan Smojver
2011-10-09 9:22 ` Pekka Enberg
2011-10-09 10:19 ` Bojan Smojver
2011-10-09 22:24 ` Bojan Smojver
2011-10-10 7:12 ` Bojan Smojver
2011-10-13 11:00 ` Bojan Smojver
2011-10-13 21:26 ` Rafael J. Wysocki [this message]
2011-10-13 21:44 ` Bojan Smojver
2011-10-13 21:57 ` Rafael J. Wysocki
2011-10-13 21:56 ` Bojan Smojver
2011-10-14 2:01 ` Bojan Smojver
2011-10-14 6:14 ` Pekka Enberg
2011-10-14 6:50 ` Bojan Smojver
2011-10-15 6:28 ` Bojan Smojver
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=201110132326.02041.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=bojan@rexursive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
/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®