From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "richard -rw- weinberger" <richard.weinberger@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-pm@lists.linux-foundation.org
Subject: Re: Corrupted files after suspend to disk
Date: Thu, 24 Mar 2011 00:00:26 +0100 [thread overview]
Message-ID: <201103240000.26788.rjw@sisk.pl> (raw)
In-Reply-To: <AANLkTi=UMDZ+78bS-U=Kvp_PYnc_BNHH5EgJnm1nssHP@mail.gmail.com>
On Wednesday, March 23, 2011, richard -rw- weinberger wrote:
> On Wed, Mar 23, 2011 at 11:22 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Wednesday, March 23, 2011, richard -rw- weinberger wrote:
> >> On Wed, Mar 23, 2011 at 11:11 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> >> > On Wednesday, March 23, 2011, richard -rw- weinberger wrote:
> >> >> 2011/3/23 Rafael J. Wysocki <rjw@sisk.pl>:
> >> >> > On Wednesday, March 23, 2011, richard -rw- weinberger wrote:
> >> >> >> Hi,
> >> >> >>
> >> >> >> I'm facing a very strange problem on my netbook (Lenovo Ideapad S10)
> >> >> >> running Linux 2.6.37.4.
> >> >> >> After resuming from s2disk some files are corrupted.
> >> >> >> But when I reboot my netbook everything seems good again.
> >> >> >>
> >> >> >> When I saw the problem the first time the ls command segfaulted always.
> >> >> >> I did a reboot and it worked again.
> >> >> >>
> >> >> >> A few days later zypper crashed. After a reboot it worked again.
> >> >> >> And today ssh crashed. I looked a bit closer and saw it crashed
> >> >> >> somewhere within libcrypto.
> >> >> >> So I made copy libcrypto and rebooted.
> >> >> >> After the reboot ssh worked again but libcrypto and the copy of it hat
> >> >> >> a different sha1 sum!
> >> >> >> WTF?!
> >> >> >>
> >> >> >> Is this a known issue?
> >> >> >
> >> >> > No.
> >> >> >
> >> >> >> dmesgs and config are attached.
> >> >> >>
> >> >> >> The used distribution is openSUSE 11.4 with suspend-0.80.20100129-7.1
> >> >> >> (default from suse).
> >> >> >> I'm using ext3 as root filesystem.
> >> >> >> What else do you need?
> >> >> >
> >> >> > Whatever you can do to narrow down the problem. At the moment I only know
> >> >> > that it's there.
> >> >>
> >> >> I can reproduce the problem now.
> >> >> After ~20 suspend and resume iterations aide finds corrupted files in /lib/.
> >> >> It's always a very basic lib like libcrypto, libglib which is used all
> >> >> the time on my system.
> >> >
> >> > Those files are never intentionally modified, right?
> >> >
> >> >> Maybe it's an issue like this one?
> >> >> https://lkml.org/lkml/2010/12/2/339
> >> >
> >> > It might have if that patch hadn't been merged before 2.6.37.
> >> >
> >> > Is the system 32-bit or 64-bit?
> >>
> >> It's a 32-bit system.
> >> cmp shows that the corrupted files differ in many bytes (not scattered).
> >> The corrupted bytes are always 0 or 252.
> >
> > Do I understand correctly that the files apparently corrupted after resume
> > are not corrupted any more when you reboot?
>
> Yes.
> Seems like a cache issue.
There's a couple things you can check before we start asking other people for
help.
First, it would be good to know if things change when you save the image
into a swap file instead of the swap partition you've been using so far
(I believe it's documented quite well how to do that).
Second, please verify if using the built-in save/load hibernate code leads
to the same issue (you can hibernate by doing "echo disk > /sys/power/state"
to verify that).
Of course, please test the above separately. :-)
Thanks,
Rafael
next prev parent reply other threads:[~2011-03-23 23:00 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 16:31 richard -rw- weinberger
2011-03-23 20:36 ` Rafael J. Wysocki
2011-03-23 21:49 ` richard -rw- weinberger
2011-03-23 22:11 ` Rafael J. Wysocki
2011-03-23 22:16 ` richard -rw- weinberger
2011-03-23 22:22 ` Rafael J. Wysocki
2011-03-23 22:30 ` richard -rw- weinberger
2011-03-23 23:00 ` Rafael J. Wysocki [this message]
2011-03-24 10:16 ` richard -rw- weinberger
2011-03-24 19:37 ` richard -rw- weinberger
2011-03-24 22:30 ` Rafael J. Wysocki
2012-02-16 10:52 ` richard -rw- weinberger
2012-02-16 16:30 ` Dave Jones
2012-02-16 21:51 ` Rafael J. Wysocki
2012-02-16 22:26 ` [linux-pm] " Alan Stern
2012-02-16 23:07 ` richard -rw- weinberger
2012-02-16 23:16 ` Rafael J. Wysocki
2012-02-16 23:22 ` richard -rw- weinberger
2012-03-06 20:03 ` Andreas Hartmann
2012-03-06 23:54 ` Andreas Hartmann
2012-03-07 10:27 ` richard -rw- weinberger
2012-03-07 11:05 ` Andreas Hartmann
2012-03-12 12:03 ` Jiri Kosina
2012-03-12 12:23 ` richard -rw- weinberger
2012-03-12 12:30 ` Jiri Kosina
2012-03-12 12:58 ` richard -rw- weinberger
2012-03-12 13:03 ` Jiri Kosina
2012-03-12 13:24 ` Andreas Hartmann
2012-03-12 21:49 ` Dave Jones
2012-03-12 21:56 ` richard -rw- weinberger
2012-03-13 8:59 ` Andreas Hartmann
2012-03-13 21:52 ` Rafael J. Wysocki
2012-03-13 22:27 ` Andreas Hartmann
2012-03-14 0:06 ` Rafael J. Wysocki
2012-03-14 7:05 ` Andreas Hartmann
2012-03-16 15:19 ` richard -rw- weinberger
2012-03-28 22:12 ` Jiri Kosina
2012-03-28 22:18 ` Dave Jones
2012-03-28 22:49 ` Keith Packard
2012-03-29 15:23 ` Jiri Kosina
2012-03-31 20:21 ` Jiri Kosina
2012-03-12 21:38 ` richard -rw- weinberger
2012-03-12 13:36 ` Andreas Hartmann
2012-02-16 23:27 ` Eric Sandeen
2012-02-16 23:37 ` richard -rw- weinberger
2011-03-23 22:33 ` richard -rw- weinberger
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=201103240000.26788.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=richard.weinberger@gmail.com \
/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®