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: Mon, 23 Mar 2015 21:55:59 +0000	[thread overview]
Message-ID: <bug-89734-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 89734
           Summary: GL_AMD_pinned_memory extension causing a kernel
                    hardlock
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: poub365-bugzilla@yahoo.com
        QA Contact: dri-devel@lists.freedesktop.org

Kubuntu 15.04, kernel 4.0rc3, amd hd7850 with recent (from ppa oibaf) open
source drivers. Dolphin emulator runs fine except that I have a complete freeze
when I exit. I have to reboot the computer (although it seems to be still
running as I can remotely log with ssh). I tried under kde,  then under icewm,
to see if it was the compositor's fault. No change. Windowed or fullscreen:
same freeze. I tried to stop Dolphin with the interface buttons: same freeze.

kubuntu 15.04, i7 4770k non overclocked, amd hd7850 on open source drivers.

dmesg log is here:
http://pastebin.ca/2962286

I reported the bug to the Dolphin team. Told me that "Basically it's AMD's
GL_AMD_pinned_memory extension causing a kernel hardlock." and that I have to
report here.

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

[-- Attachment #1.2: Type: text/html, Size: 2734 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

             reply	other threads:[~2015-03-23 21:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 21:55 bugzilla-daemon [this message]
2015-03-24  2:25 ` [Bug 89734] GL_AMD_pinned_memory extension causing a kernel hardlock 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
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@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.