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 71067] New: [drm:r600] UVD not responding OR failed testing IB on GFX ring
Date: Wed, 30 Oct 2013 22:54:13 +0000	[thread overview]
Message-ID: <bug-71067-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 71067
          Assignee: dri-devel@lists.freedesktop.org
           Summary: [drm:r600] UVD not responding OR failed testing IB on
                    GFX ring
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: timothee.romain.ravier@gmail.com
          Hardware: Other
            Status: NEW
           Version: XOrg CVS
         Component: DRM/Radeon
           Product: DRI

When I boot 3.10 or 3.11 kernels, I get either one of those errors, apparently
at random :
  * UVD not responding, trying to reset the VCPU
    -> Full log attached: *freeze-boot-then-yellow.log
    The display turns yellow when the X server starts. I can still use VT and
there is no corruption there. I made sure that I got the latest firmware and I
also checked my initrd (following instructions in 65270);

  * GPU lockup CP stall for more than 10000msec
    GPU lockup (waiting for 0x000000000000020e last fence id
0x00000000000001ec)
    r600_ib_test] *ERROR* radeon: fence wait failed (-35)
    radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35)
    -> Full log attached: *freeze-cursor.log
    I can log into my graphical session, but quickly after that, everything
freeze and I can only move the cursor which displays as a "corrupted" square.
    Again VT are fine.

I filed only one bug report as I get both issue using the same software and
boot command line.

At the beginning I had bug 67994, which turned into this one. I tried
downgrading the kernel without much success for now.

Booting with nomodeset works perfectly (with no accel/KMS obviously) and
booting under Windows 7 too.

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

[-- Attachment #1.2: Type: text/html, Size: 3282 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:[~2013-10-30 22:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30 22:54 bugzilla-daemon [this message]
2013-10-30 22:54 ` [Bug 71067] [drm:r600] UVD not responding OR failed testing IB on GFX ring bugzilla-daemon
2013-10-30 22:55 ` bugzilla-daemon
2013-10-30 22:55 ` bugzilla-daemon
2013-10-30 22:56 ` bugzilla-daemon
2013-10-31 13:02 ` bugzilla-daemon
2013-10-31 13:24 ` bugzilla-daemon
2013-11-03 21:58 ` bugzilla-daemon
2013-11-04 15:07 ` bugzilla-daemon
2013-11-04 15:15 ` bugzilla-daemon
2013-11-14 10:53 ` bugzilla-daemon
2013-11-14 14:09 ` bugzilla-daemon
2019-11-19  8:39 ` 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-71067-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).