From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110813] Vega hung on Surviving Mars game
Date: Sun, 02 Jun 2019 11:35:45 +0000 [thread overview]
Message-ID: <bug-110813-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1057 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110813
Bug ID: 110813
Summary: Vega hung on Surviving Mars game
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: stalkerg@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 144414
--> https://bugs.freedesktop.org/attachment.cgi?id=144414&action=edit
kernel log
It happens every time after +-20 min of the gaming. (I have already many items
on the map)
it's happened last few months after update to kernel 5.0.
Kernel - 5.1.6-gentoo
GPU - Vega56
from glxinfo:
Radeon RX Vega (VEGA10, DRM 3.30.0, 5.1.6-gentoo, LLVM 9.0.0)
Mesa 19.2.0-devel (git-47a10edefb)
Call trace and error log in attachment.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2526 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
next reply other threads:[~2019-06-02 11:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 11:35 bugzilla-daemon [this message]
2019-06-03 10:12 ` [Bug 110813] Vega hang on Surviving Mars game bugzilla-daemon
2019-06-10 12:20 ` bugzilla-daemon
2019-06-10 12:31 ` bugzilla-daemon
2019-07-18 3:30 ` bugzilla-daemon
2019-07-28 3:07 ` bugzilla-daemon
2019-09-25 18:50 ` 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-110813-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 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.