https://bugs.freedesktop.org/show_bug.cgi?id=106775
Bug ID: 106775
Summary: continuous error "write-fence failed" for etnaviv
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: vishwanath.chandapur(a)beckman.com
Created attachment 139957
--&…
[View More]gt; https://bugs.freedesktop.org/attachment.cgi?id=139957&action=edit
Error log
Hi,
I am trying to get chrome browser with wayland-ozone support.
We are able to get wayland terminal.But when we launch chrome its not working.
libdrm version: 2.4.89
Mesa Driver: 17.1.7
Linux Kernel Version:4.14.39
Gpu: etna_gpu
Below is error log:
[E] wait-fence failed! -16 (Device or resource busy) (etna_pipe_wait_ns:55)
[E] wait-fence failed! -16 (Device or resource busy) (etna_pipe_wait_ns:55)
[E] wait-fence failed! -16 (Device or resource busy) (etna_pipe_wait_ns:55)
[E] wait-fence failed! -16 (Device or resource busy) (etna_pipe_wait_ns:55)
[E] wait-fence failed! -16 (Device or resource busy) (etna_pipe_wait_ns:55)
[E] wait-fence failed! -16 (Device or resource busy) (etna_pipe_wait_ns:55)
[E] wait-fence failed! -16 (Device or resource busy) (etna_pipe_wait_ns:55)
[E] wait-fence failed! -16 (Device or resource busy) (etna_pipe_wait_ns:55)
[E] wait-fence failed! -16 (Device or resource busy) (etna_pipe_wait_ns:55)
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=105142
Bug ID: 105142
Summary: Texture operations hang indefinitely
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: libdrm
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: pawel.veselov(a)gmail.com
Created attachment 137413
--> …
[View More]https://bugs.freedesktop.org/attachment.cgi?id=137413&action=edit
dmesg output
Reproducible running compiz on mate, on FC27.
I can reproduce this fairly consistently, if enabling emerald window
decorations, though it can fail with GTK+ decorations as well. Using Alt-Tab to
switch between windows triggers this problem. Only the process is hanging,
SIGKILL is needed to restart the process.
Stack trace attached in stack.txt
Library version list attached in vers.txt
Full dmesg output attached in dmesg.txt
I'm fairly certain I've miscategorized this bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=100077
Bug ID: 100077
Summary: libdrm atomic_add_unless() may reverse return value
meaning
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: BSD (Others)
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: davshao(a)gmail.…
[View More]com
atomic_add_unless() in libdrm xf86atomic.h may reverse the meaning
of its return value.
Linux kernel documentation seems to indicate something like:
"Returns non-zero if @v was not @u, and zero otherwise."
A simple inverting the meaning of libdrm's return value
allowed glxgears to properly function for a hacked version
of pkgsrc on DragonFly 4.7-DEVELOPMENT on an Intel IvyBridge
integrated graphics machine. glxgears was already properly
functioning on the same machine for NetBSD current, NetBSD
using its own atomic operations declared in its sys/atomic.h
header.
A one line (character) fix is of the form:
--- xf86atomic.h.orig 2015-09-22 04:34:51.000000000 +0000
+++ xf86atomic.h
@@ -111,7 +111,7 @@ static inline int atomic_add_unless(atom
c = atomic_read(v);
while (c != unless && (old = atomic_cmpxchg(v, c, c + add)) != c)
c = old;
- return c == unless;
+ return c != unless;
}
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=99581
Bug ID: 99581
Summary: plasmashell segfault in nouveau_dri.so
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: medium
Component: libdrm
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: ken20001(a)ukr.net
Created attachment 129201
--> …
[View More]https://bugs.freedesktop.org/attachment.cgi?id=129201&action=edit
Xorg log file
After logging in in KDE session I see only desktop wallpaper and nothing more.
Nothing happens later: looks like system is stopped. But in VT I found that
plasmashell is crashed and that was the reason of that unusual behavior in my
system:
~$ dmesg | grep -i error
[ 80.251695] plasmashell[1971]: segfault at 0 ip 00007fdb276e07c6 sp
00007fff907d9570 error 4 in nouveau_dri.so[7fdb27181000+a3e000]
$ lspci | grep -i vga
04:00.0 VGA compatible controller: NVIDIA Corporation NV43 [GeForce 6600 GT]
(rev a2)
$ uname -a
Linux desktop 4.9.6-040906-generic #201701260330 SMP Thu Jan 26 08:32:10 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
I checked on Kubuntu 16.04.1LTS with distro's Mesa and with the latest git from
oibaf PPA.
plasma-desktop: 5.8.5-0ubuntu1~ubuntu16.04~ppa1
xserver-xorg-video-nouveau: 1.0.13+git1701262001.1516d3~gd~x / 1.0.12-1build2
libdrm-nouveau2: 2.4.75+git1701280630.d4b834~gd~x / 2.4.67-1 / 2.4.68-1~ppa
OpenGL version string: 2.1 Mesa 17.1.0-devel / Mesa 11.2.0
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=94951
Bug ID: 94951
Summary: [BXT] Not all primary planes and sprites are supported
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: jairo.daniel.miramontes.caton(a)intel.com
Created attachment …
[View More]122970
--> https://bugs.freedesktop.org/attachment.cgi?id=122970&action=edit
dmesg.log
While executing APL features on beta testing we found the following issue.
The following test is failing:
"Check primary plane and sprite planes supported"
Description:
"Support common YUV and RGB formats in sprite and primary planes"
Steps to reproduce:
1. clone drm sources from git://anongit.freedesktop.org/mesa/drm
2. Build drm with ./autogen.sh & make
3. go to drm/tests/modetest
4. Execute modetest and look at the list of plane formats: ./modetest
Expected result:
You should see the following formats: RGB565, XRGB8888, XBGR8888, ARGB8888,
ABGR8888, , XBGR2101010, YUYV, YVYU, UYVY, VYUY, RGB565,
ABGR8888, ARGB8888, XBGR8888, XRGB8888, YUYV, YVYU, UYVY, VYUY,
Actual result:
formats: RG16 AB24 AR24 XB24 XR24 YUYV YVYU UYVY VYUY
Configuration:
++ Platform : BXT-P
++ Motherboard model : Broxton P
++ Motherboard type : NOTEBOOK Hand Held
++ Motherboard manufacturer : Intel Corp.
++ CPU family : Other
++ CPU information : 06/5c
++ GPU Card : Intel Corporation Device 5a84 (rev
03) (prog-if 00 [VGA controller])
++ Memory ram : 8 GB
++ Maximum memory ram allowed : 16 GB
++ Display resolution :
++ CPU's number : 4
++ Hard drive capacity : 120 GB
++ Kernel version : 4.6.0-rc3-nightly+
++ Linux distribution : Ubuntu 15.10
++ Architecture : 64-bit
++ xf86-video-intel version : 2.99.917
++ Xorg-Xserver version : 1.17.2
++ DRM version : 2.4.64
++ Cairo version : 1.14.2
++ Intel GPU Tools version : Tag
[intel-gpu-tools-1.14-133-gc89e8db] / Commit [c89e8db]
++ Kernel driver in use : i915
++ Hardware acceleration :
++ Bios revision : 131.10
++ KSC revision : 1.12
Find attached the output of the test and dmesg.log
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=86043
Bug ID: 86043
Summary: Optimus issue with libdrm 2.4.58
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: libdrm
Assignee: dri-devel(a)lists.freedesktop.org
Reporter: jljusten(a)gmail.com
Users with optimus systems are reporting that
many games fail to …
[View More]run in libdrm-intel is upgraded
from 2.4.56 to 2.4.58. (And, downgrading to 2.4.56
fixes the issue.
Steam bug:
https://github.com/ValveSoftware/steam-for-linux/issues/3506
Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768045
I don't have hardware to confirm this issue.
I notice that between 2.4.56 and 2.4.58 libdrm changed
some symbol visibility settings.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=77204
Priority: medium
Bug ID: 77204
Assignee: dri-devel(a)lists.freedesktop.org
Summary: make fails due to wrong file names in man
Severity: normal
Classification: Unclassified
OS: All
Reporter: tamas.haraszti(a)uni-heidelberg.de
Hardware: Other
Status: NEW
Version: XOrg CVS
Component: libdrm
Product: DRI
make …
[View More]fails with:
/bin/sed: can't read drm-mm.7: No such file or directory
looking into the man folder I can find:
Makefile drm-kms.7 drm-memory.xml drmAvailable.3 drmHandleEvent.xml
drm\-gem.7
Makefile.am drm-kms.xml drm.7 drmAvailable.xml
drmModeGetResources.3 drm\-mm.7
Makefile.in drm-memory.7 drm.xml drmHandleEvent.3
drmModeGetResources.xml drm\-ttm.7
Thus all MANPAGE_ALIASES contain an extra \.
Renaming the files allows the make to proceed.
System: gentoo linux, newest automake, cmake, bash...
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=72425
Priority: medium
Bug ID: 72425
Assignee: dri-devel(a)lists.freedesktop.org
Summary: divide by zero error in radeon_surface.c when opening
chrome with WebGL enabled
Severity: normal
Classification: Unclassified
OS: All
Reporter: crwulff(a)gmail.com
Hardware: Other
Status: NEW
Version: unspecified
…
[View More]Component: libdrm
Product: DRI
Created attachment 90384
--> https://bugs.freedesktop.org/attachment.cgi?id=90384&action=edit
Fix divide by zero in radeon_surface
Passing a tile_split of zero to eg_surface_init_2d causes a divide by zero
error. Launching chromium with WebGL enabled on a AMD Llano (A8-3850) exhibits
this behavior and webgl then fails to work. The attached patch fixes the
problem and allows WebGL to work in chrome on this platform.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=66332
Priority: medium
Bug ID: 66332
Assignee: dri-devel(a)lists.freedesktop.org
Summary: drmHandleEvent returns 0 on read() failure
Severity: normal
Classification: Unclassified
OS: All
Reporter: mgold(a)qnx.com
Hardware: All
Status: NEW
Version: XOrg CVS
Component: libdrm
Product: DRI
drmHandleEvent contains this …
[View More]code:
len = read(fd, buffer, sizeof buffer);
if (len == 0)
return 0;
if (len < sizeof *e)
return -1;
In the (len < sizeof *e) check, len gets promoted to size_t (which is
unsigned); so when len is negative "return -1" won't be executed. Instead, the
function continues to the end and returns 0. (The documentation states
drmHandleEvent will return -1 if the read fails.)
If there's an error like EBADF, the caller won't detect it and might end up
busy-waiting. Rewriting the condition as (len < (int)(sizeof *e)) will fix
this.
--
You are receiving this mail because:
You are the assignee for the bug.
[View Less]