From: "Rafael J. Wysocki" <rjw@suse.com>
Organization: SUSE Labs
To: Jiri Slaby <jirislaby@gmail.com>
Subject: Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
Date: Sun, 5 Dec 2010 14:08:27 +0100
User-Agent: KMail/1.13.5 (Linux/2.6.37-rc4+; KDE/4.4.4; x86_64; ; )
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
        "Linux-pm mailing list" <linux-pm@lists.linux-foundation.org>
References: <201012030107.oB317ZSW019223@imap1.linux-foundation.org> <4CFB4C66.1090106@gmail.com>
In-Reply-To: <4CFB4C66.1090106@gmail.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-2"
Content-Transfer-Encoding: 7bit
Message-Id: <201012051408.27730.rjw@suse.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1148
Lines: 31

On Sunday, December 05, 2010, Jiri Slaby wrote:
> On 12/03/2010 01:34 AM, akpm@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2010-12-02-16-34 has been uploaded to
> 
> Hi, this kernel regresses with respect to resume. It doesn't wake up,
> the screen is black with blinking cursor at position [1, 1].
> 2010-11-23-16-12 seemed to be OK. In this one it is 100% reproducible so
> far.
> 
> I'm using pm-suspend, any ideas what to test before I start to find the
> reason on my own?

Please try the pm_test tests for core, processors and devices, eg.:

# echo core > /sys/power/pm_test
# echo mem > /sys/power/state

(this is described in Documentation/power/basic-pm-debugging.txt .

That will tell you if you need to go through the BIOS for the bug to show up
and perhaps at what "level" the problem occurs.

It looks like the problem caused by NX-ing of the kernel code.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/