From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@freedesktop.org
Subject: [Bug 89734] GL_AMD_pinned_memory extension causing a kernel hardlock
Date: Mon, 06 Apr 2015 13:54:19 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1519307350=="
Return-path:
Received: from culpepper.freedesktop.org (unknown [131.252.210.165])
by gabe.freedesktop.org (Postfix) with ESMTP id 3BE916E1CF
for ; Mon, 6 Apr 2015 06:54:19 -0700 (PDT)
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Errors-To: dri-devel-bounces@lists.freedesktop.org
Sender: "dri-devel"
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
--===============1519307350==
Content-Type: multipart/alternative; boundary="1428328459.d86a2DB0.9642"; charset="UTF-8"
--1428328459.d86a2DB0.9642
Date: Mon, 6 Apr 2015 13:54:18 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
https://bugs.freedesktop.org/show_bug.cgi?id=3D89734
--- Comment #16 from Christian K=C3=B6nig ---
(In reply to poub365-bugzilla from comment #15)
> Created attachment 114842 [details]
> dmesg with patch
>=20
> 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.
Mhm, could be an uninitialized variable or something like this. Not sure off
hand. But if it works fine now it's unlikely that this is a driver problem.
>=20
> So, I can now exit dolphin without freezing. I get this message on the
> console:
>=20
> 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() functio=
n.)
> terminate called without an active exception
> Abandon (core dumped)
>=20
> I attach my dmesg and xorg.log just in case.
That's a completely different issue, not even sure if it is a driver proble=
m at
all.
--=20
You are receiving this mail because:
You are the assignee for the bug.
--1428328459.d86a2DB0.9642
Date: Mon, 6 Apr 2015 13:54:19 +0000
MIME-Version: 1.0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Commen=
t # 16
on bug 89734<=
/a>
from Christian K=C3=B6nig
(In reply to poub365-bugzilla from comment #15)
> Created attachmen=
t 114842 [details]
> dmesg with patch
>=20
> 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.=
Mhm, could be an uninitialized variable or something like this. Not sure off
hand. But if it works fine now it's unlikely that this is a driver problem.
>=20
> So, I can now exit dolphin without freezing. I get this message on the
> console:
>=20
> 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() func=
tion.)
> terminate called without an active exception
> Abandon (core dumped)
>=20
> I attach my dmesg and xorg.log just in case.
That's a completely different issue, not even sure if it is a driver proble=
m at
all.
You are receiving this mail because:
=20=20=20=20=20=20
- You are the assignee for the bug.
--1428328459.d86a2DB0.9642--
--===============1519307350==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs
IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0
cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK
--===============1519307350==--