From: Chris Wilson <chris@chris-wilson.co.uk>
To: Antonio Argenziano <antonio.argenziano@intel.com>,
igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] lib: Show the kernel stack when reporting a GPU hang
Date: Fri, 04 May 2018 21:19:31 +0100 [thread overview]
Message-ID: <152546517183.11914.7737069890109259908@mail.alporthouse.com> (raw)
In-Reply-To: <769571aa-8bd3-d858-459b-b31030ad3853@intel.com>
Quoting Antonio Argenziano (2018-05-04 19:19:40)
>
>
> On 03/05/18 13:55, Chris Wilson wrote:
> > In a few tests (like gem_exec_await, gem_exec_schedule) we use the GPU
> > hang to break a deadlock hit during test setup. In these case we would
> > like to see where in kernel the process is stuck (if at all).
> >
> > References: https://bugs.freedesktop.org/show_bug.cgi?id=105900
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
>
> LGTM. Maybe with so much text adding a separator that is easy to find
> wouldn't be too bad.
It *should* be followed by the assert + stacktrace from the parent. One
hopes, not too bad for debugging. I'll let you know after looking at a
few reports...
-Chris
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2018-05-04 20:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 20:55 [igt-dev] [PATCH i-g-t] lib: Show the kernel stack when reporting a GPU hang Chris Wilson
2018-05-03 21:42 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-05-04 1:36 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-05-04 18:19 ` [igt-dev] [PATCH i-g-t] " Antonio Argenziano
2018-05-04 20:19 ` Chris Wilson [this message]
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=152546517183.11914.7737069890109259908@mail.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=antonio.argenziano@intel.com \
--cc=igt-dev@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.