DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=dV0RxLcLuP8AiGz9wezaeDzOcK+nq2c2mVJqY6g1KyrTLLy5WugkZ9m/slEWVNlfmT
         gsdIPzIQKsXsrExc3q1musG9x84ZesgPWOqHZUIBFDopHH8C3aQ/rjbRKUVozd5WSL5E
         MZ7fBHepgAlbhwLw503hTAycTOQ8++qoNmU4c=
Message-ID: <4D07EAE5.6050803@gmail.com>
Date: Tue, 14 Dec 2010 23:08:37 +0100
From: Jiri Slaby <jirislaby@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; cs-CZ; rv:1.9.2.13) Gecko/20101206 SUSE/3.1.7 Thunderbird/3.1.7
MIME-Version: 1.0
To: "Rafael J. Wysocki" <rjw@suse.com>
CC: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
        Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: Resume hangs [was: mmotm 2010-12-02-16-34 uploaded]
References: <201012030107.oB317ZSW019223@imap1.linux-foundation.org> <201012051408.27730.rjw@suse.com> <4D05EFB2.3050703@gmail.com> <201012132210.51325.rjw@suse.com>
In-Reply-To: <201012132210.51325.rjw@suse.com>
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1461
Lines: 35

On 12/13/2010 10:10 PM, Rafael J. Wysocki wrote:
> On Monday, December 13, 2010, Jiri Slaby wrote:
>> On 12/05/2010 02:08 PM, Rafael J. Wysocki wrote:
>>> 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.:
>>
>> Hmm, I haven't seen the issues since then. So it had to be some kind of
>> coincidence -- I see the issue occasionally for some time already. Now
>> it triggered twice in a row after I updated the kernel.
> 
> Hmm.  What hardware is that?

What exactly do you want to know about it? It's some specific intel
desktop machine, 3 years old, 2 intel cores, 6G of mem, 2 sata disks in
raid, dvb-t usb receiver (af9015), usb keyboard and mouse.

regards,
-- 
js
--
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/