From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97069] Radeon r600 glamor corruptions on ARM64
Date: Tue, 26 Jul 2016 14:27:32 +0000 [thread overview]
Message-ID: <bug-97069-502-5x6GKHfK7h@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97069-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 3348 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97069
--- Comment #12 from Clemens Eisserer <linuxhippy@gmail.com> ---
Thanks, with float textures it now correctly reports OpenGL-3.3
However more ugly things are going on.
When running the PBO texture upload benchmark at available at
http://www.songho.ca/opengl/gl_pbo.html, I get tons of the following messages:
radeon: Failed to allocate a buffer:
radeon: size : 4194304 bytes
radeon: alignment : 4096 bytes
radeon: domains : 2
radeon: flags : 4
radeon: Failed to allocate a buffer:
radeon: size : 4194304 bytes
radeon: alignment : 4096 bytes
radeon: domains : 2
radeon: flags : 4
EE r600_texture.c:1346 r600_texture_transfer_map - failed to create temporary
texture to hold untiled copy
later on, when I try to resize the benchmark window, Xorg segfaults:
Thread 1 "Xorg" received signal SIGSEGV, Segmentation fault.
0x0000ffffb6d59348 in evergreen_emit_constant_buffers (rctx=0xaaaaaad5cbe0,
state=0xaaaaaad5dba8, buffer_id_base=<optimized out>,
reg_alu_constbuf_size=<optimized out>, reg_alu_const_cache=<optimized out>,
pkt_flags=<optimized out>) at evergreen_state.c:1877
1877 va = rbuffer->gpu_address + cb->buffer_offset;
(gdb) bt
#0 0x0000ffffb6d59348 in evergreen_emit_constant_buffers (rctx=0xaaaaaad5cbe0,
state=0xaaaaaad5dba8, buffer_id_base=<optimized out>,
reg_alu_constbuf_size=<optimized out>, reg_alu_const_cache=<optimized out>,
pkt_flags=<optimized out>) at evergreen_state.c:1877
#1 0x0000ffffb6d86ab0 in r600_emit_atom (atom=0xaaaaaad5dba8,
rctx=0xaaaaaad5cbe0) at r600_pipe.h:549
#2 r600_draw_vbo (ctx=0xaaaaaad5cbe0, dinfo=<optimized out>) at
r600_state_common.c:1794
#3 0x0000ffffb6be30f0 in u_vbuf_draw_vbo (mgr=0xaaaaaadb1b60, info=<optimized
out>) at util/u_vbuf.c:1163
#4 0x0000ffffb6a4e104 in st_draw_vbo (ctx=0xffffb3647010, prims=<optimized
out>, nr_prims=1, ib=0x0, index_bounds_valid=<optimized out>, min_index=0,
max_index=0, tfb_vertcount=0x0, stream=0, indirect=0x0) at
state_tracker/st_draw.c:251
#5 0x0000ffffb6a17b04 in vbo_draw_arrays (ctx=0xffffb3647010, mode=5, start=0,
count=4, numInstances=1, baseInstance=0) at vbo/vbo_exec_array.c:503
#6 0x0000ffffb7290154 in glamor_poly_fill_rect_gl (prect=<optimized out>,
nrect=1, gc=0xaaaaab8415cc, drawable=0xaaaaab833fc0)
at ../../glamor/glamor_rects.c:128
#7 glamor_poly_fill_rect (drawable=0xaaaaab833fc0, gc=0xaaaaab8415cc, nrect=1,
prect=<optimized out>) at ../../glamor/glamor_rects.c:163
#8 0x0000aaaaaabeccdc in damagePolyFillRect (pDrawable=0xaaaaab833fc0,
pGC=0xaaaaab817ea0, nRects=1, pRects=<optimized out>)
at ../../../miext/damage/damage.c:1194
#9 0x0000aaaaaaafe180 in ProcPolyFillRectangle (client=0xaaaaaacd1dc0) at
../../dix/dispatch.c:1883
#10 0x0000aaaaaab01d4c in Dispatch () at ../../dix/dispatch.c:430
#11 0x0000aaaaaab05c20 in dix_main (argc=1, argv=0xfffffffffc58,
envp=<optimized out>) at ../../dix/main.c:300
#12 0x0000ffffb7a9c8a4 in __libc_start_main (main=0x0, argc=0, argv=0x0,
init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>,
stack_end=<optimized out>) at libc-start.c:291
#13 0x0000aaaaaaaefba8 in _start ()
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4305 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-07-26 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-97069-502@http.bugs.freedesktop.org/>
2016-07-26 1:03 ` [Bug 97069] Radeon r600 glamor corruptions on ARM64 bugzilla-daemon
2016-07-26 1:04 ` bugzilla-daemon
2016-07-26 2:31 ` bugzilla-daemon
2016-07-26 7:48 ` bugzilla-daemon
2016-07-26 11:03 ` bugzilla-daemon
2016-07-26 11:15 ` bugzilla-daemon
2016-07-26 11:18 ` bugzilla-daemon
2016-07-26 11:47 ` bugzilla-daemon
2016-07-26 14:27 ` bugzilla-daemon [this message]
2016-07-26 14:39 ` bugzilla-daemon
2016-07-29 12:43 ` bugzilla-daemon
2019-09-18 19:22 ` 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-97069-502-5x6GKHfK7h@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