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.
https://bugs.freedesktop.org/show_bug.cgi?id=73625
Priority: medium
Bug ID: 73625
Assignee: dri-devel(a)lists.freedesktop.org
Summary: rv730 agp unstable while uvd video playback
Severity: normal
Classification: Unclassified
OS: All
Reporter: roman.elshin(a)gmail.com
Hardware: Other
Status: NEW
Version: unspecified
Component: Drivers/Gallium/r600
Product: Mesa
While uvd video playback (no difference with mplayer, mpv or xbms) video
frequently stops at the loop of several frames, while sound move further. It
very similar to video from https://bugs.freedesktop.org/show_bug.cgi?id=73191
but loop is endless (if gpu will not hang there). Sometimes there are visible
screen corruptions (color squares) before video looping, sometimes gpu hangs up
before visible corruptions.
card - rv730 agp,
kernels - 3.12.7, 3.13-rc7 and before.
mesa, drm, video - from oibaf ppa, i suppose it is current git (own compiled
give the same).
It looks like disabling ColorTiling2D in xorg.conf.d solve this problem.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73619
Priority: medium
Bug ID: 73619
Assignee: dri-devel(a)lists.freedesktop.org
Summary: XServer frequently freezes for a few seconds
Severity: normal
Classification: Unclassified
OS: All
Reporter: arichardson.kde(a)gmail.com
Hardware: Other
Status: NEW
Version: 10.0
Component: Drivers/DRI/R600
Product: Mesa
The XServer randomly freezes for a few seconds or sometimes even 1-2 minutes. I
cannot move the mouse, and the screen does not update.
I have a HD4850 card running on a
3.12.6-1.g080d0df-desktop SMP PREEMPT x86_64 kernel with Mesa 10.0.1 (both from
openSuSE packages). These freezes also happen with the default 3.11 kernel, I
upgraded in the hope of it being fixed, but the issue is still present.
These issues started after the upgrade to openSuSE 13.1 which has a 3.11 kernel
instead of the previous 3.7 kernel. The Mesa version did not change, I was
always running the latest released version. My guess is it has something to do
with the r600 kernel changes in 3.8+.
During these freeze periods I can ssh into my system and top shows no CPU
usage, so the XServer seems to be sleeping instead of being in a busy loop.
dmesg gives me no messages and /var/log/XOrg.0.log is also empty.
I don't know how to get any more detailed logging output. If you provide me
with the necessary environment variables/kernel parameters I will give you
these logs.
Not sure if this helps, but most of the time the freeze happens when I open a
new tab in firefox or switch to a different one. However it also happens at
random intervals using other programs.
It can sometimes take quite a long time until this freeze happens, however once
it has occured once, it usually happens again after a short timespan (1-2
minutes or even less).
Is it possible to debug the XServer just like a normal program using gdb? If
yes I will try to provide a useful backtrace once the next longer freeze
happens
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73504
Priority: medium
Bug ID: 73504
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Segfault in _save_Normal3fv running FlightGear
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: nine(a)detonation.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 91869
--> https://bugs.freedesktop.org/attachment.cgi?id=91869&action=edit
full konsole output of a session with a crash
Running latest FlightGear git version on openSUSE 13.1 with
Mesa-10.1~git20140110-1.1.x86_64, libLLVM35-3.5~svn20140107-1.1.x86_64,
llvm-r600-3.5~svn20140107-1.1.x86_64, libdrm2-2.4.99~git20131225-1.2.x86_64 and
kernel 3.13.0-rc7-6.g57a2f1c-desktop on a Radeon HD 5670 I get segfaults at
seemingly random points. The backtrace always looks like this:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffebb61700 (LWP 10909)]
0x00007fffee1d5d23 in _save_Normal3fv (v=0x0) at vbo/vbo_attrib_tmp.h:340
340 vbo/vbo_attrib_tmp.h: No such file or directory.
(gdb) bt
#0 0x00007fffee1d5d23 in _save_Normal3fv (v=0x0) at vbo/vbo_attrib_tmp.h:340
#1 0x00007fffee0df589 in _ae_ArrayElement (elt=0) at main/api_arrayelt.c:1714
#2 0x00007fffee1cf690 in _save_OBE_DrawArrays (mode=<optimized out>,
start=<optimized out>, count=<optimized out>) at vbo/vbo_save_api.c:1103
#3 0x00007ffff52ea0ed in osg::DrawArrays::draw(osg::State&, bool) const ()
from /opt/FlightGear/lib64/libosg.so.100
#4 0x00007ffff52341fa in osg::Geometry::drawImplementation(osg::RenderInfo&)
const () from /opt/FlightGear/lib64/libosg.so.100
#5 0x00007ffff68b8780 in osg::Drawable::draw(osg::RenderInfo&) const () from
/opt/FlightGear/lib64/libosgParticle.so.100
#6 0x00007ffff623ea98 in osgUtil::RenderLeaf::render(osg::RenderInfo&,
osgUtil::RenderLeaf*) () from /opt/FlightGear/lib64/libosgUtil.so.100
#7 0x00007ffff623312c in
osgUtil::RenderBin::drawImplementation(osg::RenderInfo&, osgUtil::RenderLeaf*&)
() from /opt/FlightGear/lib64/libosgUtil.so.100
#8 0x00007ffff6232f2b in osgUtil::RenderBin::draw(osg::RenderInfo&,
osgUtil::RenderLeaf*&) () from /opt/FlightGear/lib64/libosgUtil.so.100
#9 0x00007ffff6233436 in
osgUtil::RenderBin::drawImplementation(osg::RenderInfo&, osgUtil::RenderLeaf*&)
() from /opt/FlightGear/lib64/libosgUtil.so.100
#10 0x00007ffff6244c13 in
osgUtil::RenderStage::drawImplementation(osg::RenderInfo&,
osgUtil::RenderLeaf*&) () from /opt/FlightGear/lib64/libosgUtil.so.100
#11 0x00007ffff6232f2b in osgUtil::RenderBin::draw(osg::RenderInfo&,
osgUtil::RenderLeaf*&) () from /opt/FlightGear/lib64/libosgUtil.so.100
#12 0x00007ffff624352a in osgUtil::RenderStage::drawInner(osg::RenderInfo&,
osgUtil::RenderLeaf*&, bool&) () from /opt/FlightGear/lib64/libosgUtil.so.100
#13 0x00007ffff624446e in osgUtil::RenderStage::draw(osg::RenderInfo&,
osgUtil::RenderLeaf*&) () from /opt/FlightGear/lib64/libosgUtil.so.100
#14 0x00007ffff6253e4e in osgUtil::SceneView::draw() () from
/opt/FlightGear/lib64/libosgUtil.so.100
#15 0x00007ffff5b02a14 in osgViewer::Renderer::draw() () from
/opt/FlightGear/lib64/libosgViewer.so.100
#16 0x00007ffff5b03c2a in
osgViewer::Renderer::operator()(osg::GraphicsContext*) () from
/opt/FlightGear/lib64/libosgViewer.so.100
#17 0x00007ffff52698e1 in osg::GraphicsContext::runOperations() () from
/opt/FlightGear/lib64/libosg.so.100
#18 0x00007ffff52740c9 in osg::RunOperations::operator()(osg::GraphicsContext*)
() from /opt/FlightGear/lib64/libosg.so.100
#19 0x00007ffff5273a38 in osg::GraphicsOperation::operator()(osg::Object*) ()
from /opt/FlightGear/lib64/libosg.so.100
#20 0x00007ffff52dec8f in osg::OperationThread::run() () from
/opt/FlightGear/lib64/libosg.so.100
#21 0x00007ffff527399e in osg::GraphicsThread::run() () from
/opt/FlightGear/lib64/libosg.so.100
#22 0x00007ffff4c52bfc in OpenThreads::ThreadPrivateActions::StartThread(void*)
() from /opt/FlightGear/lib64/libOpenThreads.so.13
#23 0x00007ffff77260db in start_thread () from /lib64/libpthread.so.0
#24 0x00007ffff206090d in clone () from /lib64/libc.so.6
Is this a bug in Mesa or more probably in FlightGear?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73480
Priority: medium
Bug ID: 73480
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Segmentation fault starting mpeg2 playback using XBMC
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: doctor64(a)gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
Created attachment 91830
--> https://bugs.freedesktop.org/attachment.cgi?id=91830&action=edit
dmesg output
When trying to play mpeg2 live TV stream in XBMC 13, using wsnipex ppa MESA and
VDPAU, XBMC crashed.
h264 streams using VDPAU play without problems.
Disabling VDPAU in XBMC remove crash.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73457
Priority: medium
Bug ID: 73457
Assignee: dri-devel(a)lists.freedesktop.org
Summary: mpeg4 through vdpau randomly either correct or garbled
(on same file!)
Severity: normal
Classification: Unclassified
OS: All
Reporter: adam(a)aphirst.karoo.co.uk
Hardware: x86-64 (AMD64)
Status: NEW
Version: 10.0
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 91790
--> https://bugs.freedesktop.org/attachment.cgi?id=91790&action=edit
mpv verbose log, when video decodes successfully
This is somewhat difficult to explain.
* AMD PALM E2-1800 APU
* Arch Linux x86_64
* Kernel 3.12.6-ck (also with vanilla 3.12.6)
* mesa 10.0.1, xf86-video-ati 7.2.0
One of the following three situations occurs, seemingly at random, when opening
an mpeg4 video file using any player which supports vdpau hardware-decoding
(e.g. mplayer r36498, VLC 2.1.2, mpv 0.3.2)
1. The video decodes and plays just fine
2. The video decodes incorrectly, with bright-green garbling, and general
smearing
3. The video decodes and plays fine, BUT with a couple of small artefacts
either in the player window, or anywhere on the screen (the artefacts are
little black squares, inside which are a few fluorescent-coloured pixels
flickering)
The interesting point is that, on the same file, you can close and re-open the
video player and receive a different random outcome each time. I'm in the habit
of trying a few times to open my .avi videos until it "just works".
This is not the same as the mpeg4 ASP garbling issue which I reported a month
or so ago, which was 100% consistent on the affected files. For this bug, the
files which display *this* problem are 'normal' mpeg4 videos, and whether or
not decoding succeeds appears to be completely random.
Frustratingly, neither the video player's verbose logs, nor the DPM messages in
dmesg, indicate anything *at all* different between successful and unsuccessful
attempts.
I'll upload to this report a couple of log files, including the outputs of
ffmpeg -i on a selection of affected files.
I'll also upload some video samples, bear with me.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73444
Priority: medium
Bug ID: 73444
Assignee: dri-devel(a)lists.freedesktop.org
Summary: wayland/weston EGL/GLESv2 - top portion of screen in
fullscreen: vertices being clipped/flicker
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: emiettin(a)edu.lahti.fi
Hardware: x86-64 (AMD64)
Status: NEW
Version: 10.0
Component: Drivers/Gallium/r600
Product: Mesa
In fullscreen wayland/weston EGL/GLESv2 clients without X11 (as in weston
launched from a tty), vertices ending up on the top 5-10% portion of the
vertical screen space are being clipped (as in seemingly skipped altogether and
disappearing), despite setting up an appropriate projection matrix + calling
glViewport. This results in flickering sawtooth-like edges on the top of the
screen area.
This effect doesn't show up
- in windowed mode
- in screenshots (weston Super+s)
- in screen capture (weston Super+r)
- while zoomed in using the weston Super+mwheel shortcut, or
- when using weston through X11.
Asking about this on #dri-devel on Freenode lead to the following hypothesis by
pq:
12:30 < pq> so if super+s, or zoom, or having it in a window makes the problem
go away, then the fundamental difference is likely that when weston composites,
everything goes well, but when weston tries to scan out the client image
directly, something breaks.
This occurs at least in mesa 9.2.x through git master.
setup:
Arch Linux x86_64 3.12.6-1,
Radeon HD 5770 w/ {ati-dri, mesa, mesa-libgl}-9.2.5-1, -10.0.1-1, or -git
wayland-1.3.0-1, weston-1.3.1-2 or git.
--
You are receiving this mail because:
You are the assignee for the bug.