DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=virtuousgeek.org;
	h=Received:Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:X-Mailer:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User;
	b=BIO7OoQcPJIzixwxtQgDho4j5jdCj/wpTsqzzoULCq3dvh06V02dH70YbeYtL12m4wee0CzQWcoECyjeImcLtoCKTxejGhhOxA+SS/6rlt5U78JE4aZLbtN2em38oFN0;
Date: Fri, 5 Feb 2010 11:17:47 -0800
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Kernel Testers List <kernel-testers@vger.kernel.org>,
       Chris Wilson <chris@chris-wilson.co.uk>, tomas m <tmezzadra@gmail.com>
Subject: Re: [Bug #15004] i915: *ERROR* Execbuf while wedged
Message-ID: <20100205111747.6619b09b@jbarnes-piketon>
In-Reply-To: <20100205190916.GD2858@think>
References: <UgwvXSBS_tM.A.alD.1EiZLB@chimera>
	<de962C6zBxL.A.bvE.cFiZLB@chimera>
	<20100205110100.57852c31@jbarnes-piketon>
	<20100205190916.GD2858@think>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1793
Lines: 43

On Fri, 5 Feb 2010 14:09:16 -0500
Chris Mason <chris.mason@oracle.com> wrote:

> On Fri, Feb 05, 2010 at 11:01:00AM -0800, Jesse Barnes wrote:
> > On Mon,  1 Feb 2010 01:43:19 +0100 (CET)
> > "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > 
> > > This message has been generated automatically as a part of a
> > > report of regressions introduced between 2.6.31 and 2.6.32.
> > > 
> > > The following bug entry is on the current list of known
> > > regressions introduced between 2.6.31 and 2.6.32.  Please verify
> > > if it still should be listed and let me know (either way).
> > > 
> > > 
> > > Bug-Entry	:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=15004
> > > Subject		: i915: *ERROR* Execbuf while wedged
> > > Submitter	: tomas m <tmezzadra@gmail.com>
> > > Date		: 2010-01-07 18:53 (25 days old)
> > 
> > Can you bisect this to a particular kernel commit?  The particular
> > error message means the kernel detected a GPU hang.  That's usually
> > a userspace bug, but the kernel should recover from it.
> 
> I see these about once a week, which would be a very difficult bisect.
> The kernel does recover when I reboot, but beyond that the messages
> loop forever.
> 
> I haven't yet seen it on 2.6.33-rc, but I'm still struggling with
> suspend/resume failures and haven't really had a one week up time yet.

The fdo bug referenced from kernel bugzilla has a small workaround you
might try.  It forces the driver to try to recover from the hang, so
you might not need to reboot.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/