dri-devel September 2019

dri-devel@lists.freedesktop.org

315 participants
2278 discussions

[Bug 105934] Gpu Hang after two compute dispatches on Intel HD 5500
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=105934 Bug ID: 105934 Summary: Gpu Hang after two compute dispatches on Intel HD 5500 Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/i915 Assignee: dri-devel(a)lists.freedesktop.org Reporter: mankeli(a)kolumbus.fi QA Contact: dri-devel(a)lists.freedesktop.org Running OpenGL program with two glDispatch() calls, causes gpu hang on HD Graphics 5500. Program basically does: if (1) { glUseProgram(computeprogram); glBindBufferBase(GL_SHADER_STORAGE_BUFFER, 1, ssbo_test); glDispatchCompute(256/4, 256/4, 256/2); glMemoryBarrier(GL_SHADER_STORAGE_BARRIER_BIT); } if (1) { glUseProgram(computeprogram); glBindBufferBase(GL_SHADER_STORAGE_BUFFER, 1, ssbo_test); glDispatchCompute(256/4, 256/4, 256/2); glMemoryBarrier(GL_SHADER_STORAGE_BARRIER_BIT); } .. and then simple one-triangle fullscreen pass to main framebuffer (0) using that SSBO. When both of those are enabled, my computer nearly hangs and dmesg reports: [127049.481163] drm/i915: Resetting chip after gpu hang. But if only one of those is enabled, everything is ok, compute dispatch takes 13ms and debug output renders on the screen. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 105257] GPU HANG: ecode 9:0:0x86dffffd, in Xorg, reason: Hang on render ring, action: reset
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=105257 Bug ID: 105257 Summary: GPU HANG: ecode 9:0:0x86dffffd, in Xorg, reason: Hang on render ring, action: reset Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/i915 Assignee: dri-devel(a)lists.freedesktop.org Reporter: ivanlevshin(a)yandex.ru QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 137611 --> https://bugs.freedesktop.org/attachment.cgi?id=137611&action=edit dmesg output with an error I'm in trouble with LibreOffice 6.0.1 during editing presentation in Impress: everything just stops responding (whole DE, I'm using KDE Plasma) then after some time I see that whole session reset, I have to start it again. I'm using X.org in OpenSUSE Tumbleweed on MSI GS40 6QE Phantom. I've seen this problem before (probably a yesr ago) but after some of updates it disappeared. Nor it happening again and again. To reproduce try to edit attached presentation, I cannot say what exactly needed to be done as I had spontaneous freezes but I can say that it will happens after 5-15 minutes you're working with it. mynote:/home/ivan # uname -a Linux mynote.levshin.site 4.15.4-1-default #1 SMP PREEMPT Sat Feb 17 09:02:00 UTC 2018 (7169cf1) x86_64 x86_64 x86_64 GNU/Linux Problem happening only in the time I'm editing some (not all) presentations in Impress, I haven't seen this problem with any other kind of workload. But I can say that it seems to be related with presentation with a lot of graphic objects embedded. At the same time it seems like X.org issue rather than LibreOffice issue as I see error message in dmesg output where exactly i915 mentioned and not a LO processes (like soffice). mynote:/home/ivan # rpm -qa|grep -i mesa Mesa-dri-nouveau-18.0.0-187.1.x86_64 Mesa-libGL-devel-18.0.0-187.1.x86_64 Mesa-libva-18.0.0-187.1.x86_64 Mesa-libEGL-devel-18.0.0-187.1.x86_64 Mesa-libGL1-18.0.0-187.1.x86_64 Mesa-gallium-18.0.0-187.1.x86_64 Mesa-dri-18.0.0-187.1.x86_64 Mesa-18.0.0-187.1.x86_64 Mesa-libEGL1-18.0.0-187.1.x86_64 Mesa-libglapi0-18.0.0-187.1.x86_64 mynote:/home/ivan # rpm -qa | grep -i xorg xorg-x11-server-wayland-1.19.6-3.1.x86_64 xorg-x11-essentials-7.6_1-16.4.noarch xorg-x11-libX11-ccache-7.6-20.5.noarch xorg-x11-fonts-core-7.6-32.3.noarch xorg-x11-fonts-7.6-32.3.noarch xorg-x11-server-1.19.6-3.1.x86_64 xorg-x11-driver-input-7.6_1-14.3.noarch xorg-x11-driver-video-7.6_1-17.1.x86_64 mynote:/home/ivan # rpm -qa | grep -i libreoffice libreoffice-6.0.1.1-1.3.x86_64 libreoffice-gtk3-6.0.1.1-1.3.x86_64 libreoffice-l10n-ru-6.0.1.1-1.3.noarch libreoffice-kde4-6.0.1.1-1.3.x86_64 libreoffice-l10n-en-6.0.1.1-1.3.noarch libreoffice-draw-6.0.1.1-1.3.x86_64 libreoffice-writer-6.0.1.1-1.3.x86_64 libreoffice-base-drivers-mysql-6.0.1.1-1.3.x86_64 libreoffice-writer-extensions-6.0.1.1-1.3.x86_64 libreoffice-calc-6.0.1.1-1.3.x86_64 libreoffice-share-linker-1-4.3.noarch libreoffice-branding-upstream-6.0.1.1-1.3.noarch libreoffice-mailmerge-6.0.1.1-1.3.x86_64 libreoffice-pyuno-6.0.1.1-1.3.x86_64 libreoffice-impress-6.0.1.1-1.3.x86_64 libreoffice-filters-optional-6.0.1.1-1.3.x86_64 libreoffice-gnome-6.0.1.1-1.3.x86_64 libreoffice-base-6.0.1.1-1.3.x86_64 libreofficekit-6.0.1.1-1.3.x86_64 libreoffice-icon-themes-6.0.1.1-1.3.noarch libreoffice-math-6.0.1.1-1.3.x86_64 libreoffice-calc-extensions-6.0.1.1-1.3.x86_64 -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 104599] corrupted desktop graphics with latest git intel driver
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104599 Bug ID: 104599 Summary: corrupted desktop graphics with latest git intel driver Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/i915 Assignee: dri-devel(a)lists.freedesktop.org Reporter: zebul666(a)hotmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136678 --> https://bugs.freedesktop.org/attachment.cgi?id=136678&action=edit photo of corrupted graphic on screen I have ubuntu 17.10 with an intel i3-3217U cpu/gpu and using the oibaf PPA repo. With latest following package: libgles2-mesa:amd64 (17.4~git1801070730.be144e~oibaf~a xserver-xorg-video-nouveau:amd64 (1:1.0.15+git1712110734.048baf~oibaf~a libdrm-nouveau2:amd64 (2.4.89+git1712180630.831036~oibaf~a libdrm-nouveau2:i386 (2.4.89+git1712180630.831036~oibaf~a xserver-xorg-video-amdgpu:amd64 (1.4.99+git1712271934.69e208~oibaf~a libegl1-mesa-dev:amd64 (17.4~git1801070730.be144e~oibaf~a libglapi-mesa:amd64 (17.4~git1801070730.be144e~oibaf~a libglapi-mesa:i386 (17.4~git1801070730.be144e~oibaf~a libxatracker2:amd64 (17.4~git1801070730.be144e~oibaf~a libegl1-mesa:amd64 (17.4~git1801070730.be144e~oibaf~a libgbm1:amd64 (17.4~git1801070730.be144e~oibaf~a libdrm-amdgpu1:amd64 (2.4.89+git1712180630.831036~oibaf~a libdrm-amdgpu1:i386 (2.4.89+git1712180630.831036~oibaf~a libllvm5.0:amd64 (1:5.0.1-1~oibaf~a libllvm5.0:i386 (1:5.0.1-1~oibaf~a xserver-xorg-video-intel:amd64 (2:2.99.917+git1712201935.708255~oibaf~a libwayland-egl1-mesa:amd64 (17.4~git1801070730.be144e~oibaf~a libdrm2:amd64 (2.4.89+git1712180630.831036~oibaf~a libdrm2:i386 (2.4.89+git1712180630.831036~oibaf~a xserver-xorg-video-ati:amd64 (1:7.10.99+git1712281934.1fe8ca~oibaf~a libgl1-mesa-dri:amd64 (17.4~git1801070730.be144e~oibaf~a libgl1-mesa-dri:i386 (17.4~git1801070730.be144e~oibaf~a libosmesa6:amd64 (17.4~git1801070730.be144e~oibaf~a libosmesa6:i386 (17.4~git1801070730.be144e~oibaf~a libgl1-mesa-glx:amd64 (17.4~git1801070730.be144e~oibaf~a libgl1-mesa-glx:i386 (17.4~git1801070730.be144e~oibaf~a xserver-xorg-video-radeon:amd64 (1:7.10.99+git1712281934.1fe8ca~oibaf~a libdrm-intel1:amd64 (2.4.89+git1712180630.831036~oibaf~a libdrm-intel1:i386 (2.4.89+git1712180630.831036~oibaf~a libdrm-radeon1:amd64 (2.4.89+git1712180630.831036~oibaf~a libdrm-radeon1:i386 (2.4.89+git1712180630.831036~oibaf~a mesa-vdpau-drivers:amd64 (17.4~git1801070730.be144e~oibaf~a mesa-vdpau-drivers:i386 (17.4~git1801070730.be144e~oibaf~a libdrm-dev:amd64 (2.4.89+git1712180630.831036~oibaf~a mesa-va-drivers:i386 (17.4~git1801070730.be144e~oibaf~a libdrm-common:amd64 (2.4.89+git1712180630.831036~oibaf~a I have a desktop screen corrupted like in the photo (screenshot did not wworked) Windows control did not work (wayland related ?) -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 104526] 0x00007fce563644fb in update_buffers (dri2_surf=dri2_surf@entry=0x55b5be7fc690) at drivers/dri2/platform_wayland.c:541
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104526 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #1 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/780. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 104520] Intermittent X crashes: GPU HANG: ecode 9:0:0x85dffffb, in Xorg [443], reason: Hang on rcs0, action: reset
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=104520 Bug ID: 104520 Summary: Intermittent X crashes: GPU HANG: ecode 9:0:0x85dffffb, in Xorg [443], reason: Hang on rcs0, action: reset Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/i915 Assignee: dri-devel(a)lists.freedesktop.org Reporter: awils_1(a)xsmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 136591 --> https://bugs.freedesktop.org/attachment.cgi?id=136591&action=edit GPU error dup. 1) startx 2) loading i3 and i3 scripts (loading an xterm and palemoon) intermittently crashes Result: GPU hangs, and eventually X crashes with this message in the dmesg. [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [443], reason: Hang on rcs0, action: reset [ 561.340148] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 561.340148] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 561.340148] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 561.340149] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 561.340149] [drm] GPU crash dump saved to /sys/class/drm/card0/error -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 102574] glDrawBuffer crashes in case of surfaceless context
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=102574 Bug ID: 102574 Summary: glDrawBuffer crashes in case of surfaceless context Product: Mesa Version: 17.1 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/i915 Assignee: dri-devel(a)lists.freedesktop.org Reporter: v.vogelhuber(a)digitalendoscopy.de QA Contact: dri-devel(a)lists.freedesktop.org I've created a surfaceless OpenGL context using the EGL_KHR_surfaceless_context extension together with eglGetPlatformDisplay/EGL_PLATFORM_GBM_MESA. In this scenario there seem to be no valid default framebuffer which is Ok, as I'm normally only render to FBOs with textures bound. Due to an error on my side I called glDrawBuffer with GL_FRONT_LEFT while no FBO was bound. This result in a crash in intel_buffers.c because in intelDrawBuffer() dri2InvalidateDrawable is called with a null pointer which is not checked in dri2InvalidateDrawable() or anywhere before. While the root cause for triggering the error is on my side, I think it may be better to raise an error instead of crashing. So I propose to add a check to brw->driContext->driDrawablePriv within intelDrawBuffer. Probably if the driDrawablePriv is nullptr one should not call intel_prepare_render either. Mesa 17.1 with Kernel 4.9.6 on Intel Apollo Lake GPU -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 102103] after switch to xserver-xorg-video-intel-native-modesetting libreoffice sidebar corrupted
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=102103 Bug ID: 102103 Summary: after switch to xserver-xorg-video-intel-native-modesetting libreoffice sidebar corrupted Product: Mesa Version: 17.1 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/i915 Assignee: dri-devel(a)lists.freedesktop.org Reporter: pieterkristensen(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 133375 --> https://bugs.freedesktop.org/attachment.cgi?id=133375&action=edit ugly sidebar libreoffice caused by xserver-xorg-video-intel-native-modesetting graphics dirver My machine is a Dell Lattitude e5500. As far as I can see it has a Mobile 4 Series Chipset Integrated Graphics Controller. I'm using kde Neon. After the introduction of the xserver-xorg-video-intel-native-modesetting driver I had a few (minor but irritating) issues. Most notably the sidebar of LibreOffice is ugly. I filed a bug at the document foundation and kde but they couldn't do anything with them. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 100612] [i915] [SNA] Graphics corruption with QupZilla
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=100612 GitLab Migration User <gitlab-migration(a)fdo.invalid> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |MOVED --- Comment #11 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/775. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 98964] Chromium complains about glXGetSyncValuesOML in 13.0.2
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=98964 Bug ID: 98964 Summary: Chromium complains about glXGetSyncValuesOML in 13.0.2 Product: Mesa Version: 13.0 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: zboszor(a)pr.hu QA Contact: dri-devel(a)lists.freedesktop.org Hi, I am running Chromium 52.0.2743.76 on Yocto with Mesa 13.0.2 / libdrm 2.4.73. It occasionally complains about this: [1347:1347:1202/032132:ERROR:sync_control_vsync_provider.cc(64)] glXGetSyncValuesOML should not return TRUE with a media stream counter of 0. Conformance bug? -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 98667] [i915] GPU HANG: ecode 6:0:0xf389fffc (Redie Beta 0.8.4)
by bugzilla-daemon＠freedesktop.org 18 Sep '19

18 Sep '19

https://bugs.freedesktop.org/show_bug.cgi?id=98667 Bug ID: 98667 Summary: [i915] GPU HANG: ecode 6:0:0xf389fffc (Redie Beta 0.8.4) Product: Mesa Version: 11.2 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/i915 Assignee: dri-devel(a)lists.freedesktop.org Reporter: xavier.l(a)magnax.ca QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 127882 --> https://bugs.freedesktop.org/attachment.cgi?id=127882&action=edit GPU crash dump GPU Hangs when running Redie Beta (https://rueckertbroductions.itch.io/redie). The game crashes with the following error message: > intel_do_flush_locked failed: Input/output error I am running Ubuntu 16.04.1 (kernel 4.4.0-47-generic). -- You are receiving this mail because: You are the assignee for the bug.

1 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel September 2019