From mboxrd@z Thu Jan  1 00:00:00 1970
From: Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [Bug 51061] GPU Hang using VAAPI
Date: Wed, 20 Jun 2012 21:29:21 +0200
Message-ID: <20120620192921.GO7170@phenom.ffwll.local>
References: <021d01cd4d80$d9ddd940$8d998bc0$@wolke7.net>
	<035601cd4ead$e9a2ed10$bce8c730$@wolke7.net>
	<20120620073331.GA4835@phenom.ffwll.local>
	<042001cd4f0a$f26f7370$d74e5a50$@wolke7.net>
	<20120620180832.GM7170@phenom.ffwll.local>
	<043401cd4f19$d8466080$88d32180$@wolke7.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from mail-we0-f177.google.com (mail-we0-f177.google.com
	[74.125.82.177])
	by gabe.freedesktop.org (Postfix) with ESMTP id 979559E9C2
	for <intel-gfx@lists.freedesktop.org>;
	Wed, 20 Jun 2012 12:27:52 -0700 (PDT)
Received: by werc12 with SMTP id c12so6170478wer.36
	for <intel-gfx@lists.freedesktop.org>;
	Wed, 20 Jun 2012 12:27:51 -0700 (PDT)
Content-Disposition: inline
In-Reply-To: <043401cd4f19$d8466080$88d32180$@wolke7.net>
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>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Angela <angela.schmid@wolke7.net>
Cc: intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

On Wed, Jun 20, 2012 at 09:21:07PM +0200, Angela wrote:
> > > Updated xorg-edgers, updated kernel (>3.5-rc3), merged
> > > drm-intel-next-queued. "Fixed" the two conflicts, are they OK ?
> > >
> > > No console, X starts in Vesa Mode.
> > >
> > > Added the new kernel dmesg, my "fixed" conflict's and a good kernel
> > dmesg.
> > >
> > > What's next.
> > 
> > Looks like the kernel couldn't communicate with the chip at all, all reads
> just
> > fail. I've pushed out a for-angela branch to my kernel playground at
> > 
> > http://cgit.freedesktop.org/~danvet/drm
> > 
> > Which contains recent drm-intel-next-queued with rc3 merged. That one
> > boots at least correctly here. Although your merge resolution looks
> correct,
> > so I have no idea what exactly went wrong.
> > -Daniel
> > 
> 
> Used head kernel and merged for-angela. Console and X are fine now, for drm
> dmesg see below.
> 
> > contains recent drm-intel-next-queued with rc3 merged
> I could also have taken for-angela alone, does it matter ?
> 
> Still have the VAAPI problem and still cannot grab error_state
> 
> [   416.677] (WW) intel(0): flip queue failed: Input/output error
> 
> cat: /sys/kernel/debug/dri/0/i915_error_state: Cannot allocate memory
> 
> With ppa kernel I didn't had a console and the system hung (could not ssh),
> will you add the "couldn't communicate with the chip at all" patch to
> drm-intel-next-queued, so I could check the error_state once again with the
> generated ppa 3.4 kernel. Will we be more lucky ? When will it be ready to
> try ?

It should all work, but something is seriously broken for you. Could you
bisect where this started to blow up for you maybe?
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48