From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102831] Some flashbased videoplayers cause GPU lockups on radeon.
Date: Thu, 13 Aug 2015 18:27:17 +0000 [thread overview]
Message-ID: <bug-102831-2300-zSpxQoAjEP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-102831-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=102831
--- Comment #3 from Jon Arne Jørgensen <jonjon.arnearne@gmail.com> ---
When the lockup fails to crash the kernel, I end up with an unusable system
with this filling my dmesg buffer:
[...snip...]
[ 1196.506527] radeon 0000:02:00.0: ring 5 stalled for more than 232970msec
[ 1196.506535] radeon 0000:02:00.0: GPU lockup (current fence id
0x0000000000000006 last fence id 0x0000000000000007 on ring 5)
[ 1197.007312] radeon 0000:02:00.0: ring 5 stalled for more than 233471msec
[ 1197.007319] radeon 0000:02:00.0: GPU lockup (current fence id
0x0000000000000006 last fence id 0x0000000000000007 on ring 5)
[ 1197.508102] radeon 0000:02:00.0: ring 5 stalled for more than 233972msec
[ 1197.508110] radeon 0000:02:00.0: GPU lockup (current fence id
0x0000000000000006 last fence id 0x0000000000000007 on ring 5)
[ 1198.008887] radeon 0000:02:00.0: ring 5 stalled for more than 234473msec
[ 1198.008896] radeon 0000:02:00.0: GPU lockup (current fence id
0x0000000000000006 last fence id 0x0000000000000007 on ring 5)
[ 1198.509671] radeon 0000:02:00.0: ring 5 stalled for more than 234974msec
[ 1198.509679] radeon 0000:02:00.0: GPU lockup (current fence id
0x0000000000000006 last fence id 0x0000000000000007 on ring 5)
[ 1199.010474] radeon 0000:02:00.0: ring 5 stalled for more than 235475msec
[ 1199.010482] radeon 0000:02:00.0: GPU lockup (current fence id
0x0000000000000006 last fence id 0x0000000000000007 on ring 5)
[ 1199.511267] radeon 0000:02:00.0: ring 5 stalled for more than 235976msec
[ 1199.511274] radeon 0000:02:00.0: GPU lockup (current fence id
0x0000000000000006 last fence id 0x0000000000000007 on ring 5)
[...snip...]
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-08-13 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 18:16 [Bug 102831] New: Some flashbased videoplayers cause GPU lockups on radeon bugzilla-daemon
2015-08-13 18:19 ` [Bug 102831] " bugzilla-daemon
2015-08-13 18:20 ` bugzilla-daemon
2015-08-13 18:22 ` bugzilla-daemon
2015-08-13 18:27 ` bugzilla-daemon [this message]
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-102831-2300-zSpxQoAjEP@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.