From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95308] [radeonsi] Hangs after some minutes on Team Fortress 2
Date: Fri, 06 May 2016 20:59:05 +0000 [thread overview]
Message-ID: <bug-95308-502-AaY1llTsz8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95308-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 548 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95308
--- Comment #1 from Matías Locatti <matias.locatti@gmail.com> ---
This is what I get:
radeon 0000:01:00.0: ring 0 stalled for more than 10386msec
radeon 0000:01:00.0: VCE init error (-22).
[drm:r600_ib_test [radeon]] *ERROR* radeon: fance wait failed (-35).
[drm:radeon_ib_ring_test [radeon]] *ERROR* radeon: failed testing IB on GFX
ring (-35).
radeon 0000:01:00.0: VCE init error (-22).
After that, the kernel hangs.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1330 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 parent reply other threads:[~2016-05-06 20:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-95308-502@http.bugs.freedesktop.org/>
2016-05-06 20:59 ` bugzilla-daemon [this message]
2016-05-16 14:52 ` [Bug 95308] [radeonsi] Hangs after some minutes on Team Fortress 2 bugzilla-daemon
2016-05-16 15:11 ` bugzilla-daemon
2016-05-18 13:18 ` bugzilla-daemon
2016-05-18 13:18 ` bugzilla-daemon
2016-05-18 13:19 ` bugzilla-daemon
2016-05-24 22:25 ` bugzilla-daemon
2016-05-25 5:04 ` bugzilla-daemon
2016-05-25 5:05 ` bugzilla-daemon
2016-05-25 5:32 ` bugzilla-daemon
2016-05-25 5:34 ` bugzilla-daemon
2016-08-15 18:14 ` bugzilla-daemon
2016-08-29 15:09 ` bugzilla-daemon
2018-04-03 4:08 ` 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-95308-502-AaY1llTsz8@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