From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89734] GL_AMD_pinned_memory extension causing a kernel hardlock
Date: Tue, 24 Mar 2015 14:56:52 +0000 [thread overview]
Message-ID: <bug-89734-502-mVHaOE7hot@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89734-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 531 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89734
--- Comment #3 from Christian König <deathsimple@vodafone.de> ---
Created attachment 114584
--> https://bugs.freedesktop.org/attachment.cgi?id=114584&action=edit
Debuging patch.
The only possible cause I can come up with is that we try to free the sg table
twice.
Please apply the attached debugging patch and report back with the resulting
dmesg.
Thanks in advance,
Christian.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1545 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
next prev parent reply other threads:[~2015-03-24 14:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 21:55 [Bug 89734] GL_AMD_pinned_memory extension causing a kernel hardlock bugzilla-daemon
2015-03-24 2:25 ` bugzilla-daemon
2015-03-24 9:04 ` bugzilla-daemon
2015-03-24 14:56 ` bugzilla-daemon [this message]
2015-03-25 6:34 ` bugzilla-daemon
2015-03-25 10:43 ` bugzilla-daemon
2015-03-27 21:17 ` bugzilla-daemon
2015-03-27 21:22 ` bugzilla-daemon
2015-03-30 10:12 ` bugzilla-daemon
2015-03-30 13:12 ` bugzilla-daemon
2015-03-31 1:52 ` bugzilla-daemon
2015-04-01 18:39 ` bugzilla-daemon
2015-04-01 18:42 ` bugzilla-daemon
2015-04-02 1:03 ` bugzilla-daemon
2015-04-03 5:36 ` bugzilla-daemon
2015-04-03 5:39 ` bugzilla-daemon
2015-04-06 13:54 ` bugzilla-daemon
2015-04-06 14:07 ` bugzilla-daemon
2015-04-08 9:44 ` 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-89734-502-mVHaOE7hot@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