From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 80419] XCOM: Enemy Unknown Causes lockup Date: Tue, 22 Dec 2015 06:29:27 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1296182784==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 2211B6E53D for ; Mon, 21 Dec 2015 22:29:27 -0800 (PST) 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 --===============1296182784== Content-Type: multipart/alternative; boundary="1450765767.7E3b2.4969"; charset="UTF-8" --1450765767.7E3b2.4969 Date: Tue, 22 Dec 2015 06:29:27 +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=3D80419 --- Comment #75 from Michel D=C3=A4nzer --- (In reply to Kamil P=C3=A1ral from comment #74) > There's this line: > (EE) 2: /lib64/libc.so.6 (__memcpy_avx_unaligned+0x1ab) [0x7fe7ee3ffafb] > which is the same function that I reported to be crashing in apitrace: > https://github.com/apitrace/apitrace/issues/407 >=20 > Is this just a coincidence, or these two bugs are related (or the very sa= me)? Presumably coincidence. The apitrace crashes are segmentation faults, i.e. probably due to overrunning some buffer[0]. The Xorg crash is a bus error, which is probably fallout of the GPU hang. That said, we could probably confirm either way if we could look at a gdb backtrace of the Xorg crash. [0] FWIW, replaying the apitrace with valgrind on llvmpipe, I'm also seeing invalid memory access, so it might be a bug in apitrace or some shared Gall= ium / Mesa code rather than in the radeonsi driver. --=20 You are receiving this mail because: You are the assignee for the bug. --1450765767.7E3b2.4969 Date: Tue, 22 Dec 2015 06:29:27 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 75 on bug 80419<= /a> from Michel D=C3=A4nzer 
(In reply to Kamil P=C3=A1ral from comment #74)
> There's this line:
> (EE) 2: /lib64/libc.so.6 (__memcpy_avx_unaligned+0x1ab) [0x7fe7ee3ffaf=
b]
> which is the same function that I reported to be crashing in apitrace:
> https://gi=
thub.com/apitrace/apitrace/issues/407
>=20
> Is this just a coincidence, or these two bugs are related (or the very=
 same)?

Presumably coincidence. The apitrace crashes are segmentation faults, i.e.
probably due to overrunning some buffer[0]. The Xorg crash is a bus error,
which is probably fallout of the GPU hang.

That said, we could probably confirm either way if we could look at a gdb
backtrace of the Xorg crash.

[0] FWIW, replaying the apitrace with valgrind on llvmpipe, I'm also seeing
invalid memory access, so it might be a bug in apitrace or some shared Gall=
ium
/ Mesa code rather than in the radeonsi driver.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1450765767.7E3b2.4969-- --===============1296182784== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1296182784==--