From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107545] radeon - ring 0 stalled - GPU lockup - SI
Date: Fri, 10 Aug 2018 22:59:59 +0000 [thread overview]
Message-ID: <bug-107545-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1246 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107545
Bug ID: 107545
Summary: radeon - ring 0 stalled - GPU lockup - SI
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
Assignee: dri-devel@lists.freedesktop.org
Reporter: julien.isorce@gmail.com
* Steps to reproduce:
for i in {0..300}; do (glxgears &); done (note that 100 might be enough
instead of 300)
* Actual result:
ring 0 stalled, gpu locakup, reset and x11 stops and cannot restart. The only
way is to reboot.
* Expected result:
The fps goes very low the more there are glxgears instances and no gpu lockup,
like with intel gpu.
* Infos:
card W600
mesa 18.2,
kernel 4.15.0-15-generic,
LLVM 7.0.0
xorg 1.20.99.1
xf86-video-ati 18.0.1.
(same result with kernel 4.4.0-130, mesa 12.0.6, llvm 3.8.0, DRM 2.43.0)
I was playing with the apitrace here
https://bugs.freedesktop.org/show_bug.cgi?id=87278#c31 and decided to through
dozens of glxgears instances to see.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2734 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-08-10 22:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 22:59 bugzilla-daemon [this message]
2018-08-14 16:52 ` [Bug 107545] radeon - ring 0 stalled - GPU lockup - SI bugzilla-daemon
2018-08-20 17:24 ` bugzilla-daemon
2018-08-20 17:26 ` bugzilla-daemon
2018-08-20 17:27 ` bugzilla-daemon
2018-08-20 17:42 ` bugzilla-daemon
2018-08-23 23:03 ` bugzilla-daemon
2018-08-23 23:04 ` bugzilla-daemon
2018-08-23 23:06 ` bugzilla-daemon
2018-08-24 7:30 ` bugzilla-daemon
2018-08-24 9:06 ` bugzilla-daemon
2018-08-24 23:34 ` bugzilla-daemon
2018-08-27 10:38 ` bugzilla-daemon
2018-11-14 9:57 ` bugzilla-daemon
2018-11-14 9:59 ` bugzilla-daemon
2018-11-14 10:02 ` bugzilla-daemon
2018-11-14 10:07 ` bugzilla-daemon
2018-11-14 10:07 ` bugzilla-daemon
2018-11-14 10:09 ` bugzilla-daemon
2018-11-15 22:24 ` bugzilla-daemon
2019-11-19 9:34 ` 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-107545-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).