dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104481] GPU lockup Polaris 11 - AMD RX 460 and RX 550 on amd64 and on ARMv7 platforms while playing video
Date: Wed, 03 Jan 2018 17:50:14 +0000	[thread overview]
Message-ID: <bug-104481-502-DfE0u0nn5v@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104481-502@http.bugs.freedesktop.org/>


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

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

--- Comment #4 from Luis Mendes <luis.p.mendes@gmail.com> ---
Created attachment 136532
  --> https://bugs.freedesktop.org/attachment.cgi?id=136532&action=edit
Kernel hung task backtrace from GPU hang caused by glretrace replay

This attachment contains the first print of the kernel backtrace with the hung
caused by GPU hang when replaying the apitrace of the armv7l playing the VP9
video with kodi.

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

[-- Attachment #1.2: Type: text/html, Size: 1651 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:[~2018-01-03 17:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03 17:04 [Bug 104481] GPU lockup Polaris 11 - AMD RX 460 and RX 550 on amd64 and on ARMv7 platforms while playing video bugzilla-daemon
2018-01-03 17:07 ` bugzilla-daemon
2018-01-03 17:08 ` bugzilla-daemon
2018-01-03 17:10 ` bugzilla-daemon
2018-01-03 17:11 ` bugzilla-daemon
2018-01-03 17:50 ` bugzilla-daemon [this message]
2018-01-03 18:09 ` bugzilla-daemon
2018-08-09 14:56 ` bugzilla-daemon
2018-08-09 15:40 ` bugzilla-daemon
2019-09-25 18:02 ` 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-104481-502-DfE0u0nn5v@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox