From mboxrd@z Thu Jan  1 00:00:00 1970
From: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH] drm/i915: kicking rings considered harmful
Date: Tue, 27 Sep 2011 11:57:49 +0200
Message-ID: <CAKMK7uFvG+A8EDzf7Kk_PpDUSwhq7LfujJ5gSTSRgo_STmx9qg@mail.gmail.com>
References: <CAObL_7Hi+c2aEtEMzrMNnrQXfnUmNY_ZnP==xCd7egMoKBow_g@mail.gmail.com>
	<1317059990-1922-1-git-send-email-daniel.vetter@ffwll.ch>
	<CAObL_7FCinDjX43-aDJYC7dsC-jCx1k1e3y+T5q11=i=Vnc7UA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from mail-vx0-f177.google.com (mail-vx0-f177.google.com
	[209.85.220.177])
	by gabe.freedesktop.org (Postfix) with ESMTP id 213489EBDE
	for <intel-gfx@lists.freedesktop.org>;
	Tue, 27 Sep 2011 02:57:50 -0700 (PDT)
Received: by vcbfo1 with SMTP id fo1so4922463vcb.36
	for <intel-gfx@lists.freedesktop.org>;
	Tue, 27 Sep 2011 02:57:49 -0700 (PDT)
In-Reply-To: <CAObL_7FCinDjX43-aDJYC7dsC-jCx1k1e3y+T5q11=i=Vnc7UA@mail.gmail.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>
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: Andrew Lutomirski <luto@mit.edu>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>
List-Id: intel-gfx@lists.freedesktop.org

On Mon, Sep 26, 2011 at 21:07, Andrew Lutomirski <luto@mit.edu> wrote:
> On Sep 26, 2011 9:00 PM, "Daniel Vetter" <daniel.vetter@ffwll.ch> wrote:
>>
>> Only do it in the hope of resurrecting the gpu. Disable when reset is
>> disabled because it seems to tremendously increases our changes to
>> actually capture an error_state before the system goes all belly-up.
>>
>> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>> ---
>> Hi Andrew,
>>
>> Can you please apply this patch and boot your system with
>>
>
> Will do in a couple days.=A0 I'm several thousand miles from that computer
> right now :)

No problem. Something else to try: Are you by chance running with
DMAR/VT-d enabled? If so, please disable it (either in the BIOS or
with intel_iommu=3Doff) and see whether that works around the semaphore
hangs.

Perhaps do this before trying out the patch, doesn't require a new kernel ;=
-)

Thanks a lot, Daniel
-- =

Daniel Vetter
daniel.vetter@ffwll.ch - +41 (0) 79 365 57 48 - http://blog.ffwll.ch