All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76501] New: fences regression
Date: Sun, 23 Mar 2014 09:47:02 +0000	[thread overview]
Message-ID: <bug-76501-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 76501
          Assignee: dri-devel@lists.freedesktop.org
           Summary: fences regression
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: odi@odi.ch
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

Created attachment 96233
  --> https://bugs.freedesktop.org/attachment.cgi?id=96233&action=edit
dmesg 3.12

I am seeing a GPU lockup from any v3.13 up to 3.14-rc7, which basically renders
my computer unusable under recent kernels :-(

[   55.762710] radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
[   55.762715] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000004
last fence id 0x000000000000000 on ring 5)
[   55.762717] [drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed (-35).
[   55.762720] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on
ring 5 (-35).

Hardware is an iMac 11,2 with a Radeon 4670 M96XT (RV730), 256MB GDDR3. 

working up to 3.12, broken as of 3.13.

Xorg comes up after some dalays with a mostly black screen, some colored
rectangular artifacts where the login fields are, a working mouse cursor.

Console fb still works.


Bisected to this commit:

commit f9eaf9ae782d6480f179850e27e6f4911ac10227
Author: Christian König <christian.koenig@amd.com>
Date:   Tue Oct 29 20:14:47 2013 +0100

    drm/radeon: rework and fix reset detection v2

    Stop fiddling with jiffies, always wait for RADEON_FENCE_JIFFIES_TIMEOUT.
    Consolidate the two wait sequence implementations into just one function.
    Activate all waiters and remember if the reset was already done instead of
    trying to reset from only one thread.

    v2: clear reset flag earlier to avoid timeout in IB test

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

[-- Attachment #1.2: Type: text/html, Size: 3570 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

             reply	other threads:[~2014-03-23  9:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23  9:47 bugzilla-daemon [this message]
2014-03-23  9:47 ` [Bug 76501] fences regression bugzilla-daemon
2014-03-23 10:04 ` bugzilla-daemon
2014-03-23 15:29 ` bugzilla-daemon
2014-03-24 20:43 ` bugzilla-daemon
2014-03-24 20:43 ` bugzilla-daemon
2014-03-24 20:55 ` bugzilla-daemon
2014-03-25 10:44 ` bugzilla-daemon
2014-03-25 10:49 ` bugzilla-daemon
2014-03-25 10:52 ` bugzilla-daemon
2014-03-25 19:42 ` bugzilla-daemon
2014-03-26 13:53 ` bugzilla-daemon
2014-03-26 14:10 ` bugzilla-daemon
2014-03-26 14:13 ` bugzilla-daemon
2014-04-03 16:31 ` 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-76501-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 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.