From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94081] [radeon 3.18 regression] GPU reset recovery fails
Date: Thu, 05 Mar 2015 01:12:11 +0000 [thread overview]
Message-ID: <bug-94081-2300-ahxlfHlfN2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-94081-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=94081
--- Comment #4 from Jan Vesely <jan.vesely@rutgers.edu> ---
This does not make sense, the work structure is zeroed so fence put should is
OK.
it looks like sometimes the lockup needs more than 1 GPU restart to manifest,
I'll replay without the good entries (at least it explains inconsistent bisect
results)
sorry for the noise
(In reply to Jan Vesely from comment #3)
> (In reply to Michel Dänzer from comment #2)
> > Can you bisect?
>
> It took a while (first bisect found unrelated i915 dispaly commit).
> the failure was introduced in:
>
> commit dd7cfd641228abb2669d8d047d5ec377b1835900
> Author: Maarten Lankhorst <maarten.lankhorst@canonical.com>
> Date: Tue Jan 21 13:07:31 2014 +0100
>
> drm/ttm: kill fence_lock
>
> No users are left, kill it off! :D
> Conversion to the reservation api is next on the list, after
> that the functionality can be restored with rcu.
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
>
> the commit moves a call to fence get below two "goto cleanup" in error
> paths, however, fence_put is left in the cleanup: error target. Moving the
> fence_put call to pflip_cleanup fixes the issue.
>
> I've posted a patch.
> >
> > (In reply to Jan Vesely from comment #1)
> > > here's dmesg output for 3.17 kernel:
> >
> > [...]
> >
> > > [ 249.362280] [drm:r600_ib_test] *ERROR* radeon: fence wait failed (-35).
> > > [ 249.362281] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB
> > > on GFX ring (-35).
> >
> > Actually, this looks like the reset didn't fully work with 3.17 either
> > though...
>
> I don't remember seeing this during bisection. This log is from fedora
> 3.17.8 kernel. I'll check 3.17.8 vanilla and see whether it's fedora specific
--
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-03-05 1:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-01 19:02 [Bug 94081] New: [radeon 3.18 regression] GPU reset recovery fails bugzilla-daemon
2015-03-01 19:05 ` [Bug 94081] " bugzilla-daemon
2015-03-02 6:58 ` bugzilla-daemon
2015-03-04 21:10 ` bugzilla-daemon
2015-03-05 1:12 ` 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-94081-2300-ahxlfHlfN2@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.