From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 90537] radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL) Date: Tue, 26 May 2015 16:16:36 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0311259419==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 5DCB96E124 for ; Tue, 26 May 2015 09:16:36 -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 --===============0311259419== Content-Type: multipart/alternative; boundary="1432656996.ccbf30.32641"; charset="UTF-8" --1432656996.ccbf30.32641 Date: Tue, 26 May 2015 16:16:36 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=90537 --- Comment #21 from Mauro Rossi --- Created attachment 116054 --> https://bugs.freedesktop.org/attachment.cgi?id=116054&action=edit dmesg (without drm.debug=7) and logcat for HD7950 Hi, here is dmesg, without drm.debug=7, and logcat collected on HD7750 with VA BO proposed patch applied. VA conflict is still happening. <3>[ 807.802668] radeon 0000:01:00.0: bo f085f400 va 0x0000001138 conflict with (bo f183c400 0x000000121c 0x000000121d) [behavior without RADEON_VA_UNMAP patch, i.e. initial status] Without the VO BO patch applied, GUI was stable on HD7750 and HD7950 and many OpenGLES apps were fine (Gears, Rajawali, Harism Effects, Harism Shaderize, and Antutu benchmark could not be launched, failure in allocating bo for 'atlas' (NOTE: idk what 'atlas' is). OpenGLES 1.0 Demo com.rtsw.opengldemo cannot reach the second cube demo (app crashing and GUI restarting). [behavior with RADEON_VA_UNMAP patch] Logcat logs are showing "GPU lockups" that cannot be recovered until reboot, we also see intermittent GUI instability and GUI sometimes is not starting. Antutu can start and pass the 'atlas' bo allocation, but cannot complete 3D tests. OpenGLES 1.0 Demo com.rtsw.opengldemo cannot reach the second cube demo (app crashing and GUI restarting). It's strange that OpenGLES 1.0 Demo is not workinh either ways. Question (please be patient I'm not skilled as you are): could some of these problem due to multicore, hyperthreading or be cacheing related? If it can help, I can provide further logs with kernel parameters maxcpus=1, maxcpus=0 or by disabling hyperthreding in the BIOS. If problems were cacheing related, is there a way to highlight this? Mauro Rossi -- You are receiving this mail because: You are the assignee for the bug. --1432656996.ccbf30.32641 Date: Tue, 26 May 2015 16:16:36 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 21 on bug 90537 from 
Created attachment 116054 [details]
dmesg (without drm.debug=7) and logcat for HD7950

Hi, 

here is dmesg, without drm.debug=7, and logcat collected on HD7750 with VA BO
proposed patch applied.

VA conflict is still happening.

<3>[  807.802668] radeon 0000:01:00.0: bo f085f400 va 0x0000001138 conflict
with (bo f183c400 0x000000121c 0x000000121d)

[behavior without RADEON_VA_UNMAP patch, i.e. initial status]

Without the VO BO patch applied, GUI was stable on HD7750 and HD7950 and many
OpenGLES apps were fine (Gears, Rajawali, Harism Effects, Harism Shaderize, and
Antutu benchmark could not be launched, failure in allocating bo for 'atlas'
(NOTE: idk what 'atlas' is).
OpenGLES 1.0 Demo com.rtsw.opengldemo cannot reach the second cube demo (app
crashing and GUI restarting).

[behavior with RADEON_VA_UNMAP patch]
Logcat logs are showing "GPU lockups" that cannot be recovered until reboot, we
also see intermittent GUI instability and GUI sometimes is not starting.
Antutu can start and pass the 'atlas' bo allocation, but cannot complete 3D
tests.
OpenGLES 1.0 Demo com.rtsw.opengldemo cannot reach the second cube demo (app
crashing and GUI restarting).

It's strange that OpenGLES 1.0 Demo is not workinh either ways.

Question (please be patient I'm not skilled as you are): could some of these
problem due to multicore, hyperthreading or be cacheing related?

If it can help, I can provide further logs with kernel parameters maxcpus=1,
maxcpus=0 or by disabling hyperthreding in the BIOS.

If problems were cacheing related, is there a way to highlight this?

Mauro Rossi

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