dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76501] fences regression
Date: Tue, 25 Mar 2014 10:52:27 +0000	[thread overview]
Message-ID: <bug-76501-502-a3JCSGwl4I@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-76501-502@http.bugs.freedesktop.org/>


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

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

--- Comment #9 from Christian König <deathsimple@vodafone.de> ---
(In reply to comment #6)
> interestingly also the last good commit produces the following log:
> [    7.573975] [drm] UVD initialized successfully.
> [    7.574210] [drm] Enabling audio 0 support
> [    7.574240] [drm] ib test on ring 0 succeeded in 0 usecs
> [    7.574263] [drm] ib test on ring 3 succeeded in 0 usecs
> [   17.730386] radeon 0000:01:00.0: GPU lockup CP stall for more than
> 10000msec
> [   17.730390] radeon 0000:01:00.0: GPU lockup (waiting for
> 0x0000000000000002 last fence id 0x0000000000000000)
> [   17.730393] [drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed
> (-35).
> [   17.730397] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB
> on ring 5 (-35).
> 
> 
> So that seems unrelated to the issue at hand.

Actually it is related, and now the behaviours makes perfect sense.

Somewhere between 3.12 and your "last good" commit we have a patch that breaks
UVD IB testing. But that isn't critical (3D still works fine) until the reset
detection rework, cause after that one we try to get the UVD ring working again
with each new IOCTL made to the card.

Please give the attached patch a try, it clears the "needs_reset" flag if the
IB test failed for some reason. So that if the initial bringup fails we won't
try to get it working over and over again.

Additional to that please bisect what commit breaks UVD IB testing between 3.12
and the "last good" commit and open up a new bug report for this issue.

Thanks for the help,
Christian.

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

[-- Attachment #1.2: Type: text/html, Size: 2604 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:[~2014-03-25 10:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-23  9:47 [Bug 76501] New: fences regression bugzilla-daemon
2014-03-23  9:47 ` [Bug 76501] " 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 [this message]
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-a3JCSGwl4I@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