From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106921] System lockup with Vega10 amdgpu: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout
Date: Thu, 14 Jun 2018 16:47:11 +0000 [thread overview]
Message-ID: <bug-106921-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1932 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106921
Bug ID: 106921
Summary: System lockup with Vega10 amdgpu:
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx
timeout
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: sam.psylo@gmail.com
Created attachment 140164
--> https://bugs.freedesktop.org/attachment.cgi?id=140164&action=edit
dmesg w/mesa 18.0.2-1.fc28
Using Vega10 hardware (in my case, RX Vega 64), the whole system experiences
regular full lockups, requiring me to force reboot either with the power switch
on the PC or using SysRq. The system is still running, since I am able to ssh
in from a separate machine and retrieve logs/run commands/etc, but all keyboard
and mouse input ceases.
I've had this occur when doing a multitude of things, some of which are as
follows:
- Playing games through Steam (Half-Life 2, Portal 2, Terraria tested)
- Playing non-Steam games (SuperTuxKart, GNOME Mines)
- Idle GNOME 3 desktop (no applications running)
- Browsing the web with Firefox 60.0.1
I have had this occur with:
Kernel: 4.16.14-300.fc28.x86_64 (from Fedora repos), 4.17.0 & 4.18.0-git5.1
(from kernel-vanilla repositories linked on Fedora wiki)
Mesa: 18.0.2-1.fc28 (from Fedora repos), 18.2.0-0.11.git41dabdc.fc28 (from
che/mesa copr repo)
linux-firmware: 20180525-85.git7518922b.fc28 (from Fedora repos), with
amdgpu/vega10_vce.bin replaced with newest version from git master.
OS: Fedora 28 Workstation
I am attaching a few dmesgs, each of which going from boot to the bug
occurring.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3379 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:[~2018-06-14 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 16:47 bugzilla-daemon [this message]
2018-06-14 16:47 ` [Bug 106921] System lockup with Vega10 amdgpu: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout bugzilla-daemon
2018-06-14 16:48 ` bugzilla-daemon
2018-09-01 14:40 ` bugzilla-daemon
2018-09-16 21:29 ` bugzilla-daemon
2018-09-18 2:10 ` bugzilla-daemon
2019-11-19 8:40 ` 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-106921-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;
as well as URLs for NNTP newsgroup(s).