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: Wed, 23 Mar 2011 21:36:18 +0100 [thread overview]
Message-ID: <201103232136.19091.rjw@sisk.pl> (raw)
In-Reply-To: <AANLkTinRC1hXvaXDVV5pOA4YyCdXwAjziZsDzm=LuHqK@mail.gmail.com>
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.
Thanks,
Rafael
next prev parent reply other threads:[~2011-03-23 20:36 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 16:31 Corrupted files after suspend to disk richard -rw- weinberger
2011-03-23 20:36 ` Rafael J. Wysocki [this message]
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
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=201103232136.19091.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;
as well as URLs for NNTP newsgroup(s).