https://bugs.freedesktop.org/show_bug.cgi?id=78009
Priority: medium
Bug ID: 78009
Assignee: dri-devel(a)lists.freedesktop.org
Summary: ETQW and TF2 creenshots have alpha=0
Severity: normal
Classification: Unclassified
OS: All
Reporter: aaalmosss(a)gmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Enemy Territory Quake Wars saves 32 bit TGA screenshots, and the alpha value of
the pixels is set to 0x00 instead of 0xFF. Team Fortress 2 saves 24 bit TGA
screenshots (before converting to jpeg), and the whole thing is black.
I also tried Doom3, Prey, Quakespasm, Nexuiz, UT2004, Half-Life 1, and Garry's
Mod but those are not affected.
This is a regression, but I couldn't find an old version of mesa that worked. I
went back as far as to 5ffa28df4e4cc224 (the first one that compiles with bison
3), and libdrm 2.4.44, but couldn't find a version that was good. When
screenshots were good, I had mesa 9.2.2 installed, and I used 10.0-dev for
running games. Now I have 10.1 installed. Maybe I need to roll back the
installed libs?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=77907
Priority: medium
Bug ID: 77907
Assignee: dri-devel(a)lists.freedesktop.org
Summary: OpenCL test 'Arithm/Absdiff.Mat/20' from OpenCV hangs
HD5470M
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: brunojimen(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
The effects are that when running that test, the screen freezes for a while,
then goes to black, then shows back my desktop, happening this some times.
After some debugging, the hang seems to occur with the compute shader sent to
the GPU, as the system freezes when it waits for the GPU to finish.
My system is Arch Linux with:
- AMD CEDAR 5470M
- kernel 3.14.1-1
- llvm at revision 207118
- mesa at commit 352e06d
- opencv at commit bb4199b
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=77745
Priority: medium
Bug ID: 77745
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [r600g] Call of Dutty 4 crashes under Wine due to
running out of memory
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: jaimerave(a)gmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 97706
--> https://bugs.freedesktop.org/attachment.cgi?id=97706&action=edit
Apitrace
While trying to play Call Of Duty 4 under Wine using the mesa driver the game
crashes while loading a saved level.
I have tried to get an ApiTrace of the game starting, looks like there's a
memory leak in some part of Mesa because when I use the Catalist driver the
game starts correctly.
I'm using Wine 1.7.17, Mesa from Git and Ubuntu 14.04.
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Madison [Mobility Radeon HD 5730 / 6570M] (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 1594
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 45
Region 0: Memory at b0000000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at c4000000 (64-bit, non-prefetchable) [size=128K]
Region 4: I/O ports at 4000 [size=256]
Expansion ROM at c4040000 [disabled] [size=128K]
Capabilities: <access denied>
Kernel driver in use: radeon
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76954
Priority: medium
Bug ID: 76954
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Unigine Tropics has rendering issues all over the
place with LLVM on Cayman
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: v10lator(a)myway.de
Hardware: All
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
This video was made with LLVM + SB: https://vimeo.com/90754450
With LLVM and noSB it doesn't render anything at all (the scene is just black).
Without LLVM everything seems to be fine. HyperZ doesn't make a difference.
If you need any more information feel free to ask.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76919
Priority: medium
Bug ID: 76919
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Random junk at the bottom of non-multiple-of-4
compressed textures (original or mipmapped)
Severity: normal
Classification: Unclassified
OS: All
Reporter: bugspam(a)moreofthesa.me.uk
Hardware: Other
Status: NEW
Version: unspecified
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 96745
--> https://bugs.freedesktop.org/attachment.cgi?id=96745&action=edit
Example image (with mipmaps), the height of which triggers the problem
There seems to be a problem with some compressed textures. When the height of
the image (more specifically, of the mipmap level used) is not a multiple of 4,
it appears that the bottom part of the image – as rendered – contains random
junk, apparently set at image load time.
The example image will show the problem at its original size. I've also played
with its height (initially 570px): increasing it to a multiple of 4 would
remove the problem if it's rendered using the full-size version, but since when
reduced by one level the height is again not a multiple of 4, the problem
re-appears. Setting the full-size height to 576px moves the problem down
further.
(We're using http://crunch.googlecode.com/svn/trunk/ for image
(de)compression.)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=76190
Priority: medium
Bug ID: 76190
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [r600g-evergreen] GPU hang in Stunt Rally (bisected)
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: b.bellec(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
In Stunt Rally (v2.2.1), when applying specific graphic settings, the GPU hang
few seconds after a race is started.
This is since commit 7e414b58640aee6e243d337e72cea290c354f632
glsl: break the gl_FragData array into separate gl_FragData[i] variables
author: Marek Olšák
date: 2013-10-29 22:50:01 (GMT)
Easy steps to reproduce:
1- Download and extract the Linux game binary here:
http://sourceforge.net/projects/stuntrally/files/2.2.1/
2- Launch the game with the shell script (./StuntRally-2.2.1-linux/stuntrally)
(it will launch a 64-bit binary on a 64-bit system)
3- Set the graphical settings to "Lowest", and close the game
4- Relaunch the game, and set this settings now:
-> Graphics > Vegetation > "Trees multiplier" to 1.00 (in fact any value
but 0.0)
-> Graphics > Vegetation > check "Use Impostors"
-> Graphics > Vegetation > uncheck "Impostors Only"
-> Effects > check "Effects enabled"
-> Effects > check "Soft Particules"
5- Close and relaunch the game in order to be sure that these new settings are
applied
6- Start a "Single race", use the default one (track "I6-Flooded")
If one of these gfx settings is different, the GPU will not hang.
The last good commit (aec20d66d9d13e0acd6a7199b63e1383e1e9900a) doesn't hangs
the GPU when these settings are applied.
R600_DEBUG=nosb doesn't solve the issue.
I also tested with RV770 and there is no problem (expect rendering bugs for
some things but not sure this commit is the problem in that case).
I tried to test with nouveau too (nv40 driver on a NV49/7900GT) but the game
crash at start (segfault), with git master or even with the commit aec20d66d9).
Note that the game Stunt Rally have many graphical settings available, I don't
know if all are very well handled by mesa. Game bugs or mesa "bugs"... I don't
know.
Config:
Fedora 19 x86-64
kernel 3.13.5-103.fc19.x86_64
libdrm 2.4.50
AMD CYPRESS (Radeon HD5870 with 1GB VRAM)
Build:
./autogen.sh --with-gallium-drivers=r600,nouveau --with-dri-drivers=
--enable-texture-float --disable-dri3 --disable-r600-llvm-compiler
--disable-gallium-llvm --enable-64-bit CFLAGS="-O0 -g -m64" CXXFLAGS="-O0 -g
-m64" --libdir=/usr/lib64
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=75784
Priority: medium
Bug ID: 75784
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Octodad: Dadliest Catch - GPU crash on CAYMAN
Severity: normal
Classification: Unclassified
OS: All
Reporter: v10lator(a)myway.de
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 95129
--> https://bugs.freedesktop.org/attachment.cgi?id=95129&action=edit
dmesg messages
This seems to be caused by R600_DEBUG=sb, with R600_DEBUG=nosb the game seems
to run fine.
Tested on a Radeon HD 6950.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=75732
Priority: medium
Bug ID: 75732
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Memory leak with celestia
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
This bug might be a duplicate of #74549. However, WoW + Wine + Valgrind is
currently proving to be an intractable problem, and so I've decided to Valgrind
celestia instead (since at least I've managed to get THAT to running again on
x86_64!!!!!!!)
For this test, git HEAD was set to:
commit 9bace99d77642f8fbd46b1f0be025ad758f83f5e
Author: Zack Rusin <zackr(a)vmware.com>
Date: Tue Jan 28 16:34:18 2014 -0500
gallivm: fix opcode and function nesting
I executed the following command:
$ valgrind --leak-check=full celestia
and amidst all of the other issues that Valgrind complained about, it also
happened to mention this:
==7446== 352 bytes in 1 blocks are possibly lost in loss record 8,803 of 9,718
==7446== at 0x4C291D4: calloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==7446== by 0x4011C44: _dl_allocate_tls (dl-tls.c:296)
==7446== by 0xBEE8862: pthread_create@@GLIBC_2.2.5 (allocatestack.c:580)
==7446== by 0x22F18208: pipe_thread_create.constprop.7 (threads_posix.h:264)
==7446== by 0x22F18B47: radeon_drm_winsys_create (radeon_drm_winsys.c:661)
==7446== by 0x22BA18F5: create_screen (drm_target.c:38)
==7446== by 0x22F13876: dri2_init_screen (dri2.c:1044)
==7446== by 0x22BA295F: driCreateNewScreen2 (dri_util.c:158)
==7446== by 0x52DC260: dri2CreateScreen (dri2_glx.c:1240)
==7446== by 0x52B67E8: __glXInitialize (glxext.c:778)
==7446== by 0x52B31AA: GetGLXPrivScreenConfig.part.2 (glxcmds.c:174)
==7446== by 0x52B392F: glXChooseVisual (glxcmds.c:170)
==7446==
==7446== 360 bytes in 5 blocks are possibly lost in loss record 8,811 of 9,718
==7446== at 0x4C291D4: calloc (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==7446== by 0xA24CEC6: g_malloc0 (in /usr/lib64/libglib-2.0.so.0.3800.2)
==7446== by 0x9FBC1D4: g_closure_new_simple (in
/usr/lib64/libgobject-2.0.so.0.3800.2)
==7446== by 0x9FBD671: g_cclosure_new (in
/usr/lib64/libgobject-2.0.so.0.3800.2)
==7446== by 0x781E83F: gtk_action_group_add_toggle_actions_full (in
/usr/lib64/libgtk-x11-2.0.so.0.2400.22)
==7446== by 0x4623F5: main (in /usr/bin/celestia)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=75699
Priority: medium
Bug ID: 75699
Assignee: dri-devel(a)lists.freedesktop.org
Summary: mplayer crashes
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: slash(a)ac.auone-net.jp
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 95013
--> https://bugs.freedesktop.org/attachment.cgi?id=95013&action=edit
backtrace
If I play any file with mplayer -vo vdpau -vf flip, it crashes with sigsegv
instantly.
--
You are receiving this mail because:
You are the assignee for the bug.