From: Ben Widawsky <ben@bwidawsk.net>
To: 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: Fri, 3 Feb 2012 18:23:10 -0800 [thread overview]
Message-ID: <20120204022309.GA7236@snipes.kumite> (raw)
In-Reply-To: <1328131605-20174-1-git-send-email-daniel.vetter@ffwll.ch>
On Wed, Feb 01, 2012 at 10:26:45PM +0100, Daniel Vetter wrote:
> Chris Wilson and me have again stared at funny error states and it's
> been pretty clear from the start that something was seriously amiss.
> The seqnos last seen by the cpu were a few hundred behind those that
> the gpu could have possibly emitted last before it died ...
>
> Chris now tracked it down (hopefully, definit verdict's still out),
> but in hindsight we'd have found the bug by simply dumping the cpu
> side tracking of the ring head and tail registers.
>
> Fix this and prevent an identical time-waster in the future.
>
> 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.
next prev parent reply other threads:[~2012-02-04 2:23 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 [this message]
2012-02-04 10:45 ` Chris Wilson
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=20120204022309.GA7236@snipes.kumite \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox