From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Jiri Kosina <jkosina@suse.cz>
Cc: richard -rw- weinberger <richard.weinberger@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org
Subject: Re: Corrupted files after suspend to disk
Date: Mon, 12 Mar 2012 14:24:00 +0100 [thread overview]
Message-ID: <4F5DF8F0.5010801@01019freenet.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1203121402460.18356@pobox.suse.cz>
Jiri Kosina schrieb:
> On Mon, 12 Mar 2012, richard -rw- weinberger wrote:
>
>>>>> This is happening to me as well. Something like 1 resume out of 5 goes
>>>>> wrong this very same way.
>>>>>
>>>>> This is thinkpad x200s.
>>>>>
>>>>> All the userspace is segfaulting all over the place (most frequently in
>>>>> libselinux for some reason).
>>>>>
>>>>> I am not able to verify the 'drop_caches' theory, as I can't invoke a
>>>>> single command that wouldn't crash.
>>>>
>>>> The question is how should we proceed?
>>>> I've reported this issue one year (!!!) ago.
>>>
>>> Hmm, 3.3-rcX seems to be the first version when it started to happen to
>>> me. I take it that you have seen this also with 3.2? 3.1?
>>
>> Quote from my very first email:
>> "I'm facing a very strange problem on my netbook (Lenovo Ideapad S10)
>> running Linux 2.6.37.4."
>
> So we both seem to have Lenovos at least. I thus wanted to verify whether
> the problem will trigger with thinkpad_acpi removed, but it oopsed while
> rmmoding :) I will start looking into this right away.
>
> Is your system using thinkpad_acpi as well?
I dont't think, that it is lenovo related as I'm having a MSI machine.
https://bugzilla.novell.com/show_bug.cgi?id=732908
Following the link, you are able to compare the used chips - maybe there
are some equal components?
Regards,
Andreas
next prev parent reply other threads:[~2012-03-12 13:26 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
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 [this message]
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=4F5DF8F0.5010801@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.weinberger@gmail.com \
--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