similar to: [Bug 66809] Compiz segfault with latest mesa-git

https://bugs.freedesktop.org/show_bug.cgi?id=66809 --- Comment #6 from Roy <r.spliet at student.tudelft.nl> --- Eric: Could you install the debugging symbols (or, if you compiled it yourself, recompile with "-g" in your CFLAGS) for nouveau_dri and libdrm_nouveau please and reproduce your crash, regenerating this backtrace? I think it would be useful to see which function is trying

https://bugs.freedesktop.org/show_bug.cgi?id=66809 --- Comment #7 from Ilia Mirkin <imirkin at alum.mit.edu> --- My guess is that this is fixed in latest mesa-git. Can you test this out again? Unfortunately you did not provide an annotated stack trace as requested, but the commit you bisected to caused all sorts of problem for nouveau. It was changed by

https://bugs.freedesktop.org/show_bug.cgi?id=66809 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #8 from Ilia Mirkin <imirkin at

Can you not render to a texture buffer? That might not be supported by nv30 actually. On Tue, May 20, 2014 at 8:49 PM, Marek Ol??k <maraeo at gmail.com> wrote: > ARB_buffer_storage doesn't have anything to do with framebuffers. > > Marek > > On Wed, May 21, 2014 at 2:27 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> On Tue, May 20, 2014 at 6:20 PM, Marek

ARB_buffer_storage doesn't have anything to do with framebuffers. Marek On Wed, May 21, 2014 at 2:27 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Tue, May 20, 2014 at 6:20 PM, Marek Ol??k <maraeo at gmail.com> wrote: >> On Tue, May 20, 2014 at 11:04 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >>> On Tue, May 20, 2014 at 4:51 PM, Marek Ol??k

On Tue, May 20, 2014 at 6:20 PM, Marek Ol??k <maraeo at gmail.com> wrote: > On Tue, May 20, 2014 at 11:04 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> On Tue, May 20, 2014 at 4:51 PM, Marek Ol??k <maraeo at gmail.com> wrote: >>> On Tue, May 20, 2014 at 9:58 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >>>> Hello, >>>>

On Tue, May 20, 2014 at 11:04 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > On Tue, May 20, 2014 at 4:51 PM, Marek Ol??k <maraeo at gmail.com> wrote: >> On Tue, May 20, 2014 at 9:58 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >>> Hello, >>> >>> I attempted doing this a while back, before I really understood what >>> was going

Thanks, Marek. Could someone with commit access pick this up? Let me know if you'd like me to reformat/resend/create a git tree/whatever. -ilia On Sun, Oct 13, 2013 at 9:16 AM, Marek Ol??k <maraeo at gmail.com> wrote: > For the series: > > Reviewed-by: Marek Ol??k <marek.olsak at amd.com> > > Marek > > On Sun, Oct 13, 2013 at 3:43 AM, Ilia Mirkin

On Tue, May 20, 2014 at 4:51 PM, Marek Ol??k <maraeo at gmail.com> wrote: > On Tue, May 20, 2014 at 9:58 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> Hello, >> >> I attempted doing this a while back, before I really understood what >> was going on. I got some advice that went totally over my head, and I >> dropped the issue. I think I'm much

On 25 May 2015 at 08:11, Marek Olšák <maraeo at gmail.com> wrote: > It's the same on Radeon. There are 2x ClipOrCullDistance output > vectors and a mask saying it should clip or cull or do nothing. > > Marek > My thinking was gallium should have a single semantic and a mask in the shader definition maybe. though it doesn't solve the does nvidia do the right thing with

https://bugs.freedesktop.org/show_bug.cgi?id=94627 Marek Olšák <maraeo at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|RESOLVED |REOPENED QA Contact|nouveau at lists.freedesktop.o

On 27.05.2015 18:28, Marek Olšák wrote: > Another thing to consider is linking shaders that occur before the > rasterizer (e.g. any two shaders from VS->TCS->TES->GS). The maximum > number of written distances is still 8, but what happens if VS writes > 1x clip and 7x cull and GS reads 8x clip and no cull? i think this should be rejected anyway (in the glsl?!), constraining

Hi David, With the recent opcode changes, does compiz need anything in order to use the newer X server? I updated glproto to 1.4.8, then built Mesa 6.5.1 release, then compiled Xserver from git then built compiz git and I get a white screen, but compiz cube shows all white/shaded when I attempt to drag the cube around. I have AIGLX used instead of Xgl. I'm testing out Xorg '7.2'

On Mon, May 25, 2015 at 9:40 AM, Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> wrote: > > On 25.05.2015 07:17, Dave Airlie wrote: >> >> On 25 May 2015 at 08:11, Marek Olšák <maraeo at gmail.com> wrote: >>> >>> It's the same on Radeon. There are 2x ClipOrCullDistance output >>> vectors and a mask saying it should clip or cull

I have the same problem. I wrote this already here. I mean this problem is cause how is implemetated GL_texture_from_pixmap in new xserver, glproto and mesa and compiz is not ready yet.

Marek Olšák <maraeo at gmail.com> writes: > We can also save space by using the main repo for private branches, > e.g. my branches would be in refs/heads/mareko/*. It sounds like gitlab is not going to have this fixed very soon: https://gitlab.com/gitlab-org/gitlab-ce/issues/23029 I think this is an interesting idea. It would increase exposure of Mesa developers to what each other

For the series: Reviewed-by: Marek Ol??k <marek.olsak at amd.com> Marek On Sun, Oct 13, 2013 at 3:43 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: > ping > > On Fri, Oct 4, 2013 at 4:32 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >> This CAP will determine whether ARB_framebuffer_object can be enabled. >> The nv30 driver does not allow mixing

https://bugs.freedesktop.org/show_bug.cgi?id=28017 Summary: Compiz segfaults, backtrace log and patch included Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at

since compiz > 0.3.4; it segfault randomly at startup... So, sometime it works, sometime not :( No problem with 0.3.4. Running gdb, i 've got this: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1221977856 (LWP 19014)] 0x08068fb8 in compSetStringOption (option=0x816ea60, value=0xbfca2888) at option.c:154 154 if (strcmp (option->rest.s.string[i], s)

On Fri, Apr 22, 2016 at 9:23 AM, Hans de Goede <hdegoede at redhat.com> wrote: > Hi, > > On 22-04-16 09:08, Marek Olšák wrote: >> >> On Thu, Apr 21, 2016 at 7:04 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >>> >>> [+radeon folk] >>> >>> Marek, Nicolai, Bas - please have a look at the doc change and let us >>> know