dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64867] Hangs on Cayman (HD6950) when watching flash/using vdpau
Date: Thu, 06 Jun 2013 19:42:42 +0000	[thread overview]
Message-ID: <bug-64867-502-9hK0exeMdz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64867-502@http.bugs.freedesktop.org/>


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

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

--- Comment #4 from Harald Judt <h.judt@gmx.at> ---
Hoping that it would be a workaround, I've applied the following patch from
another bug report:

diff --git a/drivers/gpu/drm/radeon/radeon_cs.c
b/drivers/gpu/drm/radeon/radeon_cs.c
index 5407459..959e7cf 100644
--- a/drivers/gpu/drm/radeon/radeon_cs.c
+++ b/drivers/gpu/drm/radeon/radeon_cs.c
@@ -477,6 +477,7 @@ static int radeon_cs_ib_vm_chunk(struct radeon_device
*rdev,
        if (r) {
                goto out;
        }
+    radeon_fence_wait(vm->fence, false);
        radeon_cs_sync_rings(parser);
        radeon_cs_sync_to(parser, vm->fence);
        radeon_cs_sync_to(parser, radeon_vm_grab_id(rdev, vm, parser->ring));


While the hang happened again while playing a flash video (I'll try if I can
reproduce it somehow), this time I was able to vt switch, and X was killed and
the following additional lines got appended to dmesg:

[30243.510949] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[30243.510951] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000005c90bd
last fence id 0x00000000005c90b8)
[30243.510952] radeon 0000:01:00.0: couldn't schedule ib
[30243.510973] radeon 0000:01:00.0: Trying to sync to a disabled ring!
[30243.511047] radeon 0000:01:00.0: couldn't schedule ib
[30243.511048] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[30243.511197] radeon 0000:01:00.0: couldn't schedule ib
[30243.511198] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[30243.512323] radeon 0000:01:00.0: couldn't schedule ib
[30243.512324] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[30243.512851] radeon 0000:01:00.0: couldn't schedule ib
[30243.512852] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[30254.004957] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[30254.004959] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000334
last fence id 0x0000000000000333)
[30254.004961] radeon 0000:01:00.0: couldn't schedule ib
[30254.005052] radeon 0000:01:00.0: couldn't schedule ib
[30254.005064] radeon 0000:01:00.0: couldn't schedule ib
[30254.005070] radeon 0000:01:00.0: couldn't schedule ib
[30254.005084] radeon 0000:01:00.0: couldn't schedule ib
[30254.005092] radeon 0000:01:00.0: couldn't schedule ib
[30254.005097] radeon 0000:01:00.0: Trying to sync to a disabled ring!
[...]
[30243.510949] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[30243.510951] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000005c90bd
last fence id 0x00000000005c90b8)
[30243.510952] radeon 0000:01:00.0: couldn't schedule ib
[30243.510973] radeon 0000:01:00.0: Trying to sync to a disabled ring!
[30243.511047] radeon 0000:01:00.0: couldn't schedule ib
[30243.511048] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[30243.511197] radeon 0000:01:00.0: couldn't schedule ib
[30243.511198] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[30243.512323] radeon 0000:01:00.0: couldn't schedule ib
[30243.512324] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[30243.512851] radeon 0000:01:00.0: couldn't schedule ib
[30243.512852] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[30254.004957] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[30254.004959] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000334
last fence id 0x0000000000000333)
[30254.004961] radeon 0000:01:00.0: couldn't schedule ib
[30254.005052] radeon 0000:01:00.0: couldn't schedule ib
[30254.005064] radeon 0000:01:00.0: couldn't schedule ib
[30254.005070] radeon 0000:01:00.0: couldn't schedule ib
[30254.005084] radeon 0000:01:00.0: couldn't schedule ib
[30254.005092] radeon 0000:01:00.0: couldn't schedule ib
[30254.005097] radeon 0000:01:00.0: Trying to sync to a disabled ring!
[30254.012901] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB !
[...] many similar repeated lines about IB [...]
[30264.498754] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[30264.498759] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000000090e5
last fence id 0x00000000000090e3)

Trying to restart X didn't work (X crashed), so I had to reboot the machine.
Not sure if this brings any relevations. Anything I could do to provide more
information next time when this happens?

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

[-- Attachment #1.2: Type: text/html, Size: 5232 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-06-06 19:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22 14:13 [Bug 64867] New: Hangs on Cayman (HD6950) when watching flash/using vdpau bugzilla-daemon
2013-05-22 14:26 ` [Bug 64867] " bugzilla-daemon
2013-06-03 23:33 ` bugzilla-daemon
2013-06-04  0:27 ` bugzilla-daemon
2013-06-06 19:42 ` bugzilla-daemon [this message]
2013-06-06 20:58 ` bugzilla-daemon
2013-06-06 21:11 ` bugzilla-daemon
2013-06-16 18:36 ` bugzilla-daemon
2013-06-16 18:39 ` bugzilla-daemon
2013-06-16 18:47 ` bugzilla-daemon
2013-09-14  2:42 ` bugzilla-daemon
2015-01-27 10:27 ` 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-64867-502-9hK0exeMdz@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).