linux-kernel - Re: [Bug #15004] i915: *ERROR* Execbuf while wedged

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100208093551.58a10643@jbarnes-piketon>
Date:	Mon, 8 Feb 2010 09:35:51 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Chris Mason <chris.mason@...cle.com>
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 Mon, 8 Feb 2010 12:24:10 -0500
Chris Mason <chris.mason@...cle.com> wrote:

> On Fri, Feb 05, 2010 at 11:17:47AM -0800, Jesse Barnes wrote:
> > On Fri, 5 Feb 2010 14:09:16 -0500
> > Chris Mason <chris.mason@...cle.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@...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.
> 
> Ok, updating to rc7 and updating my xf86 driver to 2.10 seems to have
> fixed up my suspend/resume problems.  So, I should be able to trigger
> the execbuf problem again.

I've heard some reports that the 2D driver introduces and fixes hangs,
so it's possible 2.10 will fix both issues for you.

> Well, the rebooting isn't a huge deal, but if there's something I can
> track/kick or force to core dump, would it help?

We do have a test in intel-gpu-tools that will instigate a hang, but it
would be best to figure out what's causing it in your environment.

-- 
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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/