From: "Simon Holm Thøgersen" <account@cs.aau.dk>
To: Pavel Machek <pavel@suse.cz>, "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-pm@lists.linux-foundation.org
Subject: Crash during suspend to disk
Date: Thu, 20 Nov 2008 13:41:56 +0100 [thread overview]
Message-ID: <1227184916.4855.31.camel@odie.local> (raw)
Hi
I hope this information is sufficient to debug my problem, though it
unfortunately is somewhat incomplete. I took two pictures of the OOPS
with my mobile phone, but unfortunately the picture of the upper part is
so blurred that it is unreadable. Apparently I have to be in a hurry
getting out of the door for this to happen. Here is what I got from the
lower part
Call Trace:
__blkdev_put
swsusp_write
hibernate
state_store
state_store
state_store
kobj_attr_store
sysfs_write_file
sysfs_write_file
vfs_write
sys_write
sysenter_do_call
Code: ......
EIP: [<...>] iput
---[ end trace ........................... ]---
There is a lot of blanks here that I should be able provide on request
as well.
The problem occured in my third attempt in quick succession to suspend
to disk. The first two did not succeed due to insufficient free swap. I
got 768 MB ram and a ~1 GB swap partition. I believe top said something
like Mem: 3xxxxxk used and Swap: 6xxxxxk used before the third attempt
to suspend to disk.
The system that was running had at least one successful suspend to disk
and restore the day before and I also use it sucessfully on a daily
basis.
I believe I've seen the same crash before with a 2.6.27 or earlier
kernel, but I was in a hurry getting out of the door back then as I was
here. Circumstances was the same though, with already successful suspend
to disk and the crash appearing during second or third attempt to
suspend to disk in quick succession.
I guess I should be able to reproduce the crash with some efforts, but
I'd like to hear your thoughts on this before I do that.
Filesystems are reiserfs.
Simon Holm Thøgersen
next reply other threads:[~2008-11-20 12:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 12:41 Simon Holm Thøgersen [this message]
2008-11-20 16:50 ` 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=1227184916.4855.31.camel@odie.local \
--to=account@cs.aau.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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®