[FFE] mesa 10.3

Bug #1364003 reported by Maarten Lankhorst
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
Fix Released
High
Maarten Lankhorst

Bug Description

Impact to ubuntu:
    Proper support for llvm 3.5 without crashing llvmpipe when running tests on i386.
    kms swrast was requested, will be available in 10.3.
    Build fixes to support a gallium megablob, reducing size even further.

New features
    GL_ARB_ES3_compatibility on nv50, nvc0, r600, radeonsi, softpipe, llvmpipe
    GL_ARB_clear_texture on i965
    GL_ARB_compressed_texture_pixel_storage on all drivers
    GL_ARB_conditional_render_inverted on i965, nvc0, softpipe, llvmpipe
    GL_ARB_derivative_control on i965, nv50, nvc0, r600
    GL_ARB_draw_indirect on nvc0, radeonsi
    GL_ARB_explicit_uniform_location (all drivers that support GLSL)
    GL_ARB_fragment_layer_viewport on nv50, nvc0, llvmpipe, r600
    GL_ARB_gpu_shader5 on i965/gen7, nvc0
    GL_ARB_multi_draw_indirect on nvc0, radeonsi
    GL_ARB_sample_shading on radeonsi
    GL_ARB_seamless_cubemap_per_texture on i965, llvmpipe, nvc0, r600, radeonsi, softpipe
    GL_ARB_stencil_texturing on nv50, nvc0, r600, and radeonsi
    GL_ARB_texture_barrier on nv50, nvc0, r300, r600, radeonsi
    GL_ARB_texture_compression_bptc on i965/gen7+, nvc0, r600/evergreen+, radeonsi
    GL_ARB_texture_cube_map_array on radeonsi
    GL_ARB_texture_gather on r600, radeonsi
    GL_ARB_texture_query_levels on nv50, nvc0, llvmpipe, r600, radeonsi, softpipe
    GL_ARB_texture_query_lod on r600, radeonsi
    GL_ARB_viewport_array on nvc0
    GL_AMD_vertex_shader_viewport_index on i965/gen7+, r600
    GL_OES_compressed_ETC1_RGB8_texture on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe
    GLX_MESA_query_renderer on nv30, nv50, nvc0, r300, r600, radeonsi, softpipe, llvmpipe
    A new software rasterizer driver (kms_swrast_dri.so) that works with DRM drivers that don't have a full-fledged GEM (such as qxl or simpledrm)
    Distribute the Khronos GL/glcorearb.h header file.

Changes
    Removed support for the GL_ATI_envmap_bumpmap extension
    The hacky --enable-32/64-bit is no longer available in configure. To build 32/64 bit mesa refer to the default method recommended by your distribution

Revision history for this message
Matthias Klose (doko) wrote :

updating mesa allows us to demote llvm 3.4, so +1 from me on this

Changed in mesa (Ubuntu):
importance: Undecided → High
Revision history for this message
Jonathan Riddell (jr) wrote :

How can I test this?

Revision history for this message
Jonathan Riddell (jr) wrote :

Got it in ppa:canonical-x/x-staging

Revision history for this message
Adam Conrad (adconrad) wrote :

+1 from me, please also pull http://lists.freedesktop.org/archives/mesa-dev/2014-August/064711.html if you haven't already.

Might want to wait on Riddell's okay, if he has time to test, but if not, I wouldn't block on it either, as you did some basic KDE testing yourself.

Revision history for this message
Jonathan Riddell (jr) wrote :

I'm against this I'm afraid, we have a history of these late mesa updates causing problems. We can't adequately test it in both KWin 4 and KWin 5 on all the graphics cards in the time left before the release. Upstream says he has not tested mesa 10.3 and won't be able to fix problems in KWin 4.

Revision history for this message
Jonathan Riddell (jr) wrote :

Testing it just now some problems have occured which I can't definately say are due to the update but I haven't seem them before. Windows stopped accepting keys when I did the dist-upgrade to the new packages. After a reboot the Window Manager Settings -> Desktop Effects dialog appears frozen when I interact with it. I started dolphin and it didn't accept mouse input or allow me to resize it. More testing is needed.

Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 1364003] Re: [FFE] mesa 10.3

On Monday, September 22, 2014 16:38:20 you wrote:
> Testing it just now some problems have occured which I can't definately
> say are due to the update but I haven't seem them before. Windows
> stopped accepting keys when I did the dist-upgrade to the new packages.
> After a reboot the Window Manager Settings -> Desktop Effects dialog
> appears frozen when I interact with it. I started dolphin and it didn't
> accept mouse input or allow me to resize it. More testing is needed.

I was tempted to suggest that if someone volunteered to deal with the kwin
issues, it'd be OK, but given the problems you've had, I think it's just too
late in the cycle.

Revision history for this message
Adam Conrad (adconrad) wrote :

Rescinding my +1 unless the above can get heavier testing on a few different cards, as per IRC.

Revision history for this message
Jonathan Riddell (jr) wrote :

09:25 < Riddell> I've made a testing matrix, will try to fill it in during beta 2 tests today and tomorrow
                 https://docs.google.com/spreadsheets/d/1KchGJ6d50Knx9hGS7MvSRKhId-yBMOpPpUoihKHyJm0/edit?usp=sharing

Revision history for this message
Andreas Pokorny (andreas-pokorny) wrote :

Which intel driver is meant in the spreadsheet?

Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

No idea, but it seems those bugs are probably just bugs in kde5, since I don't hit them with 10.3 on amd64/i386, but I can reproduce something similar with the kde5 ppa, without updating mesa.

Revision history for this message
Jonathan Riddell (jr) wrote :

I tested today with Plasma 4 and Plasma 5 images and the problems I found seem to be unrelated to the mesa update. I also tested on a machine with Plasma 4 and AMD hardware and the mesa update also seemed to go smooth. I'd still rather this did not happen due to unforseen issues we've had from similar updates in the past but I won't block it, +0

Revision history for this message
Scott Kitterman (kitterman) wrote :

On Tuesday, September 23, 2014 14:59:33 you wrote:
> I tested today with Plasma 4 and Plasma 5 images and the problems I
> found seem to be unrelated to the mesa update. I also tested on a
> machine with Plasma 4 and AMD hardware and the mesa update also seemed
> to go smooth. I'd still rather this did not happen due to unforseen
> issues we've had from similar updates in the past but I won't block it,
> +0

Since kwin upstream has told us they won't support kwin4 with mesa 10.3, is
there anyone who could fix problems if they occur after this lands?

Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

Depending on the problems I might be able to fix them myself. I would also like to note that at least with nouveau I haven't encountered any yet.

Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

I've done some more testing just in case, and it looks like there are no regressions on llvmpipe on 32-bits or 64-bits, only new tests passing.

I've also done a comparison of 32-bits llvmpipe against 64-bits, and it looks like there's probably a small issue on the teximage-colors with GL_UNSIGNED_INT. This is not a regression though, it was already the case in 10.2.6.

Changed in mesa (Ubuntu):
status: New → Fix Committed
Revision history for this message
Loïc Minier (lool) wrote :

This broke autopkgtests of some packages; see bug #1374131.

This is likely to be removed from utopic-proposed for now to allow other packages to keep transitioning to utopic.

Revision history for this message
Scott Kitterman (kitterman) wrote :

On Friday, September 26, 2014 12:35:59 you wrote:
> This broke autopkgtests of some packages; see bug #1374131.

Doesn't this pretty well establish there's undue risk with going forward with
10.3 this late in the cycle? Also, I don't see where the FFe was approved, so
I'm not sure why this got uploaded?

Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :

Hey,

It is my opinion the autopkgtests themselves were broken, but I've added explicit depends in mesa to always force libgl1-mesa-dri to be installed when libgl1-mesa-dri, libegl1-mesa or libgbm1 are installed.

This allows the tests to run correctly again, and presumably fixes the armhf tests too.

~Maarten

Revision history for this message
Maarten Lankhorst (mlankhorst) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mesa - 10.3.0-0ubuntu2

---------------
mesa (10.3.0-0ubuntu2) utopic; urgency=medium

  * Add depends on libgl1-mesa-dri to some packages.
    - libgl1-mesa-glx, libegl1-mesa and libgbm1 depend on the dri
      files to be installed, even for swrast support. (LP: #1374131)

mesa (10.3.0-0ubuntu1) utopic; urgency=medium

  * New upstream release. (LP: #1364003)
  * Merge from released debian-experimental.

mesa (10.3.0-1) UNRELEASED; urgency=medium

  * New upstream release.
  * Remove upstreamed patch.
    - 01_gallium-util-add-missing-u_debug-include.patch
  * Remove gallium-pipe, no longer built.

mesa (10.3.0~rc3-3) experimental; urgency=medium

  [ Andreas Boll ]
  * Bump llvm-3.5-dev and libclang-3.5-dev to 1:3.5-1, should fix FTBFS on
    kfreebsd-*.
  * Bump compat to v9 for changed dh_strip behavior:
    - dh_strip puts separated debug symbols in a location based on their
      build-id (Closes: #755921).
  * Drop redundant libegl1-mesa-drivers.install.linux.in.

  [ Dima Kogan ]
  * All -dev packages are now Multi-Arch: same (Closes: #689088, #678040).

  [ Julien Cristau ]
  * Upload clean source without partial Ubuntu alternatives patches (closes: #761678)

mesa (10.3.0~rc3-2) experimental; urgency=medium

  [ Andreas Boll ]
  * Add 01_gallium-util-add-missing-u_debug-include.patch, fixes FTBFS on
    big endian archs.
  * Enable --with-egl-platforms=drm on kfreebsd-any, should fix FTBFS.
  * Don't try to install vdpau hardlinks on hurd, should fix FTBFS.

  [ Fabio Pedretti ]
  * debian/rules: minor cleanup.

mesa (10.3.0~rc3-1) experimental; urgency=medium

  [ Maarten Lankhorst ]
  * Build with llvm 3.5.
  * New upstream release.
  * Remove mention of tdfx.

  [ Timo Aaltonen ]
  * mesa-common-dev: Add glcorearb.h.
  * not-installed: Skip libglapi.so.
 -- Maarten Lankhorst <email address hidden> Mon, 29 Sep 2014 14:33:23 +0200

Changed in mesa (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.