https://bugs.freedesktop.org/show_bug.cgi?id=52171
Bug #: 52171
Summary: [gallium/r600/clover] Simple benchmarks failed to run
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: alexxy(a)gentoo.org
I get benchmarks from here
http://www.bealto.com/gpu-benchmarks.html
CPU ones runs fine while all gpu benchmarks failed with:
Build failed, errors:
clGetProgramInfo NUM_DEVICES failed
HW is 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI
Turks [Radeon HD 6670]
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=55941
Summary: Hybrid graphics i915/radeon. Switch to radeon results
to black screen
Product: Drivers
Version: 2.5
Kernel Version: 3.8.4
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org
ReportedBy: damigos(a)freemail.gr
Regression: No
Created an attachment (id=96611)
--> (https://bugzilla.kernel.org/attachment.cgi?id=96611)
lspci
I have installed Arch Linux on a Dell Inspiron R15 with hybrid Intel/AMD
graphics. vga_switcheroo is enabled and I can control radeon power with "echo
ON/OFF > /sys/kernel/debug/vgaswitcheroo/switch".
But when I try to switch to radeon in console with "echo DIS >
/sys/kernel/debug/vgaswitcheroo/switch" the screen turns off.
I can switch back to intel with "echo IGD >
/sys/kernel/debug/vgaswitcheroo/switch" by blind typing it, and then the screen
turns back on.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=60929
Priority: medium
Bug ID: 60929
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [r600-llvm] mono games with opengl are blocking on
start
Severity: normal
Classification: Unclassified
OS: All
Reporter: lordheavym(a)gmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
Mono games using opengl (Rochard, Bastion, Splice, ...) are blocking on start
when llvm is in use. The only way to make them start is to define R600_LLVM=0
* Mesa from git
* llvm from tstellar repo
* radeon HD6870
I've tried to trace through strace/MONO_LOG_LEVEL=debug/apitrace without much
success. It seem (for bastion) always stuck in 'glXGetCurrentContext'
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=41079
Summary: xorg-r600: display (sometimes) doesn't get updated or
only partially
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: debian(a)carbon-project.org
Created an attachment (id=51451)
--> (https://bugs.freedesktop.org/attachment.cgi?id=51451)
Xorg.0.log from the R600G run (version: Mesa/4a96a02d)
DDX: Mesa/Gallium/xorg-r600 (Git master/4a96a02d)
X: 1.11.0
libdrm2: 2.4.26
This bug can be seen in many applications, e.g. on loading of a website in
Iceweasel or in less, when displaying a text file. AFAIKT it's always
reproducible in Konsole/less:
1. Open a text file.
2. Press End.
Instead of immediately displaying the end of the file, nothing (visible)
happens*, only when you press the up arrow (down arrow doesn't work for me),
the display gets updated and you see almost the end of the file (except the
last line due to the up arrow key depression).
* The blinking cursor gets displayed in the middle of the file name in the
lower left corner.
Again (as with bug #40986), no screenshot possible, because as soon as I press
Print, the screen also gets updated and the updated screen ends up in the
screenshot.
Please let me know, when you need more information.
--
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=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.