All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bojan Smojver <bojan@rexursive.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: Memory corruption on hibernate/thaw with KMS
Date: Mon, 10 Oct 2011 19:01:40 +1100	[thread overview]
Message-ID: <1318233700.2010.7.camel@shrek.rexursive.com> (raw)
In-Reply-To: 1317103928.1981.5.camel@shrek.rexursive.com

On Mon, 2011-10-10 at 18:15 +1100, Bojan Smojver wrote:
> Will try some more tests, just to confirm whether memory corruption
> thing is still present.

Yes, still present. I did this on my Fedora 15 system with 3.1.0-rc9+
(git pull as of half an hour ago):

echo -n reboot > /sys/power/disk
for (( i=0; i<15; i++)); do pm-hibernate; sleep 2; done

With nomodeset passed into to the kernel, the cycle finished
successfully. There was one program that segfaulted (modem-manager) in
one of the cycles only. I'm guessing this is probably a bug in the
program.

Without nomodeset (i.e. KMS), I got corruption and "unable to handle
paging request", followed by kernel hang on second thaw. It's pretty
much what happens when corruption occurs.

PS. Kernel 3.1.0-rc9+ was patched with my own hibernation patch that
calculates CRC32 of image pages on hibernate/thaw, so the chances that
what was read in was not what was hibernated were minimal. You can find
it here: http://marc.info/?l=linux-kernel&m=131820444524522&w=2. I'm
experiencing the same with Fedora supplied kernels (i.e.
2.6.40.6-0.fc15.x86_64, which is really 3.0.6).

-- 
Bojan

  parent reply	other threads:[~2011-10-10  8:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27  6:12 Memory corruption on hibernate/thaw with KMS Bojan Smojver
2011-09-29 23:38 ` Bojan Smojver
2011-10-03  6:44 ` Bojan Smojver
2011-10-04  2:32   ` Eugeni Dodonov
2011-10-04  2:46     ` Bojan Smojver
2011-10-04  3:21       ` Bojan Smojver
2011-10-10  7:15 ` Bojan Smojver
2011-10-10  7:53   ` Daniel Vetter
2011-10-10  8:18     ` Bojan Smojver
2011-10-10 10:05       ` Bojan Smojver
2011-10-10 10:12         ` Bojan Smojver
2011-10-10 10:37           ` Bojan Smojver
2011-10-10 11:23             ` Bojan Smojver
2011-10-11  9:29               ` Daniel Vetter
2011-10-11  9:42                 ` Bojan Smojver
2011-10-11 11:02                   ` Bojan Smojver
2011-10-11 11:22                     ` Daniel Vetter
2011-10-11 11:31                       ` Daniel Vetter
2011-10-11 12:25                         ` Bojan Smojver
2011-10-12  1:38                         ` Bojan Smojver
2011-10-14  1:14                         ` Bojan Smojver
2011-10-14  1:29                         ` Bojan Smojver
2011-10-11 12:24                       ` Bojan Smojver
2011-10-11 15:51                         ` Eugeni Dodonov
2011-10-11 16:13                           ` Daniel Vetter
2011-10-12  3:09                       ` Bojan Smojver
2011-10-12 22:16                         ` Bojan Smojver
2011-10-26  3:44                         ` Bojan Smojver
2011-10-11  9:55                 ` Bojan Smojver
2011-10-11 10:39                   ` Daniel Vetter
2011-10-11 10:41                     ` Bojan Smojver
2011-10-10  8:01 ` Bojan Smojver [this message]
2011-10-14  1:02 ` Bojan Smojver
2011-10-14  1:39   ` Bojan Smojver
2011-10-14  2:01     ` Bojan Smojver

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=1318233700.2010.7.camel@shrek.rexursive.com \
    --to=bojan@rexursive.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.