All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89734] GL_AMD_pinned_memory extension causing a kernel hardlock
Date: Wed, 25 Mar 2015 10:43:29 +0000	[thread overview]
Message-ID: <bug-89734-502-iD667h75iv@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89734-502@http.bugs.freedesktop.org/>


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

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

--- Comment #5 from Christian König <deathsimple@vodafone.de> ---
(In reply to poub365-bugzilla from comment #4)
> Created attachment 114609 [details]
> first requested dmesg
> 
> Here's the first requested dmesg output.
> Applying the attached debugging patch is above my skills, unfortunately.
> Don't know if you can create a binary so that I can test (or give me a
> procedure on how to apply the patch).
> Sorry for too low technical skills guys.
> The dolphin version tested is 5921 (but same pb on older revisions). Freeze
> happens on the exit of Mario Kart and Donkey Kong Country Wii (I didn't test
> more as if seems independant of the game).

Unfortunately we usually don't have time to provide binary packages for every
small patch we make, sorry.

You could try following one of the tutorials on the net how to compile your own
kernel with kbuntu. If you managed to do so applying the patch on top of it is
trivial.

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

[-- Attachment #1.2: Type: text/html, Size: 2189 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:[~2015-03-25 10:43 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
2015-03-25  6:34 ` bugzilla-daemon
2015-03-25 10:43 ` bugzilla-daemon [this message]
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-iD667h75iv@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 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.