From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Richter <thor@math.tu-berlin.de>
Subject: Re: Partial success - Fixing resume from s2ram on S6010
Date: Mon, 09 Jun 2014 14:57:39 +0200
Message-ID: <5395AF43.1090304@math.tu-berlin.de>
References: <5394EE4E.3040402@rus.uni-stuttgart.de>
 <1402296430-5065-1-git-send-email-chris@chris-wilson.co.uk>
 <20140609083025.GL27580@intel.com>
 <28223_1402303866_5395757A_28223_3428_1_20140609085045.GE16767@nuc-i3427.alporthouse.com>
 <5395932A.5080904@math.tu-berlin.de>
 <28223_1402312148_539595D3_28223_4884_1_20140609110857.GM27580@intel.com>
 <53959852.4000504@math.tu-berlin.de>
 <2086_1402313568_53959B5F_2086_895_1_20140609113155.GN27580@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Content-Transfer-Encoding: quoted-printable
Return-path: <intel-gfx-bounces@lists.freedesktop.org>
Received: from mail-2.alumni.tu-berlin.de (mail-2.alumni.tu-berlin.de
 [130.149.5.29])
 by gabe.freedesktop.org (Postfix) with ESMTP id 442E66E286
 for <intel-gfx@lists.freedesktop.org>; Mon,  9 Jun 2014 05:57:44 -0700 (PDT)
In-Reply-To: <2086_1402313568_53959B5F_2086_895_1_20140609113155.GN27580@intel.com>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
 <mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Errors-To: intel-gfx-bounces@lists.freedesktop.org
Sender: "Intel-gfx" <intel-gfx-bounces@lists.freedesktop.org>
To: =?ISO-8859-1?Q?Ville_Syrj=E4l=E4?= <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

Am 09.06.2014 13:31, schrieb Ville Syrj=E4l=E4:

>
> So now you're using acpi_sleep=3Ds3_bios, or nothing?

Ok, tried now with acpi_sleep=3Ds3. Unfortunately, this hangs the machine =

completely during resume, I cannot even ping it.

Then, I tried the same trick again, namely unloading the i915 module =

before the resume, reloading it after the resume. This worked =

flawlessly, display came back without requiring any quirks, even with =

the state the bios left the hardware in.

Note again that this is different for the resume from acpi_sleep=3Ds3 or =

'nothing', where I can restore the display (though the result is a hick-up).

If there is another deadlock in i915 (not unlikely) I cannot debug it =

this way, unfortunately.

Unfortunately, the S6010 does not have a serial port to redirect the =

console to. I can only use the netconsole, though this reveals nothing. =

Probably the deadlock happens before the is enabled.

Greetings,
	Thomas