All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106666] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vmid:3 pas_id:0), [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=327845, last emitted seq=327847
Date: Thu, 14 Jun 2018 15:18:37 +0000	[thread overview]
Message-ID: <bug-106666-502-3KHOaq5BQD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106666-502@http.bugs.freedesktop.org/>


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

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

--- Comment #20 from sam.psylo@gmail.com ---
Created attachment 140158
  --> https://bugs.freedesktop.org/attachment.cgi?id=140158&action=edit
dmesg w/mesa 18.0.2-1.fc28

I am still suffering from this issue, even with latest firmware from comment
15.
Kernel: 4.16.14-300.fc28.x86_64
Mesa: tested both 18.0.2-1.fc28 (current Fedora release) and
18.2.0-0.11.git41dabdc.fc28 (from che/mesa copr repo). Bug occurred on both.
Firmware: 20180525-85.git7518922b.fc28 (current Fedora release), but with
vega10_vce.bin from comment 15 replacing the one installed by the package.

My graphics card is a PowerColor RX Vega 64.

I am attaching two dmesgs: one with each mentioned tested Mesa version.

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

[-- Attachment #1.2: Type: text/html, Size: 2124 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-06-14 15:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-26 11:30 [Bug 106666] amdgpu 0000:09:00.0: [gfxhub] VMC page fault (src_id:0 ring:56 vmid:3 pas_id:0), [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=327845, last emitted seq=327847 bugzilla-daemon
2018-05-26 11:40 ` bugzilla-daemon
2018-05-30 15:53 ` bugzilla-daemon
2018-05-30 15:55 ` bugzilla-daemon
2018-05-30 15:55 ` bugzilla-daemon
2018-06-02  3:56 ` bugzilla-daemon
2018-06-02  3:58 ` bugzilla-daemon
2018-06-02  3:58 ` bugzilla-daemon
2018-06-02  3:59 ` bugzilla-daemon
2018-06-03  2:40 ` bugzilla-daemon
2018-06-03  2:50 ` bugzilla-daemon
2018-06-03 20:58 ` bugzilla-daemon
2018-06-05 16:37 ` bugzilla-daemon
2018-06-06  2:25 ` bugzilla-daemon
2018-06-06  7:08 ` bugzilla-daemon
2018-06-06 13:05 ` bugzilla-daemon
2018-06-10 10:28 ` bugzilla-daemon
2018-06-10 14:31 ` bugzilla-daemon
2018-06-13 15:41 ` bugzilla-daemon
2018-06-14  8:10 ` bugzilla-daemon
2018-06-14 15:18 ` bugzilla-daemon [this message]
2018-06-14 15:19 ` bugzilla-daemon
2018-06-14 15:43 ` bugzilla-daemon
2018-06-14 16:28 ` 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-106666-502-3KHOaq5BQD@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.