From: Stefan Seyfried <seife@suse.de>
To: Pavel Machek <pavel@ucw.cz>
Cc: ncunningham@linuxmail.org, linux-kernel@vger.kernel.org,
pascal.schmidt@email.de
Subject: Re: 2.6.9-rc2-mm1 swsusp bug report.
Date: Mon, 11 Oct 2004 11:56:18 +0200 [thread overview]
Message-ID: <416A58C2.6090304@suse.de> (raw)
In-Reply-To: <20040925101640.GB4039@elf.ucw.cz>
Hi,
Pavel Machek wrote:
> OTOH this is first report of this failure. If it fails once in a blue
> moon, it is probably better to let it fail than waste memory.
PM: Attempting to suspend to disk.
PM: snapshotting memory.
swsusp: critical section:
swsusp: Saving Highmem
[nosave pfn 0x3be]<7>[nosave pfn 0x3bf]swsusp: Need to copy 30519 pages
suspend: (pages needed: 30519 + 512 free: 100469)
do_acpi_sleep: page allocation failure. order:7, mode:0x120
[<c013a628>] __alloc_pages+0x3a8/0x3b0
[<c013a648>] __get_free_pages+0x18/0x30
[<c0132c37>] alloc_pagedir+0x17/0x60
[<c0132ddb>] swsusp_alloc+0x4b/0xa0
[<c0132e63>] suspend_prepare_image+0x33/0x80
[<c028beda>] swsusp_arch_suspend+0x2a/0x30
[<c0132f1b>] swsusp_suspend+0x2b/0x40
[<c01332ad>] pm_suspend_disk+0x3d/0xb0
[<c0131765>] enter_state+0x85/0x90
[<c01318b1>] state_store+0xc1/0xc3
[<c01317f0>] state_store+0x0/0xc3
[<c01852e6>] subsys_attr_store+0x26/0x30
[<c018548d>] flush_write_buffer+0x1d/0x30
[<c01854c9>] sysfs_write_file+0x29/0x40
[<c01854a0>] sysfs_write_file+0x0/0x40
[<c0150c7f>] vfs_write+0x9f/0x100
[<c0150d8c>] sys_write+0x3c/0x70
[<c0105c69>] sysenter_past_esp+0x52/0x79
suspend: Allocating pagedir failed.
swsusp: Restoring Highmem
this happened right now, after running fine over the weekend and doing a
successful suspend/resume cycle this morning.
It was a "battery critical" suspend, so this is not nice :-( I had about
2 minutes left until hard powerdown during which i tried to get it to
suspend but failed. Yes, userspace should handle the "failed
battery-critical suspend" case better and probably call "shutdown -h now".
Stefan
next prev parent reply other threads:[~2004-10-11 13:53 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2HO0C-4xh-29@gated-at.bofh.it>
[not found] ` <2I5b2-88s-15@gated-at.bofh.it>
[not found] ` <2I5E5-6h-19@gated-at.bofh.it>
[not found] ` <2I7Zd-1TK-11@gated-at.bofh.it>
2004-09-25 1:05 ` 2.6.9-rc2-mm1 swsusp bug report Pascal Schmidt
2004-09-25 10:16 ` Pavel Machek
2004-10-10 18:17 ` Jan Rychter
2004-10-11 13:32 ` Pavel Machek
2004-10-11 14:53 ` Jan Rychter
2004-10-17 19:10 ` Pavel Machek
2004-10-17 21:40 ` Nigel Cunningham
2004-10-11 9:56 ` Stefan Seyfried [this message]
2004-10-11 14:59 ` Pavel Machek
2004-10-11 17:18 ` Stefan Seyfried
2004-10-11 19:58 ` Rafael J. Wysocki
2004-10-12 8:55 ` Pavel Machek
2004-10-13 17:29 ` Rafael J. Wysocki
2004-10-14 21:47 ` swsusp: 8-order allocation failure on demand (was: Re: 2.6.9-rc2-mm1 swsusp bug report.) Rafael J. Wysocki
2004-10-14 21:54 ` swsusp: 8-order allocation failure on demand (update) Rafael J. Wysocki
2004-10-16 16:43 ` Pavel Machek
2004-10-16 19:31 ` Rafael J. Wysocki
2004-10-16 20:40 ` Pavel Machek
2004-10-16 21:05 ` Rafael J. Wysocki
2004-10-16 21:25 ` Pavel Machek
2004-09-24 2:19 2.6.9-rc2-mm1 swsusp bug report Kevin Fenzi
2004-09-24 14:37 ` Pavel Machek
2004-09-24 21:09 ` Kevin Fenzi
2004-09-24 23:40 ` Nigel Cunningham
2004-09-25 1:45 ` Kevin Fenzi
2004-09-25 11:53 ` Nigel Cunningham
2004-09-25 12:22 ` Nick Piggin
2004-09-25 12:56 ` William Lee Irwin III
2004-09-25 13:21 ` Nigel Cunningham
2004-09-25 12:56 ` Nigel Cunningham
2004-09-25 13:38 ` Nick Piggin
2004-09-25 13:03 ` Nigel Cunningham
2004-09-25 15:45 ` Pavel Machek
2004-09-25 22:03 ` Nigel Cunningham
2004-09-26 10:04 ` Pavel Machek
2004-09-26 21:59 ` Nigel Cunningham
2004-09-26 22:43 ` Pavel Machek
2004-09-27 10:12 ` Nigel Cunningham
2004-09-26 16:18 ` Marcelo Tosatti
2004-09-26 18:39 ` Pavel Machek
2004-09-25 10:15 ` Pavel Machek
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=416A58C2.6090304@suse.de \
--to=seife@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.org \
--cc=pascal.schmidt@email.de \
--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.