https://bugs.freedesktop.org/show_bug.cgi?id=91930
Bug ID: 91930
Summary: Program with GtkGLArea widget does not redraw
Product: Mesa
Version: 11.0
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: pavol(a)klacansky.com
QA Contact: dri-devel(a)lists.freedesktop.org
If the program contains GtkGLArea widget then whole window does not redraw upon
an action (dragging sliders), and redraw can be done by alt-tabing or swapping
workspaces.
This example app shows the defect.
https://github.com/ebassi/glarea-example
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=91251
Bug ID: 91251
Summary: [r600g] "ARK: Survival Evolved" game: shader errors
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: b.bellec(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
CC: b.bellec(a)gmail.com
With the slowest gfx settings, the game "ARK: Survival Evolved" starts on my
computer though it's too slow to be played.
That said, the logs is repeating these 2 errors:
steam.desktop[23285]: EE r600_shader.c:158 r600_pipe_shader_create -
translation from TGSI failed !
steam.desktop[23285]: EE r600_state_common.c:766 r600_shader_select - Failed to
build shader variant (type=1) -1
Config:
Intel Core i5-2500K / 8 GB / AMD HD5850 1GB (Evergreen)
Fedora 22 (64-bit)
Kernel 4.0.6-300.fc22.x86_64
Mesa 10.7.0-devel (git-86a3557) (current master)
Apitrace:
ark.trace.xz =>
https://drive.google.com/file/d/0B7D2Y0QXFND2c1RocTJ5azE0Qms/view?usp=shari…
(440 MB)
sha256sum: fe16cefdca5389dd3215590c6bed34afddf590b22af7b436d36736d81981b30e
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=91001
Bug ID: 91001
Summary: lock-ups with video playback in mpv and vlc with vdpau
enabled
Product: Mesa
Version: 10.5
Hardware: x86-64 (AMD64)
URL: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=7890
00
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: arthur.marsh(a)internode.on.net
QA Contact: dri-devel(a)lists.freedesktop.org
with kernel 4.1.0-rc8 and mesa 10.5.7-1, using a Radeon 3850HD video card,
video playback in mpv and vlc with vdpau enabled, particularly with 1080
resolution videos caused weird colour effects and eventual lock-ups (see Debian
bug report at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789000 ).
I'm happy to run further tests.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=90404
Bug ID: 90404
Summary: Shaders are choppy
Product: Mesa
Version: 10.5
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: charlespoetwolf(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 115700
--> https://bugs.freedesktop.org/attachment.cgi?id=115700&action=edit
Link to the apitrace (Couldn't figure out how to trim it small enough)
I'm pretty sure these are the shaders that are broken. They have an arboreal
effect on my screen. Attached is an apitrace and screenshot of what it looks
like. The video card specifically is AMD Radeon HD 3650 Mobility
The item used for the report is Assault Android Cactus demo.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=90278
Bug ID: 90278
Summary: random computer freeze with screen corruption
Product: Mesa
Version: 10.5
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: spam(a)abma.de
QA Contact: dri-devel(a)lists.freedesktop.org
my computer randomly freezes. sadly there are no errors in kern.log / xorg.log
related to it i can only reset the computer.
I've an Radeon HD 5750.
it always crashes for me, when i run https://github.com/abma/qvdpautest
are there some instructions how to debug such crashes/freezes? what info do you
need?
i'm using Ubuntu 15.04 / amd64.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=90219
Bug ID: 90219
Summary: Half as many compute cores reported as when running
with 'fglrx'
Product: Mesa
Version: 10.4
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: benjiwiebe14(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
When using 'fglrx', this program
(https://gist.github.com/BenjiWiebe/52a01924009d3534a5d6) reports 24 compute
cores. When running with r600, it reports only 12.
I have only one GPU, a Radeon HD6970.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=90184
Bug ID: 90184
Summary: [r600g] GPU lockup when using kdenlive GPU
acceleration
Product: Mesa
Version: 10.5
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: paul(a)konecny.at
QA Contact: dri-devel(a)lists.freedesktop.org
Created attachment 115343
--> https://bugs.freedesktop.org/attachment.cgi?id=115343&action=edit
Journald output radeon ring 0 stalled for more than XXX msecs
Hi,
when grading a video with the new GPU-accelerated kdenlive frameworks branch I
encounter a GPU lockup when I add three effects to a clip simultaneously (White
balance(GPU), Saturation(GPU) and Deconvolution sharpen(GPU) ) and seek the
timeline. I already filed a bugreport here
https://bugs.kde.org/show_bug.cgi?id=346184 but I think the problem lies in the
driver rather than the program because trying the same on Intel hardware slows
the system but there is no crash / lockup.
Fortunately I managed to recover the journal (is attached)
I hope you can help me. Thanks!
Hardware:
HD 6970 (Cayman XT)
Software:
Archlinux
Kernel 3.19.3
Mesa 10.5.4
Kdenlive stack:
kdenlive frameworks git (PKGBUILD attached)
mlt 0.9.6 (PKGBUILD attached)
movit 1.1.3 GPU effects package (PKGBUILD attached)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89995
GitLab Migration User <gitlab-migration(a)fdo.invalid> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |MOVED
Status|NEW |RESOLVED
--- Comment #3 from GitLab Migration User <gitlab-migration(a)fdo.invalid> ---
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.
You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/544.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=89619
Bug ID: 89619
Summary: Chrome crashes in 64 bit r600 driver while running
google maps
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: jrpstonecarver(a)gmail.com
QA Contact: dri-devel(a)lists.freedesktop.org
Sorry folks, I am new to this and will do my best.
I first reported this bug to Google. They got all the data here:
https://code.google.com/p/chromium/issues/detail?id=467821
and told me that this is a bug in the r600 driver.
Back in December I updated from 32 bit Ubuntu 12.04 to 64 bit Ubuntu 14.04 and
have had major stability issues with Chrome ever since, particularly while
using Google Maps.
This URL
https://www.google.com/maps/place/Los+Gatos,+CA+95033/@37.1893925,-121.9894…
was the first time I've managed to capture something that crashes chrome
reliably, however.
At their suggestion I tried running chrome with --disable-gpu and at least with
a simple test the problem went away.
I think these drivers are the default in Ubuntu now, but they seem to be
causing me a lot of grief.
You can pickup what Google got from the crash report Chrome sent to them from
the bug listed above.
And for the time being I will figure out how to run with --disable-gpu on all
the time to see if that avoids my issue.
Failing that I guess it's time to figure out how to go back to ATI's drivers.
If there is additional data I can provide somehow, I am happy to try. I'm no
wizard, but I will follow instructions and get whatever you need if possible.
Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.