lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1227184916.4855.31.camel@odie.local>
Date:	Thu, 20 Nov 2008 13:41:56 +0100
From:	Simon Holm Thøgersen <account@...aau.dk>
To:	Pavel Machek <pavel@...e.cz>, "Rafael J. Wysocki" <rjw@...k.pl>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-pm@...ts.linux-foundation.org
Subject: Crash during suspend to disk

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ