[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100205190916.GD2858@think>
Date: Fri, 5 Feb 2010 14:09:16 -0500
From: Chris Mason <chris.mason@...cle.com>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Kernel Testers List <kernel-testers@...r.kernel.org>,
Chris Wilson <chris@...is-wilson.co.uk>,
tomas m <tmezzadra@...il.com>
Subject: Re: [Bug #15004] i915: *ERROR* Execbuf while wedged
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@...k.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@...il.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.
-chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists