All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99158] vdpau segfaults and gpu locks with kodi on R9285
Date: Thu, 22 Dec 2016 00:00:02 +0000	[thread overview]
Message-ID: <bug-99158-502-wpcfE7Ghxu@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99158-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 568 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99158

--- Comment #3 from Andy Furniss <adf.lists@gmail.com> ---
Couldn't get it to crash with valgrind.

Bisect not 100% sure as it seemed to get harder to provoke going back in time,
but it does seem to need temporal deint and I got -

first bad commit: [d0d5f7600c2e8ab8d0c153787185f7a534753edd]
Revert "st/vdpau: use linear layout for output surfaces

The revert reverts from current head, so I will test for a while like that.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1352 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-12-22  0:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20 11:22 [Bug 99158] vdpau segfaults and gpu locks with kodi on R9285 bugzilla-daemon
2016-12-20 11:23 ` bugzilla-daemon
2016-12-20 14:41 ` bugzilla-daemon
2016-12-22  0:00 ` bugzilla-daemon [this message]
2016-12-29 11:03 ` bugzilla-daemon
2017-01-04  9:02 ` bugzilla-daemon
2017-01-04 10:18 ` bugzilla-daemon
2017-01-04 10:49 ` bugzilla-daemon
2017-01-05  0:00 ` bugzilla-daemon
2017-01-05 10:51 ` bugzilla-daemon

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=bug-99158-502-wpcfE7Ghxu@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@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.