From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110637] Any OpenCL application causes "*ERROR* ring gfx timeout" on Vega 64
Date: Sun, 26 May 2019 04:28:36 +0000 [thread overview]
Message-ID: <bug-110637-502-rBLgpSD9lF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110637-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 507 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110637
--- Comment #9 from Alexander Mezin <mezin.alexander@gmail.com> ---
Tried Mesa 19.1.0-rc3
Geekbench hangs, but there are no immediate errors in dmesg. It looks like gpu
is doing something based on 'sensors' output (~130 W power consumption, at idle
it is <20W). And power consumption doesn't go down even when I kill geekbench.
When I try to reboot, the system hangs.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1358 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 prev parent reply other threads:[~2019-05-26 4:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 22:30 [Bug 110637] Enabling OpenCL in Libreoffice kills Vega 64 bugzilla-daemon
2019-05-09 5:02 ` bugzilla-daemon
2019-05-09 5:03 ` [Bug 110637] Any OpenCL application causes "*ERROR* ring gfx timeout" on " bugzilla-daemon
2019-05-09 5:09 ` bugzilla-daemon
2019-05-09 5:29 ` bugzilla-daemon
2019-05-09 5:30 ` bugzilla-daemon
2019-05-09 6:37 ` bugzilla-daemon
2019-05-09 7:20 ` bugzilla-daemon
2019-05-09 16:42 ` bugzilla-daemon
2019-05-10 4:40 ` bugzilla-daemon
2019-05-10 5:23 ` bugzilla-daemon
2019-05-26 4:28 ` bugzilla-daemon [this message]
2019-07-29 22:20 ` bugzilla-daemon
2019-07-30 1:46 ` bugzilla-daemon
2019-09-25 18:49 ` 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-110637-502-rBLgpSD9lF@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