From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@zip.com.au>,
kernel list <linux-kernel@vger.kernel.org>,
Patrick Mochel <mochel@digitalimplant.org>
Subject: swsusp (2.6.9-rc1-mm4 + bigdiff): Unable to handle kernel paging request
Date: Sun, 12 Sep 2004 12:32:48 +0200 [thread overview]
Message-ID: <200409121232.48759.rjw@sisk.pl> (raw)
In-Reply-To: <200409112359.43265.rjw@sisk.pl>
On Saturday 11 of September 2004 23:59, Rafael J. Wysocki wrote:
> On Saturday 11 of September 2004 21:22, Rafael J. Wysocki wrote:
> > On Saturday 11 of September 2004 11:50, Rafael J. Wysocki wrote:
[- snip -]
> After issuing "echo 4 > /proc/acpi/sleep" I get things similar to this:
Here goes a similar trace of that sort:
Stopping tasks:
====================================================================|
Freeing memory... done (97366 pages freed)
PM: Attempting to suspend to disk.
PM: snapshotting memory.
swsusp: critical section:
[nosave pfn 0x5ef]swsusp: Need to copy 26830 pages
suspend: (pages needed: 26830 + 512 free: 104049)
[nosave pfn 0x5ef]swsusp: critical section/: done (27086 pages copied)
Unable to handle kernel paging request at ffffffff93d9fdff RIP:
<ffffffff805cd401>{syscall_init+1}
PML4 103027 PGD 105027 PMD 0
Oops: 0002 [1]
CPU 0
Modules linked in: usbserial parport_pc lp parport joydev sg sd_mod sr_mod
scsi_mod ohci1394 yenta_socket ieee1394 pcmcia_core cpufreq_ud
Pid: 17970, comm: bash Not tainted 2.6.9-rc1-mm4
RIP: 0010:[<ffffffff805cd401>] <ffffffff805cd401>{syscall_init+1}
RSP: 0000:000001000a089e40 EFLAGS: 00010402
RAX: 0000000000000089 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 000001000a089e68 RDI: ffffffff804741d0
RBP: ffffffff80487140 R08: 0000000000000000 R09: 0000000000000004
R10: 00000000ffffffff R11: 0000000000000000 R12: 0000000000000003
R13: 0000000000000002 R14: 0000002a955a5000 R15: 0000000000000000
FS: 0000002a95d330a0(0000) GS:ffffffff805c16c0(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffff93d9fdff CR3: 0000000000101000 CR4: 00000000000006e0
Process bash (pid: 17970, threadinfo 000001000a088000, task 0000010016f7aa10)
Stack: ffffffff801211d9 0000000000000002 ffffffff80487140 8000895b7e402080
00000000ffffffff ffffffff8053de00 ffffffff80121448 0000000000000000
ffffffff80161033 0000000000000002
Call Trace:<ffffffff801211d9>{fix_processor_context+137}
<ffffffff80121448>{__restore_processor_state+120}
<ffffffff80161033>{swsusp_suspend+19}
<ffffffff80161ee4>{pm_suspend_disk+100}
<ffffffff8015fa26>{enter_state+70}
<ffffffff803032c4>{acpi_system_write_sleep+107}
<ffffffff8018ff14>{vfs_write+228} <ffffffff80190053>{sys_write+83}
<ffffffff80110be2>{system_call+126}
Code: d9 93 ff fd d9 93 ff fe da 93 ff fd da 91 ff fc d9 90 ff fd
RIP <ffffffff805cd401>{syscall_init+1} RSP <000001000a089e40>
CR2: ffffffff93d9fdff
It is easily reproducible. It suffices to run X with KDE and some apps with
it and try "echo 4 > /proc/acpi/sleep" to get one of those (100% of the time
or so).
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-09-12 10:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 15:42 swsusp: kill crash when too much memory is free Pavel Machek
2004-09-09 22:01 ` Rafael J. Wysocki
2004-09-10 9:40 ` Pavel Machek
2004-09-10 10:45 ` Rafael J. Wysocki
2004-09-10 17:26 ` Rafael J. Wysocki
2004-09-10 22:29 ` Pavel Machek
2004-09-11 9:50 ` Rafael J. Wysocki
2004-09-11 19:22 ` Rafael J. Wysocki
2004-09-11 21:59 ` Rafael J. Wysocki
2004-09-12 10:32 ` Rafael J. Wysocki [this message]
2004-09-12 20:42 ` Pavel Machek
2004-09-12 21:16 ` Rafael J. Wysocki
2004-09-12 21:40 ` Stefan Seyfried
2004-09-12 22: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=200409121232.48759.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ak@suse.de \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.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 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®