From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.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 [thread overview]
Message-ID: <bug-90537-502-3Ud54MQQbb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90537-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1840 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90537
--- Comment #21 from Mauro Rossi <issor.oruam@gmail.com> ---
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.
[-- Attachment #1.2: Type: text/html, Size: 2902 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-05-26 16:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 14:06 [Bug 90537] radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL) bugzilla-daemon
2015-05-20 14:26 ` bugzilla-daemon
2015-05-20 14:28 ` bugzilla-daemon
2015-05-21 2:12 ` bugzilla-daemon
2015-05-21 19:14 ` bugzilla-daemon
2015-05-21 19:19 ` bugzilla-daemon
2015-05-21 20:09 ` bugzilla-daemon
2015-05-22 8:53 ` bugzilla-daemon
2015-05-22 9:30 ` bugzilla-daemon
2015-05-22 11:49 ` bugzilla-daemon
2015-05-22 12:07 ` bugzilla-daemon
2015-05-22 12:16 ` bugzilla-daemon
2015-05-23 1:22 ` bugzilla-daemon
2015-05-24 14:25 ` bugzilla-daemon
2015-05-24 14:26 ` bugzilla-daemon
2015-05-24 14:29 ` bugzilla-daemon
2015-05-25 12:10 ` bugzilla-daemon
2015-05-25 16:32 ` bugzilla-daemon
2015-05-26 8:12 ` bugzilla-daemon
2015-05-26 9:06 ` bugzilla-daemon
2015-05-26 9:06 ` bugzilla-daemon
2015-05-26 9:30 ` bugzilla-daemon
2015-05-26 16:16 ` bugzilla-daemon [this message]
2015-05-26 18:09 ` bugzilla-daemon
2015-05-26 18:12 ` bugzilla-daemon
2015-05-27 10:00 ` bugzilla-daemon
2015-06-25 2:46 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-90537-502-3Ud54MQQbb@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).