https://bugs.freedesktop.org/show_bug.cgi?id=40986
Summary: xorg-r600: graphical glitches on cursor display
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: debian(a)carbon-project.org
Created an attachment (id=51309)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51309)
X.org Log of the R600G run
Git snapshot of: Mesa/ee09c1e1
I've tested Mesa's r600 DDX (xorg state-tracker) with X.org 1.11.0 and KDE
4.6.5. Immediately after KDM is launched, the mouse cursor is distorted (wrong
proportions, longer than wide) and is overlayed with a blue strip pattern
(horizontal) in a rather large square area around the actual cursor. Underneath
the distorted cursor is visible.
There are further graphical glitches (like when you open something in less,
Pos1 and End seem to have no effect, only when you press an arrow key, the
display is updated partially, after the second arrow key press, you get a full
update, waiting doesn't help) or slow reaction to pressing keys (entering
something takes like a felt extra second per key, ie. between pressing the key
and seeing the result on screen), but I guess those are different bugs, right?
If you need further information, just let me know.
--
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=61349
Priority: medium
Bug ID: 61349
Keywords: regression
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [r300g, bisected] piglit rgtc-teximage-01 fails
Severity: normal
Classification: Unclassified
OS: All
Reporter: pavel.ondracka(a)email.cz
Hardware: Other
Status: NEW
Version: git
Component: Drivers/Gallium/r300
Product: Mesa
./bin/rgtc-teximage-01 -auto
r300: DRM version: 2.24.0, Name: ATI RV530, ID: 0x71c5, GB: 1, Z: 2
r300: GART size: 509 MB, VRAM size: 256 MB
r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: YES
Got bad R channel reading back 0x8dbb as 0x1908
Got bad R channel reading back 0x8dbc as 0x1908
PIGLIT: {'result': 'fail' }
first bad commit:
commit ea63491629f48099371f725e7c3779f2982d7a52
Author: Marek Olšák <maraeo(a)gmail.com>
Date: Thu Feb 7 04:36:33 2013 +0100
st/mesa: accelerate glGetTexImage for all formats using a blit
This commit allows using glGetTexImage during rendering and still
maintain interactive framerates.
This improves performance of WarCraft 3 under Wine. The framerate is
improved
from 25 fps to 39 fps in the main menu, and from 0.5 fps to 32 fps in the
game.
v2: fix choosing the format for decompression
GPU:RV530
Mesa: 2fa9e4c97cd7580010a8aa2eb3026e8f2bdb0035
Kernel: 3.7.3-101.fc17.i686
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=39782
Summary: [r300g] XvMC playback fails with MPEG2 video and RV350
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: rankincj(a)googlemail.com
Created an attachment (id=49853)
--> (https://bugs.freedesktop.org/attachment.cgi?id=49853)
Verbose output from mplayer
Trying to play captured DVB-T/MPEG2 data with mplayer gives the following
error:
Unsupported PixelFormat 61
Unsupported PixelFormat 53
Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
The selected video_out device is incompatible with this codec.
Try appending the scale filter to your filter list,
e.g. -vf spp,scale instead of -vf spp.
Full output from the following command is attached:
$ MPLAYER_VERBOSE=1 mplayer -msglevel all=9 -nosound -vo xvmc <file>
--
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=48746
Bug #: 48746
Summary: radeon express 1250 and vdpau doesn't work for
interlaced sample in mplayer.
Classification: Unclassified
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: randrik(a)mail.ru
Using recent vdpau lib (compliled form mesa commit
1ce9205f790471214b69c94f2ee07c4eabfa26f0 - "targets/xvmc-nouveau: fix
accidental hardcoded include path") i saw strange crash inside vdpau driver for
r300g.
sample from
http://streams.videolan.org/samples/MPEG2/interlaced/ - burosch1.mpg
I'll attach gdb.txt (unfortunately i need mesa recompile for more useful debug
output) and player's output.
--
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=39309
Summary: vdpau decodes noise on rv350
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: aaalmosss(a)gmail.com
Created an attachment (id=49216)
--> (https://bugs.freedesktop.org/attachment.cgi?id=49216)
screenshot.png
See the attached screenshot. The colored parts of the noise somewhat resemble
the movements that should be on the screen, but gradually everything fades into
dark green in about 3 seconds. There are no error messages on the console.
The video file is a DVD .VOB (it's a tv show recorded with a dvd recorder box):
MPEG-PS file format detected.
VIDEO: MPEG2 352x288 (aspect 2) 25.000 fps 9682.0 kbps (1210.2 kbyte/s)
llvmpipe is also totally wrong, but in a completely different way.
--
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=39308
Summary: mplayer -vo vdpau draws incorrectly on rv350
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: aaalmosss(a)gmail.com
Created an attachment (id=49215)
--> (https://bugs.freedesktop.org/attachment.cgi?id=49215)
screenshot.png
As I understand it, simply running `mplayer -vo vdpau something.mpg` uses vdpau
as an output surface only, without any decoding done via vdpau (and adding -vc
ffmpeg12vdpau enables decoding). In this mode the video is drawn incorrectly,
as the attached screenshot shows.
Tried with this version (latest from debian-multimedia unstable):
MPlayer SVN-r33367 (C) 2000-2010 MPlayer Team
With libvdpau_softpipe.so mplayer segfaults in this mode. It doesn't segfault
when I enable decoding as well, in that case it renders into a smaller area,
just like r300.
--
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=64600
Priority: medium
Bug ID: 64600
Assignee: dri-devel(a)lists.freedesktop.org
Summary: r600g pyrit OpenCL issue on HD6850
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: spamjunkeater(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Using openSuSE 12.3 with 3.9.2 kernel, mesa-trunk and llvm-trunk.
Pyrit generates this output on radeon HD6850.
> pyrit benchmark
Pyrit 0.4.1-dev (svn r308) (C) 2008-2011 Lukas Lueg http://pyrit.googlecode.com
This code is distributed under the GNU General Public License v3+
Calibrating... LLVM ERROR: Not supported instr: <MCInst 206 <MCOperand
Reg:1046> <MCOperand Reg:1031> <MCOperand Imm:0> <MCOperand Imm:0>>
Detailed debug log is here:
https://bugs.freedesktop.org/attachment.cgi?id=78839
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=34495
Summary: Selecting objects in Blender 2.56 slow with gallium
r600 driver
Product: Mesa
Version: 7.10
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: terraformers(a)gmail.com
Created an attachment (id=43567)
--> (https://bugs.freedesktop.org/attachment.cgi?id=43567)
Xorg Logfile
In Blender 2.56 selecting objects is verry slow.
Maybe this has someting todo with the "r600: fix blender picking" patch from
http://cgit.freedesktop.org/mesa/mesa/commit/?id=cf8af9bcf127e170b64112bd54…
not applied to the gallium driver?
This is with:
mesa-dri-drivers-7.10-0.26.fc15.x86_64
on an HP Compaq 6830s
with ATI Mobility Radeon HD 3430.
Thanks Lars
--
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=41756
Summary: [wine] Alpha Prime crashes in u_upload_data
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: sa(a)whiz.se
Created an attachment (id=52308)
--> (https://bugs.freedesktop.org/attachment.cgi?id=52308)
backtrace from gdb
The game Alpha Prime (running with Wine 1.3.30) crashes shortly after start
with latest git. With 7.11 I get another crash, so I'm not sure if this is a
regression or not.
The backtrace from Wine is below, I also attached a backtrace from gdb but I'm
not sure if it's good or not.
=>0 0xb7547aa0 in libc.so.6 (+0x10faa0) (0x0032fd80)
1 0x7b33aae4 u_upload_data+0x73(upload=0x7caea288, min_out_offset=0x32fd80,
size=0x1200, data=0x5d16da0, out_offset=0x7cb5ce48, outbuf=0x7cb5ce4c,
flushed="═|")
[/home/sa/Programming/gfx/mesa/mesa/src/gallium/auxiliary/util/u_upload_mgr.c:220]
in r600_dri.so (0x0032fd80)
2 0x7b33adce u_vbuf_upload_buffers+0x1dd(mgr=0x7cb5ccc0, min_index=0xcbf6,
max_index=0xcc3d, instance_count=0x1)
[/home/sa/Programming/gfx/mesa/mesa/src/gallium/auxiliary/util/u_vbuf_mgr.c:575]
in r600_dri.so (0x0032fd80)
3 0x7b33bf04 u_vbuf_draw_begin+0x193(mgrb=0x7cb5ccc0, info=0xb9e98c)
[/home/sa/Programming/gfx/mesa/mesa/src/gallium/auxiliary/util/u_vbuf_mgr.c:652]
in r600_dri.so (0x00b9e98c)
4 0x7b13ab1b r600_draw_vbo+0x5a(ctx=0x7ccd1908, info=0xb9e98c)
[/home/sa/Programming/gfx/mesa/mesa/src/gallium/drivers/r600/r600_state_common.c:571]
in r600_dri.so (0x00000003)
5 0x7b1fd5f1 st_draw_vbo+0x330(ctx=0x7cd079a0, arrays=0x7cd54fec,
prims=0xb9ea20, nr_prims=0x1, ib=0xb9ea34, index_bounds_valid=0, min_index=0,
max_index=0x47)
[/home/sa/Programming/gfx/mesa/mesa/src/mesa/state_tracker/st_draw.c:798] in
r600_dri.so (0x00000003)
6 0x7b2b8a1e vbo_validated_drawrangeelements+0x13d(ctx=0x7cd079a0, mode=0x4,
index_bounds_valid=0, start=0xffffffff, end=0xffffffff, count=0xc0,
type=0x1403, indices=0x3a4c7b4, basevertex=0xcbf6, numInstances=0x1)
[/home/sa/Programming/gfx/mesa/mesa/src/mesa/vbo/vbo_exec_array.c:860] in
r600_dri.so (0x000000c0)
7 0x7b2b8b34 vbo_exec_DrawElementsBaseVertex+0xa3(mode=0x4, count=0xc0,
type=0x1403, indices=0x3a4c7b4, basevertex=0xcbf6)
[/home/sa/Programming/gfx/mesa/mesa/src/mesa/vbo/vbo_exec_array.c:1040] in
r600_dri.so (0x03a4c7b4)
8 0x7ea887e4 drawPrimitive+0x11e3(device=0x171740, index_count=0xc0,
StartIdx=0x53ca, idxSize=0x2, idxData=0x3a42020)
[/home/sa/Programming/wine-test/dlls/wined3d/drawprim.c:44] in wined3d
(0x00000002)
9 0x7ea6955b wined3d_device_draw_indexed_primitive+0xda(device=0x171740,
start_idx=0x53ca, index_count=0xc0)
[/home/sa/Programming/wine-test/dlls/wined3d/device.c:4158] in wined3d
(0x02a17b58)
10 0x7eb72d5e IDirect3DDevice9Impl_DrawIndexedPrimitive+0xcd(iface=0x171710,
PrimitiveType=D3DPT_TRIANGLELIST, BaseVertexIndex=0xcbf6, MinVertexIndex=0,
NumVertices=0x48, startIndex=0x53ca, primCount=0x40)
[/home/sa/Programming/wine-test/dlls/d3d9/device.c:1941] in d3d9 (0x000053ca)
11 0x00451479 in alphaprime (+0x51478) (0x7eb8f100)
12 0x7eb6c840 in d3d9 (+0xc83f) (0x7eb74440)
13 0xe84c245c (0x895cec83)
err:mmtime:TIME_MMTimeStop Timer still active?!
err:d3d:wined3d_wndproc Window 0xc0024 is not registered with wined3d.
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: REDWOOD
-- Model: XFX Radeon HD 5670 1GB
-- Display connector: DVI
-- xf86-video-ati: 6.14.2
-- xserver: 1.11.1
-- mesa: 349e4db99e938f8ee8826b0d27e490c66a1e8356
-- drm: 2.4.26
-- kernel: 3.0
--
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=59720
Priority: medium
Bug ID: 59720
Assignee: dri-devel(a)lists.freedesktop.org
Summary: kwin_gles freezes on Mesa from git
Severity: critical
Classification: Unclassified
OS: Linux (All)
Reporter: ken20001(a)ukr.net
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 73459
--> https://bugs.freedesktop.org/attachment.cgi?id=73459&action=edit
kwin_gles backtrace logfile
Using kwin_gles instead of kwin causes freeze after entering KDE. This bug is
reproducible not each time when starting kwin_gles by hand but it's
reproducible almost each time when kwin_gles starting automatically with system
booting. This issue appeared since Jan. ~18-20.
kwin developers believe that problem is in driver. Here is bug report:
https://bugs.kde.org/show_bug.cgi?id=313599
While freeze moment turning compositing off gives nothing. But switching from
kwin_gles to kwin from any VT unfreezes desktop.
Software:
Kubuntu 12.10 x86_64
Linux 3.5.0-22
KDE 4.9.5, desktop effects enabled.
Mesa: 2.1 Mesa 9.1-devel (git-148fc6d quantal-oibaf-ppa)
libdrm-radeon1: 2.4.41+git1301220934.303ca3~gd~q
xserver-xorg-video-radeon: 1:7.0.0+git1301160928.102ee4~gd~q
xserver-xorg-core: 2:1.13.0-0ubuntu6.1
Hardware:
Intel C2D 7200
ASUS P5B Deluxe
AMD Radeon HD 2600 TX
Note. Please se in atachment: kwin_gles backtrace logfile (the same is on
https://bugs.kde.org/show_bug.cgi?id=313599) and two log files with driver
versions that was upgraded at Jan. 18 and Jan. 20.
--
You are receiving this mail because:
You are the assignee for the bug.