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.
https://bugs.freedesktop.org/show_bug.cgi?id=73127
Priority: medium
Bug ID: 73127
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [r600g] Possible memory leak when playing WoW with
CAICOS
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: rankincj(a)googlemail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 91298
--> https://bugs.freedesktop.org/attachment.cgi?id=91298&action=edit
Message log showing page allocation failure
I finally managed to build some libdrm-2.4.50 RPMs for Fedora 19 so that I
could compile a recent -git snapshot. The HEAD commit was:
author Alex Deucher <alexander.deucher(a)amd.com> 2013-12-24 20:22:31 (GMT)
committer Alex Deucher <alexander.deucher(a)amd.com> 2013-12-24 20:22:31
(GMT)
commit e2d53fac1c5b18f5c9e95d39d4e2be4703b0b363 (patch) (side-by-side diff)
tree 51caa6afa79db9a733198f6bf5c6224c023fea2f
parent 35a34143026785e015adb906756651807de89bde (diff)
download mesa-e2d53fac1c5b18f5c9e95d39d4e2be4703b0b363.zip
mesa-e2d53fac1c5b18f5c9e95d39d4e2be4703b0b363.tar.gz
r600g: fix SUMO2 pci id
0x9649 is sumo2, not sumo.
This resulted in an eventual crash of WoW and Minecraft, apparently due to
memory exhaustion. (The messages log is attached).
Reverting to my previous build seemed to fix things:
author Marek Olšák <marek.olsak(a)amd.com> 2013-11-20 00:47:36 (GMT)
committer Marek Olšák <marek.olsak(a)amd.com> 2013-11-23 00:54:57 (GMT)
commit a3969aa125c8f61b093a5f5f69e8265a131051d0 (patch) (side-by-side diff)
tree aaa0b9350231b29d9dd51c49c5c86e1fe78a6096
parent 46cf80fb366cb14827724a7fea004e81400cc602 (diff)
download mesa-a3969aa125c8f61b093a5f5f69e8265a131051d0.zip
mesa-a3969aa125c8f61b093a5f5f69e8265a131051d0.tar.gz
mesa: initialize gl_renderbuffer::Depth in core
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=73088
Priority: medium
Bug ID: 73088
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Juniper (6770): Gone Home / Unigine Heaven 4.0 lock up
system after several minutes of use
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: appletorch(a)hotmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
Created attachment 91246
--> https://bugs.freedesktop.org/attachment.cgi?id=91246&action=edit
Xorg.log
Gone Home and Unigine Heaven 4.0 lock up my system after a few minutes of
operation when using this ppa:
https://launchpad.net/~oibaf/+archive/graphics-drivers/
When using mesa 9.2.1 provided in ubuntu 13.10 this does not occur with Gone
Home. Same lock up issue happens when using ubuntu 14.04 development with mesa
10.0.1. In all cases I had radeon.audio=1, radeon.dpm=1, and R600_DEBUG=sb.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=72877
GitLab Migration User <gitlab-migration(a)fdo.invalid> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #23 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/477.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=72732
Priority: medium
Bug ID: 72732
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Missing NULL check; radeon_drm_winsys.c
Severity: normal
Classification: Unclassified
OS: All
Reporter: freedesktop(a)treblig.org
Hardware: Other
Status: NEW
Version: unspecified
Component: Drivers/DRI/R600
Product: Mesa
I can sometime trigger a seg in do_winsys_init at radeon_drm_winsys.c on my
HD4350
There seems to be a simple missing NULL check:
214 version = drmGetVersion(ws->fd);
215 if (version->version_major != 2 ||
216 version->version_minor < 3) {
All the other users of drmGetVersion do a NULL check, so I suggest adding:
if (!version) {
fprintf(stderr,"%s: drmGetVersion NULL - bad fd (%d)?\n", __FUNCTION__,
ws->fd);
return FALSE;
}
I believe this to be part of the reason for:
https://bugzilla.redhat.com/show_bug.cgi?id=993463
why drmGetVersion is failing is a different matter (probably a bad fd at that
point - but why?) , but at least the NULL check would stop the seg.
Dave
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=72699
Priority: medium
Bug ID: 72699
Assignee: dri-devel(a)lists.freedesktop.org
Summary: [llvm] Europa Universalis 4 closes its window and eats
all memory while loading
Severity: normal
Classification: Unclassified
OS: All
Reporter: nikoamia(a)gmail.com
Hardware: Other
Status: NEW
Version: git
Component: Drivers/DRI/R600
Product: Mesa
Hello,
While using new llvm from svn (rev. 197173) Europa Universalis 4 closes its
window on "Loading Graphics" stage but retains as process and eats up all
memory and swap, so it is needed to kill it manually. Problem disappears after
reverting to rev. 196300.
Kernel: 3.12.5, was also tested on earlier
Mesa: git 60139.40070e7
Video: Mobility Radeon HD 5650M
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=72387
Priority: medium
Bug ID: 72387
Assignee: dri-devel(a)lists.freedesktop.org
Summary: Tearing at one specific part of the screen on CAYMAN
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: v10lator(a)myway.de
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Drivers/Gallium/r600
Product: Mesa
I see this with games as well as on my (composited) desktop when scrolling very
fast in firefox, for example.
Let me try to explain:
If you would cut the screen horizontally in 3 pieces the line between the
middle and the down piece is where the tearing appears. It appears even with
vsync.
I tried to capture it with gtk-rekordmydesktop but for some reason the video is
tear-free.
--
You are receiving this mail because:
You are the assignee for the bug.