From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 90873] Kernel hang, TearFree On, Mate desktop environment Date: Thu, 18 Jun 2015 19:37:01 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1688565323==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 925326E2A0 for ; Thu, 18 Jun 2015 12:37:01 -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 --===============1688565323== Content-Type: multipart/alternative; boundary="1434656221.7A0d5Ac0.11658"; charset="UTF-8" --1434656221.7A0d5Ac0.11658 Date: Thu, 18 Jun 2015 19:37:01 +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=3D90873 --- Comment #6 from Tom --- (In reply to Michel D=C3=A4nzer from comment #5) > http://lists.freedesktop.org/archives/dri-devel/2015-June/084514.html fix= es > the hang for me (not a GPU hang but a kernel hang, because it tries to lo= ck > a mutex that's already locked). >=20 >=20 > > [ 141.232226] radeon 0000:01:00.0: bo ffff8804236d3400 va 0x0000001000 > > conflict with (bo ffff88042a018800 0x0000001000 0x0000001563) >=20 > These still happen, but at least with GNOME it continues working for me > somehow. I tried various workarounds for this in the Xorg driver, but I > haven't found anything that avoids these. I think the proper solution for > these would be for the kernel driver to track GPU VA ranges per GEM handle > instead of per BO. The latest patch applied to linux kernel rc8 fixed this issue, thanks. --=20 You are receiving this mail because: You are the assignee for the bug. --1434656221.7A0d5Ac0.11658 Date: Thu, 18 Jun 2015 19:37:01 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Comment= # 6 on bug 90873<= /a> from Tom 
(In reply to Michel D=C3=A4nzer from comment #5)
> http://lists.freedesktop.org/archives/dri=
-devel/2015-June/084514.html fixes
> the hang for me (not a GPU hang but a kernel hang, because it tries to=
 lock
> a mutex that's already locked).
>=20
>=20
> > [  141.232226] radeon 0000:01:00.0: bo ffff8804236d3400 va 0x0000=
001000
> > conflict with (bo ffff88042a018800 0x0000001000 0x0000001563)
>=20
> These still happen, but at least with GNOME it continues working for me
> somehow. I tried various workarounds for this in the Xorg driver, but I
> haven't found anything that avoids these. I think the proper solution =
for
> these would be for the kernel driver to track GPU VA ranges per GEM ha=
ndle
> instead of per BO.

The latest patch applied to linux kernel rc8 fixed this issue, thanks.

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