From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68125] Radeon HD6950: Failed to parse relocation -35 (Linux 3.11-rc regression)
Date: Sat, 17 Aug 2013 21:13:48 +0000 [thread overview]
Message-ID: <bug-68125-502-wexUSd7hDS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68125-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 918 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=68125
Andreas Bombe <aeb@debian.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Andreas Bombe <aeb@debian.org> ---
While bisecting I noticed that CONFIG_DEBUG_WW_MUTEX_SLOWPATH was introduced
and that I had it enabled. Since that potentially introduces additional
-EDEADLK I suspected that check.
Turns out that check was buggy, the fix 85f489612 "mutex: Fix w/w mutex
deadlock injection" was merged since I posted this bug and the commit even
mentions explicitly that the bug caused spurious GPU lockups on radeon. The
problem appears to be gone with this fix.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2450 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
prev parent reply other threads:[~2013-08-17 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 23:07 [Bug 68125] New: Radeon HD6950: Failed to parse relocation -35 (Linux 3.11-rc regression) bugzilla-daemon
2013-08-14 23:09 ` [Bug 68125] " bugzilla-daemon
2013-08-14 23:10 ` bugzilla-daemon
2013-08-14 23:26 ` bugzilla-daemon
2013-08-17 21:13 ` 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-68125-502-wexUSd7hDS@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