https://bugs.freedesktop.org/show_bug.cgi?id=75602
Priority: medium
Bug ID: 75602
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Unigine Heaven/Vally: Multi monitor rendering does not
work
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: knut.tidemann(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 94870
--> https://bugs.freedesktop.org/attachment.cgi?id=94870&action=edit
Unigine vally output
When trying to start the unigine demos with multiple monitors enabled (Wall 2x1
or any other of the options in the launch dialog), it will exit with a failure.
It seems that Mesa is using the compatability context which is limited to
OpenGL 3.0.
I've attached the output log of Unigine Vally when started with multi monitor
enabled.
The demos run fine when only a single monitor is enabled.
I'm currently using mesa-git g085f61b and linux 3.13.5 on Arch Linux with a
Radeon 5730.
The same issue can be seen when I try to enable dual output stereo 3D, which
should start two separate windows that it will render to.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=75112
Priority: medium
Bug ID: 75112
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Meta Bug for HyperZ issues on r600g and radeonsi
Severity: normal
Classification: Unclassified
OS: All
Reporter: andreas.boll.dev(a)gmail.com
Hardware: All
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
This bug is for tracking all the outstanding HyperZ issues on r600g and
radeonsi.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74766
Priority: medium
Bug ID: 74766
Assignee: dri-devel(a)lists.freedesktop.org
Summary: no image output in Sonic Robo Blast 2 in OpenGL mode
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: thepouar(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: 10.0
Component: Drivers/DRI/R600
Product: Mesa
Created attachment 93729
--> https://bugs.freedesktop.org/attachment.cgi?id=93729&action=edit
screenshot
All I see is a bunch of gray and black rectangles in OpenGL mode
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74765
Priority: medium
Bug ID: 74765
Assignee: dri-devel(a)lists.freedesktop.org
Summary: weird glitches in firefox
Severity: normal
Classification: Unclassified
OS: All
Reporter: thepouar(a)gmail.com
Hardware: Other
Status: NEW
Version: 10.0
Component: Drivers/DRI/R600
Product: Mesa
Created attachment 93727
--> https://bugs.freedesktop.org/attachment.cgi?id=93727&action=edit
screenshot of affected area
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74726
Priority: medium
Bug ID: 74726
Assignee: dri-devel(a)lists.freedesktop.org
Summary: r600g: unrecoverable GPU lockup after glDrawElements
INVALID_ENUM
Severity: normal
Classification: Unclassified
OS: All
Reporter: edwin+mesa(a)etorok.net
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 93679
--> https://bugs.freedesktop.org/attachment.cgi?id=93679&action=edit
corrupt.trace
If you send a lot of invalid glDrawElements commands to Mesa it can cause a GPU
lockup. Would it be possible to validate this Mesa side / or kernel CS checker
side to avoid the GPU lockup? [1]
If you replay the attached trace on r600g you get a GPU lockup, see
attachments:
* gpureset.log: dmesg when reboot is the only solution, no text console, no X,
nothing works until a reboot
* text_recovered.log: dmesg when I can kill the application and X, and get to
a framebuffer text console. Starting X is impossible though, unless I reboot
I've run the trace under valgrind, and I see no valgrind errors, but of course
I see a lot of Mesa errors. The mesa errors shouldn't cause a GPU lockup
though.
I reproduced this with the 10.1 branch, but similar lockups happen on the
10.0.2 release too (if you force the version to 3.3), so it doesn't seem to be
related to the 3.3 work on the 10.1 branch.
Mesa built like this:
$ ./configure --enable-dri --enable-glx-tls --enable-shared-glapi
--enable-texture-float --enable-xa --disable-xvmc --disable-vdpau
--with-gallium-drivers=r600,swrast LLVM_CONFIG=/usr/bin/llvm-config-3.4
--disable-dri3 --enable-debug
OpenGL version:
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV730
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.0-rc1
(git-1e6bba5)
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.1.0-rc1 (git-1e6bba5)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
kernel:
$ uname -a
Linux debian 3.14.0-rc1-00015-g7c4c62a #48 SMP PREEMPT Sat Feb 8 17:33:48 EET
2014 x86_64 GNU/Linux
[1]
There are some use-after-free bugs in the gltut tutorials when you press
Escape: it frees some stuff, then calls glutLeaveMainLoop(), but freeglut still
calls display(), causing use-after-frees. Of course its expected that the
application itself might crash, or otherwise misbehave, but I was not expecting
an unrecoverable GPU lockup.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74539
Priority: medium
Bug ID: 74539
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [r600g] Memory leak when playing WoW with RV790
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: rankincj(a)googlemail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 93417
--> https://bugs.freedesktop.org/attachment.cgi?id=93417&action=edit
dmesg log showing memory allocation failure.
I am seeing a possible memory leak while playing WoW-64.exe with my RV790. The
problem seems to happen after ~ 1 hour of play:
[ 117.896993] fuse init (API version 7.22)
[ 3326.401752] WoW-64.exe: page allocation failure: order:4, mode:0x10c0d0
[ 3326.407099] CPU: 7 PID: 31106 Comm: WoW-64.exe Not tainted 3.12.9 #1
[ 3326.412185] Hardware name: Gigabyte Technology Co., Ltd.
EX58-UD3R/EX58-UD3R, BIOS FB 05/04/2009
[ 3326.419812] ffff8801afdcdbd0 ffffffff812d0071 0000000000000001
ffffffff810a0c50
[ 3326.426142] 0000000000000001 0000000000000000 ffffffff8164ff80
ffffffff8164f400
[ 3326.432429] 000000000010c0d0 ffffffff812cebb7 ffffffff8164f400
ffff880100000000
I *think* I can bisect this, although it might make some time:
9bace99d77642f8fbd46b1f0be025ad758f83f5e BAD
f5bd5568abcc234c1c2b6a4bb67b880706f3caed GOOD
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=74140
Priority: medium
Bug ID: 74140
CC: tstellar(a)gmail.com
Assignee: dri-devel(a)lists.freedesktop.org
Summary: scrypt mining via bfgminer generates a too large
opencl kernel
Severity: normal
Classification: Unclassified
OS: All
Reporter: slicksam(a)gmx.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Needs less aggressive unrolling and/or opencl function call support.
Posted as a bug by request of tstellar
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73739
Priority: medium
Bug ID: 73739
Assignee: dri-devel(a)lists.freedesktop.org
Summary: RV630 flickering on "Wargame European Escalation"
Severity: normal
Classification: Unclassified
OS: All
Reporter: karzisss(a)hotmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
On Wargame European Escalation there is flickering while you play and you
select a "unit" to move.
I've tested it with following setups:
-(x)Ubuntu 13.10 stock mesa-kernel
-(x)Ubuntu 13.10 Oibaf's ppa + 3.13-RC7 kernel
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73649
Priority: medium
Bug ID: 73649
Assignee: dri-devel(a)lists.freedesktop.org
Summary: SIGSEGV: r600_sb::bc_parser::decode_shader()
Severity: normal
Classification: Unclassified
OS: All
Reporter: octoploid(a)yandex.com
Hardware: Other
Status: NEW
Version: 10.0
Component: Drivers/Gallium/r600
Product: Mesa
Trying to run the http://code.google.com/p/glyphy/ demo with
r600 LLVM backend enabled I get:
Enter: demo_glstate_create
Enter: demo_shader_create_program
Enter: compile_shader
Leave: compile_shader
Enter: compile_shader
Leave: compile_shader
Enter: link_program
Leave: link_program
Leave: demo_shader_create_program
Enter: demo_atlas_create
Leave: demo_atlas_create
Leave: demo_glstate_create
Enter: demo_view_create
Leave: demo_view_create
Welcome to GLyphy demo
45 glyphs; avg num endpoints 23.78; avg error 60.4%; avg tex fetch 2.96; avg
2.23kb per glyph
Setting vsync on.
Setting sRGB framebuffer on.
No sRGB framebuffer extension found; failed to set sRGB framebuffer
Setting debug to 0
Setting contrast to 1
Setting gamma_adjust to 1
Setting outline to 0
Setting outline_thickness to 1
Setting boldness to 0
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6a865e6 in r600_sb::bc_parser::decode_shader() () from
/usr/lib64/dri/r600_dri.so
(gdb) bt
#0 0x00007ffff6a865e6 in r600_sb::bc_parser::decode_shader() () from
/usr/lib64/dri/r600_dri.so
#1 0x00007ffff6a8b23e in r600_sb_bytecode_process () from
/usr/lib64/dri/r600_dri.so
#2 0x00007ffff6a20966 in r600_shader_select () from /usr/lib64/dri/r600_dri.so
#3 0x00007ffff6a22100 in r600_create_shader_state () from
/usr/lib64/dri/r600_dri.so
#4 0x00007ffff6b69bae in st_translate_fragment_program () from
/usr/lib64/dri/r600_dri.so
#5 0x00007ffff6b6bf66 in st_get_fp_variant () from /usr/lib64/dri/r600_dri.so
#6 0x00007ffff6a60a15 in update_fp () from /usr/lib64/dri/r600_dri.so
#7 0x00007ffff6a7a63f in st_validate_state () from /usr/lib64/dri/r600_dri.so
#8 0x00007ffff68e807a in st_Clear.lto_priv.2949 () from
/usr/lib64/dri/r600_dri.so
#9 0x0000000000406df2 in demo_view_display (vu=0x9f0ae0, buffer=0x83e260) at
demo-view.cc:640
#10 0x00007ffff7bc2934 in fghcbDisplayWindow () from /usr/lib/libglut.so.3
#11 0x00007ffff7bc63f9 in fgEnumWindows () from /usr/lib/libglut.so.3
#12 0x00007ffff7bc2f55 in glutMainLoopEvent () from /usr/lib/libglut.so.3
#13 0x00007ffff7bc373d in glutMainLoop () from /usr/lib/libglut.so.3
#14 0x0000000000403250 in main (argc=1, argv=<optimized out>) at
glyphy-demo.cc:136
--
You are receiving this mail because:
You are the assignee for the bug.