From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@zip.com.au>,
agruen@suse.de
Subject: swsusp: 8-order memory allocations problem (was: Re: Fix random crashes in x86-64 swsusp)
Date: Fri, 8 Oct 2004 22:59:43 +0200 [thread overview]
Message-ID: <200410082259.43627.rjw@sisk.pl> (raw)
In-Reply-To: <20041006220600.GB25059@elf.ucw.cz>
Hi,
On Thursday 07 of October 2004 00:06, Pavel Machek wrote:
> Hi!
>
> fix_processor_context was calling functions marked __init on x86-64;
> bad idea. Maybe we should memset freed memory to zero so such bugs are
> prevented?
>
> Thanks to Rafael for keeping notifying me about this bug, and someone
> get me yet another brown paper bag.
>
> Anyway, this should fix it, please apply,
[-- snip --]
The patch apparently fixes the problem that I have reported, so thanks a lot,
Pavel. After it's been fixed, however, I often get things like that:
PM: snapshotting memory.
swsusp: critical section:
..<7>[nosave pfn
0x58b]...........................................................................
............................................swsusp: Need to copy 31927 pages
suspend: (pages needed: 31927 + 512 free: 98952)
hibernate.sh: page allocation failure. order:8, mode:0x120
Oct 8 14:15:57 albercik kernel:
Call Trace:<ffffffff8016eb2d>{__alloc_pages+749}
<ffffffff8016ebd1>{__get_free_pages+33}
<ffffffff80161a23>{suspend_prepare_image+531}
<ffffffff8026d7a7>{pci_device_suspend+71}
<ffffffff80161cb6>{swsusp_swap_check+22}
<ffffffff802ea112>{suspend_device+50}
<ffffffff80120d0c>{swsusp_arch_suspend+124}
<ffffffff801610cc>{swsusp_suspend+12}
<ffffffff8016222a>{pm_suspend_disk+90}
<ffffffff8015fe04>{enter_state+68}
<ffffffff802adc0d>{acpi_system_write_sleep+100}
<ffffffff80193914>{vfs_write+228}
<ffffffff80193a53>{sys_write+83} <ffffffff80110c72>{system_call+126}
Oct 8 14:16:05 albercik kernel:
suspend: Allocating pagedir failed.
It's sort of strange, because there were 250 meg of RAM available, out of 500,
at that time.
Anyway I was able to suspend the machine after the above one had happened (I
stopped an app occupying some memory and then the box suspended), but then I
got a spectacular crash on resume (unfortunately I was unable to save the
trace, but I'll try to reproduce it).
Greets,
RJW
--
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
-- Lewis Carroll "Alice's Adventures in Wonderland"
next prev parent reply other threads:[~2004-10-08 20:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 21:14 2.6.9-rc3[+recent swsusp patches]: swsusp kernel-preemption-unfriendly? Rafael J. Wysocki
2004-10-05 21:27 ` Pavel Machek
2004-10-06 8:55 ` Rafael J. Wysocki
2004-10-06 8:54 ` Pavel Machek
2004-10-06 10:06 ` Rafael J. Wysocki
2004-10-06 10:12 ` Pavel Machek
2004-10-06 21:46 ` Rafael J. Wysocki
2004-10-06 22:06 ` Fix random crashes in x86-64 swsusp Pavel Machek
2004-10-06 22:13 ` [kernel] " Andi Kleen
2004-10-06 22:25 ` Andrew Morton
2004-10-06 22:24 ` Pavel Machek
2004-10-08 20:59 ` Rafael J. Wysocki [this message]
2004-10-10 13:48 ` swsusp: 8-order memory allocations problem (was: Re: Fix random crashes in x86-64 swsusp) Pavel Machek
2004-10-10 18:28 ` Andrew Morton
2004-10-13 17:24 ` Rafael J. Wysocki
2004-10-14 15:37 ` swsusp: 8-order memory allocations problem (update) 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=200410082259.43627.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=agruen@suse.de \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox