From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89734] GL_AMD_pinned_memory extension causing a kernel hardlock
Date: Fri, 03 Apr 2015 05:39:17 +0000 [thread overview]
Message-ID: <bug-89734-502-2M6d1JS1zH@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89734-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1268 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=89734
--- Comment #15 from poub365-bugzilla@yahoo.com ---
Created attachment 114842
--> https://bugs.freedesktop.org/attachment.cgi?id=114842&action=edit
dmesg with patch
Very strange: I booted on the patch kernel today to get a Xlog. No flickering
on desktop neither on fullscreen game. I didn't upgrade any component since
last time. Dolphin is working fine from my quick test.
So, I can now exit dolphin without freezing. I get this message on the console:
The program 'dolphin-emu' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8835 error_code 3 request_code 38 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
terminate called without an active exception
Abandon (core dumped)
I attach my dmesg and xorg.log just in case.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2167 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-04-03 5:39 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
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 [this message]
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-2M6d1JS1zH@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