From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bojan Smojver Subject: Re: Memory corruption on hibernate/thaw with KMS Date: Mon, 10 Oct 2011 19:01:40 +1100 Message-ID: <1318233700.2010.7.camel@shrek.rexursive.com> References: <1317103928.1981.5.camel@shrek.rexursive.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from beauty.rexursive.com (beauty.rexursive.com [150.101.121.179]) by gabe.freedesktop.org (Postfix) with ESMTP id B6B869E709 for ; Mon, 10 Oct 2011 01:01:41 -0700 (PDT) Received: from [10.1.120.20] (shrek.rexursive.com [10.1.120.20]) by beauty.rexursive.com (Postfix) with ESMTPSA id EC4F51A01BE for ; Mon, 10 Oct 2011 19:01:40 +1100 (EST) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org To: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org 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