From: Dave Jones <davej@redhat.com>
To: richard -rw- weinberger <richard.weinberger@gmail.com>
Cc: linux-pm@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
esandeen@redhat.com
Subject: Re: Corrupted files after suspend to disk
Date: Thu, 16 Feb 2012 11:30:31 -0500 [thread overview]
Message-ID: <20120216163030.GA32651@redhat.com> (raw)
In-Reply-To: <CAFLxGvzzHDRma_Y_XEpOD+fY+vonbkoR1mvQp4Vb4c3M6fTsPA@mail.gmail.com>
On Thu, Feb 16, 2012 at 11:52:27AM +0100, richard -rw- weinberger wrote:
> >> >> Of course, please test the above separately. :-)
> >> >
> >> > Ok, I'll test this when I'm at home.
> >> >
> >> > BTW: dropping the caches helps, when some files seem corrupted.
> >> > Today /usr/bin/okular was broken.
> >> > After setting vm.drop_caches=1 it worked again.
> >>
> >> On Linux 2.6.38 I'm unable to reproduce the issue.
> >> Only 2.6.37 seems to be affected.
> >> So, I'm moving over to 2.6.38. :)
> >
> Bad news:
> I saw the issue on 3.x too but thought it's because my IdeaPad s10 is crap.
> Now with my shiny new Lenovo x121e I have the same issue! :-(
>
> OpenSUSE 12.1, kernel 3.2.7.
> After a few suspend2disk iterations random files are corrupted.
> But only cached files. A reboot solves the problem.
FWIW, we've been seeing a number of hard to diagnose failures
with suspend to disk for the last few releases in Fedora.
Eric Sandeen has been chasing https://bugzilla.redhat.com/show_bug.cgi?id=744275
for a while, but there's no smoking gun that really explains what's
getting into these states. Further complicating things, is that it
doesn't seem to be 100% reproducable.
Dave
next prev parent reply other threads:[~2012-02-16 16:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTinRC1hXvaXDVV5pOA4YyCdXwAjziZsDzm=LuHqK@mail.gmail.com>
2011-03-23 20:36 ` Corrupted files after suspend to disk Rafael J. Wysocki
[not found] ` <201103232136.19091.rjw@sisk.pl>
2011-03-23 21:49 ` richard -rw- weinberger
[not found] ` <AANLkTimSyPiaq14yNP-KPxPcUaCqd4xr1xVNhefdK722@mail.gmail.com>
2011-03-23 22:11 ` Rafael J. Wysocki
[not found] ` <201103232311.38889.rjw@sisk.pl>
2011-03-23 22:16 ` richard -rw- weinberger
[not found] ` <AANLkTinkLj6SUMn-9Dkqn-Dx_7SN2dF70LYb2pFu19+3@mail.gmail.com>
2011-03-23 22:22 ` Rafael J. Wysocki
[not found] ` <201103232322.52485.rjw@sisk.pl>
2011-03-23 22:30 ` richard -rw- weinberger
[not found] ` <AANLkTi=UMDZ+78bS-U=Kvp_PYnc_BNHH5EgJnm1nssHP@mail.gmail.com>
2011-03-23 23:00 ` Rafael J. Wysocki
[not found] ` <201103240000.26788.rjw@sisk.pl>
2011-03-24 10:16 ` richard -rw- weinberger
[not found] ` <AANLkTinewk=mJZifVxEJkCtKfNauOjHnLAqwbGn139C=@mail.gmail.com>
2011-03-24 19:37 ` richard -rw- weinberger
[not found] ` <AANLkTikui_HQ5JMcMJUqMr9WLyTRNzF-z4G7wAUNPOFy@mail.gmail.com>
2011-03-24 22:30 ` Rafael J. Wysocki
[not found] ` <201103242330.14416.rjw@sisk.pl>
2012-02-16 10:52 ` richard -rw- weinberger
2012-02-16 16:30 ` Dave Jones [this message]
2012-02-16 21:51 ` Rafael J. Wysocki
2012-02-16 22:26 ` 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-02-16 23:27 ` Eric Sandeen
2012-02-16 23:37 ` richard -rw- weinberger
2011-03-23 22:33 ` richard -rw- weinberger
2011-03-23 16:31 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=20120216163030.GA32651@redhat.com \
--to=davej@redhat.com \
--cc=esandeen@redhat.com \
--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