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 110413] GPU crash and failed reset leading to deadlock on Polaris 22 XL [Radeon RX Vega M GL]
Date: Thu, 01 Aug 2019 18:44:41 +0000	[thread overview]
Message-ID: <bug-110413-502-WTnv8ZoUAn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110413-502@http.bugs.freedesktop.org/>


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

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

Utku Helvacı (tuxutku) <proje.pdf@outlook.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |proje.pdf@outlook.com

--- Comment #11 from Utku Helvacı (tuxutku) <proje.pdf@outlook.com> ---
Created attachment 144926
  --> https://bugs.freedesktop.org/attachment.cgi?id=144926&action=edit
journalctl -b0 output on kernel 5.3.0-rc2 from ubuntu mainline repository, with
a system with rx 540 gpu

kernel 5.3.0-rc1 was just fine and was just fixed a long lasted regression on
rx 540 gpu, updating to 5.3.0-rc2 causes gpu to be disabled after launching a
single application with it, gpu works fine until application is closed, then
DRI_PRIME=1 doesn't work

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

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

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

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

  parent reply	other threads:[~2019-08-01 18:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 14:44 [Bug 110413] GPU crash and failed reset leading to deadlock on Polaris 22 XL [Radeon RX Vega M GL] bugzilla-daemon
2019-04-12 14:45 ` bugzilla-daemon
2019-04-12 14:47 ` bugzilla-daemon
2019-04-12 14:48 ` bugzilla-daemon
2019-04-12 14:52 ` bugzilla-daemon
2019-04-13 13:27 ` bugzilla-daemon
2019-04-13 13:29 ` bugzilla-daemon
2019-04-13 13:30 ` bugzilla-daemon
2019-04-13 13:32 ` bugzilla-daemon
2019-04-13 13:32 ` bugzilla-daemon
2019-07-28 15:41 ` bugzilla-daemon
2019-08-01 18:44 ` bugzilla-daemon [this message]
2019-08-07 18:56 ` bugzilla-daemon
2019-11-19  9:19 ` 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-110413-502-WTnv8ZoUAn@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