Bug 58925

Summary:	compis/kwin crashes on nouveau due to msaa
Product:	Mesa	Reporter:	Vladimir <bobahu4>
Component:	Mesa core	Assignee:	mesa-dev
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	medium	CC:	maraeo, pedretti.fabio
Version:	git
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Vladimir 2013-01-01 21:25:44 UTC

Here compiz/kwin crashes when tries to run with weird assertion on msaa textures. 
Found that msaa can be swithced off with enviroment variable 

http://cgit.freedesktop.org/mesa/mesa/commit/?id=1d0bf69f831e138a05a282e59746f20141046fd6

but GALLIUM_MSAA = 0 doesnt help at all.

so I edited dri_fill_st_visual in dri_screen.c to disable msaa at all 

   if (mode->sampleBuffers) {
-      stvis->samples = mode->samples;
+      stvis->samples = 1;
   }

Now compiz/kwin work fine.

kernel 3.8-git from ubuntu daily kernel-ppa, ubuntu 12.10, nvidia gtx670

Comment 1 Vladimir 2013-01-01 21:28:17 UTC

Forgot the assertion

nvc0_miptree_init_ms_mode:177 - invalid nr_samples: 32
dri2.c:256:dri2_drawable_process_buffers: Assertion `drawable->msaa_textures[att]' failed.

Comment 2 Christoph Bumiller 2013-01-02 21:12:53 UTC

What's weird is, why does it try to create a texture with 32 samples ? 32x MSAA is not very common ...

Comment 3 Pali Rohár 2013-08-19 17:18:01 UTC

This problem is maybe related:
http://lists.freedesktop.org/archives/mesa-dev/2013-August/043505.html

Kwin from KDE4.8 not rendering properly after commit 35840ab189595b817fa8b1a1df8cc92474a7c38d:
st/dri: implement MSAA for GLX/DRI2 framebuffers
Author: Marek Olšák  2012-12-03 05:36:08
Committer: Marek Olšák  2012-12-07 14:19:29
Reviewed-by: Brian Paul

Comment 4 Emil Velikov 2014-09-22 18:48:21 UTC

Pretty sure that this one got resolved. Although as I cannot really point out to the commit that did it, and I've been using KDE for the last 6+ months I'll go with workforme :)

Feel free to reopen if it's still an issue with latest mesa/kwin.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.