From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99782] Driver lockup using dolphin in specific areas
Date: Sun, 12 Feb 2017 17:20:49 +0000 [thread overview]
Message-ID: <bug-99782-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1342 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=99782
Bug ID: 99782
Summary: Driver lockup using dolphin in specific areas
Product: Mesa
Version: git
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: radeon.20.mathieui@dfgh.net
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 129537
--> https://bugs.freedesktop.org/attachment.cgi?id=129537&action=edit
Dolphin FIFO log that triggers the lockup
Using my RX 470 card and mesa, my video driver locks up in specific parts of a
game (Fire Emblem: Radiant Dawn) using the Dolphin emulator.
I can still interact with the system using ssh, but the screen stays frozen at
the exact moment and stays unresponsive until reboot (trying to kill dolphin
leads to a zombie).
I tried with all stable mesa versions between 13.0 and 13.0.4, and a fairly
recent git version (3f064e9a40), and I can reproduce the lockup every time.
I attached a dolphin fifo log which triggers the bug and can be run without
owning the game.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2886 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
next reply other threads:[~2017-02-12 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 17:20 bugzilla-daemon [this message]
2018-07-02 22:48 ` [Bug 99782] Driver lockup using dolphin in specific areas bugzilla-daemon
2019-09-25 17:57 ` 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-99782-502@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