From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ben Widawsky <ben@bwidawsk.net>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: dump even more into the error_state
Date: Sat, 04 Feb 2012 10:45:50 +0000 [thread overview]
Message-ID: <c55c5d$1s9504@AZSMGA002.ch.intel.com> (raw)
In-Reply-To: <20120204022309.GA7236@snipes.kumite>
On Fri, 3 Feb 2012 18:23:10 -0800, Ben Widawsky <ben@bwidawsk.net> wrote:
> On Wed, Feb 01, 2012 at 10:26:45PM +0100, Daniel Vetter wrote:
> > Because the hangs always involved semaphores in one way or another,
> > we've tried to dump the mbox registers, but couldn't find any
> > inconsistencies. Still, dump them too.
>
> How about we only do this if semaphores are actually enabled? I think
> that will eliminate potential confusion.
I suggested that we add the module parameters to the error-state to
aide, though even that is not fool proof as they could change between
the driver doing an undefined op and it fouling up the GPU. Any sign of
conflicting information inside the error-state is meant to be thought
provoking. ;-)
The idea is to dump as much information as we can about the errors and
leave the complex art of interpretation up to userspace.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-02-04 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 21:26 [PATCH] drm/i915: dump even more into the error_state Daniel Vetter
2012-02-01 21:39 ` Chris Wilson
2012-02-02 0:23 ` Eugeni Dodonov
2012-02-09 14:52 ` Daniel Vetter
2012-02-04 2:23 ` Ben Widawsky
2012-02-04 10:45 ` Chris Wilson [this message]
2012-02-04 19:55 ` Ben Widawsky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='c55c5d$1s9504@AZSMGA002.ch.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.