https://bugs.freedesktop.org/show_bug.cgi?id=41051
Summary: Portal hard locks the machine on rv350.
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: oreaus(a)gmail.com
I recently installed Steam and subsequently the game Portal through wine and it
starts but after the loading screen, it hard locks the machine. The system
requirements for the game are low enough for this machine to handle. I'm not
really sure how to diagnose the problem but I've tested on 2.6.40.3-0.fc15.i686
and 2.6.38-11-generic with mesa master yielding same results. Using OpenGL
version string: 2.1 Mesa 7.12-devel (git-47b556f) with OpenGL renderer string:
Gallium 0.4 on ATI RV350.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=36596
Summary: Major 2D performance bottleneck (most noticeable with
compiz)
Product: Mesa
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: bluesloth600(a)gmail.com
Created an attachment (id=46072)
--> (https://bugs.freedesktop.org/attachment.cgi?id=46072)
lspci -v
With compiz, making a new window or resizing a window makes the framerate drop
to 2 fps for about 5 or 6 seconds.
Running conky makes the frame rate that low most of the time, alternating with
brief moments of decent performance. With a more traditional window manager
(openbox), a lot of programs (including xterm) freeze briefly every time conky
redraws itself, so it seems like that particular problem is not entirely a Mesa
bug. Things run smoothly with the fbdev Xorg driver.
I tried compiz with the --no-fbo option once, and the framerate stayed at 2 fps
until I rebooted. Restarting X didn't help, I actually had to reboot.
With the classic Mesa drivers, compiz would sometimes take a long time to
render a few frames, but not nearly as often as it does now.
I've had this problem with the Debian Mesa packages since they switched to
gallium, and with git master (as of yesterday) built with and without
--enable-gallium-llvm.
I run Debian sid on a Dell Inspiron 1721 with an integrated Radeon X1270.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=35861
Summary: [r300g] Oilrush: whiter triangle between center of the
screen and horizon
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: minor
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: pavel.ondracka(a)email.cz
Created an attachment (id=45121)
--> (https://bugs.freedesktop.org/attachment.cgi?id=45121)
terminal output
There is a strange triangle of whiter area and missing effects between screen
center and horizon in Oilrush.
I'm attaching terminal output, however I don't think there is anything
important, just a few of:
Mesa warning: glDraw[Range]Elements(start 130, end 877, count 1650, type
0x1403, indices=0x1c2)
end is out of bounds (max=876) Element Buffer 31 (size 3750)
This should probably be fixed in the application.
and
Mesa: User error: GL_INVALID_VALUE in glTexSubImage2D(xoffset+width)
OpenGL error: invalid value
However both of those errors are also present with llvmpipe which renders fine
(not 100% fine, but this bug is not present there).
RADEON_NOT_TCL=1 also solves this issue, where READEON_DEBUG=noopt has no
effect.
BTW you need to set MESA_EXTENSION_OVERRIDE="-GL_ARB_draw_instanced" when using
llvmpipe of software TCL otherwise you run into other troubles like:
GLShader::loadVertex(): error in
"core/shaders/default/meshes/vertex_base.shader" file
defines:
UNKNOWN,QUALITY_LOW,MULTISAMPLE_0,USE_INSTANCING,USE_TEXTURE_3D,USE_ALPHA_FADE,USE_ENVIRONMENT,OPENGL,USE_PSEUDO_INSTANCING,USE_PSEUDO_TRANSFORM,HAS_ARB_DRAW_INSTANCED,BASE_AMBIENT_REFLECTION_CUBE,AMBIENT,PAINT,OPACITY,MULTIPLY_0
0:194(39): error: `gl_InstanceID' undeclared
0:194(42): error: Operands to arithmetic operators must be numeric
0:194(19): error: cannot construct `ivec3' from a non-numeric data type
0:194(58): error: Operands to arithmetic operators must be numeric
and almost no rendering at all.
My system
GPU:RV530
mesa: 9f013a8233197d4a0482661cb37cfeac1a61b804
Kernel: 2.6.38
Oilrush version: 0.61
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=34588
Summary: Screen corruption when running gtkperf on awesomewm
Product: Mesa
Version: git
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: jeff(a)deserettechnology.com
Recently, gtkperf will tear my whole screen apart in awesomewm 3.4.9 when it
gets to the drawing sections. I will try to take and attach a photo soon. I am
using cairo 1.10.2 with xcb enabled. I just compiled mesa, ati-dri, libgl,
xf86-ati from git today. This problem does *not* occur on a composited kwin
desktop on the same machine. Using a Macbook Pro 2,2 with Radeon Mobility
X1600. Using r300g.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=92184
Bug ID: 92184
Summary: Many piglit assertion failures in
radeon_unmap_renderbuffer
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R100
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: idr(a)freedesktop.org
QA Contact: dri-devel(a)lists.freedesktop.org
While doing other things, I noticed quite a few piglit tests crashing with
radeon_fbo.c:454: radeon_unmap_renderbuffer: Assertion `ok' failed.
This occurs when r100_blit fails. Just skimming the code, there are a LOT of
reasons that r100_blit could return false, so it seems like there should be
some fallback path. Some (perhaps all?) of the failures also log
WRITE DOMAIN RELOC FAILURE 0x1 6 4
Some tests that fail in this manner are:
bin/fbo-depthstencil copypixels default_fb -auto
bin/stencil-drawpixels -auto
bin/texsubimage -auto
bin/tex3d-depth1 -auto -fbo
There are many others. On my last run there were 39 crashes (out of 1072 tests
not skipped), and most of those seem to be this assertion.
If it matters, this was on:
Linux grundgetta.home 4.1.6-201.fc22.x86_64 #1 SMP Fri Sep 4 17:49:24 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
00:01.0 PCI bridge [0604]: Intel Corporation 82865G/PE/P AGP Bridge [8086:2571]
(rev 02)
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] RV200 [Radeon 7500/7500 LE] [1002:5157]
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=41849
Bug #: 41849
Summary: Mesa error megaglest
Classification: Unclassified
Product: Mesa
Version: 7.11
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: korchoi(a)mail.ru
Mesa 7.11 implementation error: Unexpected texture format in
radeon_update_wrapper()
Please report at bugs.freedesktop.org
Megaglest crashes entering game, reports the error above.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.