Bug 100189

mpv only crashes when fullscreen on start is activated in mpv.conf (fs=yes).

blender crashes also with segfault:

# Blender 2.78 (sub 0), Commit date: 2017-02-24 14:33, Hash e92f2352830

	# backtrace
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(BLI_system_backtrace+0x1d) [0x19aad1d]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender() [0x104e2e6]
	/lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x7f3f49d924b0]
	/usr/lib/x86_64-linux-gnu/dri/i915_dri.so(+0x4e46e8) [0x7f3f352dc6e8]
	/usr/lib/x86_64-linux-gnu/dri/i915_dri.so(+0x4e4c65) [0x7f3f352dcc65]
	/usr/lib/x86_64-linux-gnu/dri/i915_dri.so(+0x4d68ed) [0x7f3f352ce8ed]
	/usr/lib/x86_64-linux-gnu/dri/i915_dri.so(+0x1df184) [0x7f3f34fd7184]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(_ZN13GHOST_Context11initClearGLEv+0x25) [0x19cd185]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(_ZN16GHOST_ContextGLX24initializeDrawingContextEv+0x270) [0x19cc490]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(_ZN15GHOST_WindowX1117newDrawingContextE25GHOST_TDrawingContextType+0x5d) [0x19cb9cd]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(_ZN12GHOST_Window21setDrawingContextTypeE25GHOST_TDrawingContextType+0x8e) [0x19ce33e]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(_ZN15GHOST_WindowX11C1EP15GHOST_SystemX11P9_XDisplayRK10STR_Stringiijj18GHOST_TWindowStatei25GHOST_TDrawingContextTypebbbtb+0x5b3) [0x19cadb3]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(_ZN15GHOST_SystemX1112createWindowERK10STR_Stringiijj18GHOST_TWindowState25GHOST_TDrawingContextType16GHOST_GLSettingsbi+0xb1) [0x19c8d71]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(GHOST_CreateWindow+0x62) [0x19c40b2]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(wm_window_ghostwindows_ensure+0x1e1) [0x106dbf1]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(WM_check+0x41) [0x104eb31]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(wm_homefile_read+0x12c) [0x105b4fc]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(WM_init+0xff) [0x105d48f]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender(main+0x264) [0xfed4a4]
	/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f3f49d7d830]
	/home/javi/Downloads/blender-2.78c-linux-glibc219-x86_64/blender() [0x104b278]

Hi Javi, I don't think we have many devs looking at the i915 driver.

If you can track down the commit that introduced the regression (considering it is one) or write a simple test program that will be appreciated.

Hi Emil.
The upgrade that initiated the problem was (17.0~git1701100730.17eac3~gd~x, 17.1~git1702040730.106a51~gd~x), something happened between 170110 and 170204.

About the test program or tracking the exact commit, not shure how to do it. Can you point me to info on how to?

Thanks.

"LIBGL_ALWAYS_SOFTWARE=1 blender" works. Blender runs without errors. Also Mpv, glmark2 and glxgears.

(In reply to Javi Ballester Tomás from comment #3)
> Hi Emil.
> The upgrade that initiated the problem was (17.0~git1701100730.17eac3~gd~x,
> 17.1~git1702040730.106a51~gd~x), something happened between 170110 and
> 170204.
> 
Perfect - what you're looking for is "how to use git bisect". There's dozens of sources out there - from `git help bisect' (in the command line) to the Wine example [1]. In case you're wondering - Mesa source tree is located at [2]

Note that you will need to rebuild and test mesa ~10 times. Make sure to use exact same build (configure) flags as your distro.

[1] https://wiki.winehq.org/Regression_Testing#Running_the_bisection
[2] https://cgit.freedesktop.org/mesa/mesa

(In reply to Javi Ballester Tomás from comment #4)
> "LIBGL_ALWAYS_SOFTWARE=1 blender" works. Blender runs without errors. Also
> Mpv, glmark2 and glxgears.

This is very good step - it tells us that the software rasteriser is working fine.
I.e. the variable 'disables' the GPU driver and makes the CPU do all the heavy lifting.

Almost forgot - if you don't want to overwrite your system mesa simply do
$ git bisect...
$ configure ...
$ make
$ export LIBGL_DRIVERS_PATH=`pwd`/lib
$ export LIBGL_DEBUG=verbose
$ ... app to test ... 
# ensure that the i915_dri.so from the above location is used

The result of 'git bisect':

e027935a795ecf546f3e4abcc25655766f9615ac is the first bad commit
commit e027935a795ecf546f3e4abcc25655766f9615ac
Author: Marek Olšák <marek.olsak@amd.com>
Date:   Wed Feb 22 19:59:27 2017 +0100

    st/mesa: don't update unrelated states in non-draw calls such as Clear
    
    If a VAO isn't bound and u_vbuf isn't enabled because of the Core profile,
    we'll get user vertex buffers in drivers if we update vertex buffers
    in glClear. So don't do that.
    
    This fixes a regression since disabling u_vbuf for Core profiles.
    
    Reviewed-by: Brian Paul <brianp@vmware.com>

:040000 040000 7843bc274cb97b72ebd0ba00906ba3baeecf0658 97a362bcd14da53ec9cfa940b3612d77e54be72d M      src

Is this the gallium driver?

Created attachment 130508 [details]
output of glxinfo

The "Gallium 0.4 on i915 (chipset: Pineview M)" is the one giving the segfault. 
The "Mesa DRI Intel(R) Pineview M" works.

Additional info, not related to this bug, I think:

The two works with some glitches in Blender. Gallium, the working ones, with black windows or past state window, specially when rendering, that disappears when some action is done in the part of the application that shows this behavior. DRI with colorful semitransparent triangles in the corners of blender windows, these doesn't disappears, but changes when scrolling.

No glitches in any of the two with "LIBGL_ALWAYS_SOFTWARE=1".

I attach the output of "glxinfo | grep OpenGL" for both, some errors in the gallium one.

(In reply to Marek Olšák from comment #8)
> Is this the gallium driver?

Yes.

The i915 gallium driver is unmaintained and not even supported by its manufacturer. This bug report starts its deprecation period. If the driver remains in a broken state for a while, it will be removed from Mesa. Feel free to ignore this bug. Cheers. :)

Nicely spotted Marek. Changing the component to gallium/i915g so that Stéphane can find if a bit easier.

I also have a problem with these Gallium drivers. Is there a way to fix them, or find an old unbroken version?

I actually need this.

I did a git bisect too, and I get the same bad commit as in comment 7.

I'm trying to build Mesa with Gallium for Intel/i915. But recent versions of Mesa make my web browser Falkon crash at startup.

-- 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/669.