From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mattia Dongili <malattia@linux.it>
Subject: Re: gma500 suspend to ram fails (3.4)
Date: Thu, 21 Jun 2012 06:19:26 +0900
Message-ID: <20120620211925.GA12542@kamineko.org>
References: <CAMeQTsYfveOsPNyYEGb+AtjvwWWm0yX1DxuXEO5-SJM57Gw07w@mail.gmail.com>
	<20120618122629.54ad3c62@bob.linux.org.uk>
	<20120619105652.GA16280@kamineko.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org>
Received: from smtp.kamineko.org (ac250205.ppp.asahi-net.or.jp
	[183.77.250.205])
	by gabe.freedesktop.org (Postfix) with ESMTP id 6E54C9E748
	for <dri-devel@lists.freedesktop.org>;
	Wed, 20 Jun 2012 14:19:26 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <20120619105652.GA16280@kamineko.org>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/dri-devel>
List-Post: <mailto:dri-devel@lists.freedesktop.org>
List-Help: <mailto:dri-devel-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/dri-devel>,
	<mailto:dri-devel-request@lists.freedesktop.org?subject=subscribe>
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: Alan Cox <alan@linux.intel.com>, Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
Cc: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org

On Tue, Jun 19, 2012 at 07:56:52PM +0900, Mattia Dongili wrote:
> On Mon, Jun 18, 2012 at 10:04:00PM +0200, Patrik Jakobsson wrote:
> > On Sun, Jun 17, 2012 at 12:03 PM, Mattia Dongili <malattia@linux.it> wrote:
...
> > If possible, add drm.debug=7 to your boot line and send a dmesg of 3.5-rc3.
> 
> attached the dmesg on rc3 with drm.debug=7.
> In addition I have a black screen and 3 modprobe processes stuck that
> udev tried to kill for a bit... then the console went blank and I can't
> tell if it's still trying:
> 
>   359 ?        R     11:08 /sbin/modprobe -b pci:v00008086d00008108sv0000104Dsd0000905Fbc03sc00i00
>   361 ?        D      0:00 /sbin/modprobe -b pci:v00008086d0000811Bsv0000104Dsd0000905Fbc04sc03i00
>   422 ?        D      0:00 /sbin/modprobe -b pci:v00008086d00008119sv0000104Dsd0000905Fbc06sc01i00

for the record, here below is where the screen flickers a bit and
booting gets stuck until udev starts trying to kill the modprobe calls.

...
> [    5.547841] [drm:psb_intel_sdvo_debug_write], SDVOB: W: 1D                         (SDVO_CMD_GET_INPUT_PIXEL_CLOCK_RANGE)
> [    5.560512] [drm:psb_intel_sdvo_read_response], SDVOB: R: (Success) C4 09 74 40
> [    5.560520] [drm:psb_intel_sdvo_init], SDVOB device VID/DID: 02:42.02, clock range 25MHz - 165MHz, input 1: Y, input 2: N, output 1: Y, output 2: N
> [    5.660023] gma500 0000:00:02.0: Backlight lvds set brightness 74367436
> [  117.723197] Adding 4883756k swap on /dev/sda2.  Priority:-1 extents:1 across:4883756k SS
> [  117.911192] EXT3-fs (sda1): using internal journal

-- 
mattia
:wq!