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, 11 Jun 2015 09:51:53 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2046320868==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id D13B86E9DE for ; Thu, 11 Jun 2015 02:51:52 -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 --===============2046320868== Content-Type: multipart/alternative; boundary="1434016312.48B6Bd20.18021"; charset="UTF-8" --1434016312.48B6Bd20.18021 Date: Thu, 11 Jun 2015 09:51:52 +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 Michel D=C3=A4nzer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |deathsimple@vodafone.de Component|Drivers/Gallium/radeonsi |DRM/Radeon Version|git |unspecified Product|Mesa |DRI Summary|GPU hang, TearFree On, Mate |Kernel hang, TearFree On, |desktop environment |Mate desktop environment QA Contact|dri-devel@lists.freedesktop | |.org | --- Comment #5 from Michel D=C3=A4nzer --- 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 m= utex that's already locked). > [ 141.232226] radeon 0000:01:00.0: bo ffff8804236d3400 va 0x0000001000 > conflict with (bo ffff88042a018800 0x0000001000 0x0000001563) 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 hav= en't found anything that avoids these. I think the proper solution for these wou= ld be for the kernel driver to track GPU VA ranges per GEM handle instead of p= er BO. --=20 You are receiving this mail because: You are the assignee for the bug. --1434016312.48B6Bd20.18021 Date: Thu, 11 Jun 2015 09:51:52 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable = Michel D=C3=A4nzer changed bug 90873<= /a>
What Removed Added
CC   deathsimple@vodafone.de
Component Drivers/Gallium/radeonsi DRM/Radeon
Version git unspecified
Product Mesa DRI
Summary GPU hang, TearFree On, Mate desktop environment Kernel hang, TearFree On, Mate desktop environment
QA Contact dri-devel@lists.freedesktop.org  

Comment= # 5 on bug 90873<= /a> from Michel D=C3=A4nzer 
http://lists.freedesktop.org/archives/dri-devel/2015-Ju=
ne/084514.html fixes the
hang for me (not a GPU hang but a kernel hang, because it tries to lock a m=
utex
that's already locked).


> [  141.232226] radeon 0000:01:00.0: bo ffff88042=
36d3400 va 0x0000001000
> conflict with (bo ffff88042a018800 0x0000001000 0x0000001563)

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 hav=
en't
found anything that avoids these. I think the proper solution for these wou=
ld
be for the kernel driver to track GPU VA ranges per GEM handle instead of p=
er
BO.

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