From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Subject: Re: Partial success - Fixing resume from s2ram on S6010 Date: Mon, 9 Jun 2014 14:31:55 +0300 Message-ID: <20140609113155.GN27580@intel.com> 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> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by gabe.freedesktop.org (Postfix) with ESMTP id CEB896E534 for ; Mon, 9 Jun 2014 04:32:44 -0700 (PDT) Content-Disposition: inline In-Reply-To: <53959852.4000504@math.tu-berlin.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Thomas Richter Cc: intel-gfx@lists.freedesktop.org List-Id: intel-gfx@lists.freedesktop.org On Mon, Jun 09, 2014 at 01:19:46PM +0200, Thomas Richter wrote: > Am 09.06.2014 13:08, schrieb Ville Syrj=E4l=E4 > > No, we do restore the mode you were using before suspend. > > > > Are you still using vbetool? That would explain why things go bad since > > vbetool will clobber whatever i915 already did. > = > No, vbetool is out of the equation (see the script attached to the = > previous post). So now you're using acpi_sleep=3Ds3_bios, or nothing? > However, I dumped the 830MG register set > and the ns2501 DVO set before and after the suspend, and they are pretty = > different. As said, the 830 is configured > to use a 640x480 mode (instead of the 1024x786 mode) and the DVO is off. > = > Maybe the kernel tries to mode-detect the connected monitor, and this = > fails because the PLLs are not yet > configured correctly? Note that the ns2501 requires a correctly = > configured DVO to be able to respond on > the i2c bus. If so, mode-detection requires configuring the PLLs to = > *some* useful mode before attempting > to detect anything, otherwise the DVO just plays "dead". Boot with drm.debug=3D0xe grab the dmesg after the resume and let's see if there is something fishy happening. -- = Ville Syrj=E4l=E4 Intel OTC