Include extra information such as the user_handle and hw_id so that
userspace can identify which of their contexts hung, useful if they are
performing self-diagnositics.
Signed-off-by: Chris Wilson
Cc: Mika Kuoppala
---
drivers/gpu/drm/i915/i915_drv.h | 14 +--
drivers/gpu/drm/i915/i9
On Sun, Jan 29, 2017 at 10:33:07AM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 1/28/2017 1:47 PM, Imre Deak wrote:
> >On Sat, Jan 28, 2017 at 10:32:03AM +0530, Sharma, Shashank wrote:
> >>Regards
> >>
> >>Shashank
> >>
> >>
> >>On 1/27/2017 3:09 PM, Imre Deak wrote:
> >>>Durin
Guys, I've gotten absolutely no response to this, and the problem
seems to still occur.
I just got a slightly different hang at shutdown, due to a kernel oops
that seems related. It's not identical - the call trace is very
different - but it's close.
In particular, it's once again the same NULL p
Otherwise we won't log anything with OpenGL applications using a
recent Mesa driver.
Signed-off-by: Lionel Landwerlin
---
tools/aubdump.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/tools/aubdump.c b/tools/aubdump.c
index d53addc2..59ef3e7e 100644
--- a/tools/aubdump.c
Nothing should happen before than given that drm_fd will be set to -1.
Signed-off-by: Lionel Landwerlin
---
tools/aubdump.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/tools/aubdump.c b/tools/aubdump.c
index 6715a5d7..d53addc2 100644
--- a/tools/aubdump.c
+++ b/tools/au
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
drivers/gpu/drm/ttm/ttm_bo.c
between commit:
7c6d639d465e ("drm/ttm: Make sure BOs being swapped out are cacheable")
from the drm-misc-fixes tree and commit:
bdfafc4ffdd2 ("locking/atomic, kref: Kill kref_sub()")
from
Rami Ben Hassine schreef op do 26-01-2017 om 16:36 [+0100]:
> From: ramibh
>
> This is atomic modesetting acceptance tests added to
> feat_profile.json. Wating for your feedback.
>
> ---
> tests/feat_profile.json | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/t