[Ubuntu-x-swat] [Bug 947544]

2013-06-19 Thread Ross Schlaikjer
Created attachment 80882
apitrace dump for glxgears

I am seeing what appears to be the same error. It is reproducible 100%
of the time with glxgears.

I ran glxgears in apitrace (causing a segfault). Attatched is the raw
apitrace.

Is there any other data that I can provide that would be useful?

Hardware is an Intel i7-2860QM.

The segfault is visible in the apitrace replay.
$ apitrace replay glxgears.trace
apitrace: warning: caught signal 11
1357: error: caught an unhandled exception
apitrace: info: taking default action for signal 11

gdb output for glxgears:

Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.

Program received signal SIGSEGV, Segmentation fault.
brw_update_renderbuffer_surface (brw=0x77fae040, rb=0x61aa30, unit=0)
at brw_wm_surface_state.c:954
954 brw_wm_surface_state.c: No such file or directory.
(gdb) l
949 in brw_wm_surface_state.c
(gdb) bt
#0 brw_update_renderbuffer_surface (brw=0x77fae040, rb=0x61aa30, unit=0)
at brw_wm_surface_state.c:954
#1 0x7388c220 in brw_update_renderbuffer_surfaces (brw=0x77fae040)
at brw_wm_surface_state.c:1047
#2 0x738765a0 in brw_upload_state (brw=brw@entry=0x77fae040)
at brw_state_upload.c:503
#3 0x73864047 in brw_try_draw_prims (max_index=optimized out,
min_index=optimized out, ib=0x0, nr_prims=2, prim=0x7ef4a0,
arrays=0x67a810, ctx=0x77fae040) at brw_draw.c:482
#4 brw_draw_prims (ctx=0x77fae040, arrays=0x67a810, prim=0x7ef4a0,
nr_prims=2, ib=0x0, index_bounds_valid=optimized out, min_index=0,
max_index=161, tfb_vertcount=0x0) at brw_draw.c:566
#5 0x739916ac in vbo_save_playback_vertex_list (ctx=0x77fae040,
data=0x7eed08) at vbo/vbo_save_draw.c:298
#6 0x738e2fe2 in ext_opcode_execute (node=0x7eed00, ctx=0x77fae040)
at main/dlist.c:602
#7 execute_list (ctx=0x77fae040, list=optimized out) at main/dlist.c:7505
#8 0x738e6a22 in _mesa_CallList (list=1) at main/dlist.c:8922
#9 0x004023bc in draw () at glxgears.c:263
#10 0x00401bc9 in draw_gears () at glxgears.c:315
#11 draw_frame (win=52428802, dpy=0x605010) at glxgears.c:340
#12 event_loop (win=52428802, dpy=0x605010) at glxgears.c:696
#13 main (argc=1, argv=optimized out) at glxgears.c:776

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  mesa SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 947544] Re: mesa SIGSEGV in brw_update_renderbuffer_surface()

2013-06-15 Thread Ross Schlaikjer
I am seeing what appears to be the same error. It is reproducible 100%
of the time with glxgears.

I ran glxgears in apitrace (causing a segfault). Attatched is the raw
apitrace.

Is there any other data that I can provide that would be useful?

The segfault is visible in the apitrace replay.
$ apitrace replay glxgears.trace 
apitrace: warning: caught signal 11
1357: error: caught an unhandled exception
apitrace: info: taking default action for signal 11

gdb output for glxgears:

Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.

Program received signal SIGSEGV, Segmentation fault.
brw_update_renderbuffer_surface (brw=0x77fae040, rb=0x61aa30, unit=0)
at brw_wm_surface_state.c:954
954 brw_wm_surface_state.c: No such file or directory.
(gdb) l
949 in brw_wm_surface_state.c
(gdb) bt
#0  brw_update_renderbuffer_surface (brw=0x77fae040, rb=0x61aa30, unit=0)
at brw_wm_surface_state.c:954
#1  0x7388c220 in brw_update_renderbuffer_surfaces (brw=0x77fae040)
at brw_wm_surface_state.c:1047
#2  0x738765a0 in brw_upload_state (brw=brw@entry=0x77fae040)
at brw_state_upload.c:503
#3  0x73864047 in brw_try_draw_prims (max_index=optimized out, 
min_index=optimized out, ib=0x0, nr_prims=2, prim=0x7ef4a0, 
arrays=0x67a810, ctx=0x77fae040) at brw_draw.c:482
#4  brw_draw_prims (ctx=0x77fae040, arrays=0x67a810, prim=0x7ef4a0, 
nr_prims=2, ib=0x0, index_bounds_valid=optimized out, min_index=0, 
max_index=161, tfb_vertcount=0x0) at brw_draw.c:566
#5  0x739916ac in vbo_save_playback_vertex_list (ctx=0x77fae040, 
data=0x7eed08) at vbo/vbo_save_draw.c:298
#6  0x738e2fe2 in ext_opcode_execute (node=0x7eed00, ctx=0x77fae040)
at main/dlist.c:602
#7  execute_list (ctx=0x77fae040, list=optimized out) at main/dlist.c:7505
#8  0x738e6a22 in _mesa_CallList (list=1) at main/dlist.c:8922
#9  0x004023bc in draw () at glxgears.c:263
#10 0x00401bc9 in draw_gears () at glxgears.c:315
#11 draw_frame (win=52428802, dpy=0x605010) at glxgears.c:340
#12 event_loop (win=52428802, dpy=0x605010) at glxgears.c:696
#13 main (argc=1, argv=optimized out) at glxgears.c:776


** Attachment added: apitrace dump for glxgears
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/947544/+attachment/3704593/+files/glxgears.trace

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  mesa SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 947544]

2013-06-08 Thread Eric Anholt
Ran the segfault one in a loop both on ivb and gm45 for a while, with no
segfaults.  Were you seeing segfaults in the apitrace replay?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  mesa SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 947544] Re: mesa SIGSEGV in brw_update_renderbuffer_surface()

2013-06-08 Thread Bug Watch Updater
** Changed in: mesa
   Status: Confirmed = Incomplete

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  mesa SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 947544]

2013-05-03 Thread Eric Anholt
Do you have an exact command line and set of things to do to reproduce
the problem?  Perhaps an apitrace of a crashing application?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  mesa SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 947544]

2013-05-03 Thread Mike Gratton
It's easy to reproduce using Gazebo.

1. Install Gazebo: http://gazebosim.org/wiki/1.6/install
2. Run gzserver in one terminal
3. Run gzclient in another

Both processes use OpenGL, but only gzclient displays a gui. Starting
gzserver will result in this error, but only occasionally. Starting
gzclient will result in the error more frequently - perhaps once in
every 5-10 invocations. Closing the gzclient window will also often
produce the error.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  mesa SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 947544]

2013-05-03 Thread Mike Gratton
I can't attach the apitrace dumps to this bug because they are too big,
so have uploaded them to a web server:

gzclient-1.7.1 successful startup: 
http://vee.net/tmp/fdo-61724/gzclient-1.7.1.trace-nosegfault
gzclient-1.7.1 segfault startup: 
http://vee.net/tmp/fdo-61724/gzclient-1.7.1.trace-segfault

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  mesa SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 947544] Re: mesa SIGSEGV in brw_update_renderbuffer_surface()

2013-03-13 Thread Roman
This or very similar crash (with the same stuff on top of the stack)
appears very frequently with fullscreen windows, when the KWin option
suspend desktop effects for fullscreen windows is turned on. This is
similar to the fixed bug 974041, though that one looks different. The
crash is typically trigerred by alt-tabbing from such a fullscreen
window  (with ~50% chance).

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  mesa SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 947544] Re: mesa SIGSEGV in brw_update_renderbuffer_surface()

2013-03-13 Thread Mike Gratton
Bug 974041 seems like an X server crash, while this involves clients
crashing but X server remains up (although I suspect that after numerous
such client crashes the system's stability in general starts to suffer).
The cases I have encountered have all involved non-full-screen windows,
also.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  mesa SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 947544] Re: mesa SIGSEGV in brw_update_renderbuffer_surface()

2013-03-12 Thread Bug Watch Updater
Launchpad has imported 3 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=61724.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-03-03T05:03:54+00:00 Mike Gratton wrote:

Multiple apps are getting a segfault in brw_update_renderbuffer_surface,
including VLC, Compiz and Gazebo (which uses OGRE).

Ubuntu bug is reported here with a number of stack traces:

https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/947544

I'll attach a complete, more recent one in a moment, but the head looks
like this:

#0  brw_update_renderbuffer_surface (brw=0x403eb30, rb=0x4510500, unit=0) at 
brw_wm_surface_state.c:1109
#1  0x7fffdc0e9ab0 in brw_update_renderbuffer_surfaces (brw=0x403eb30) at 
brw_wm_surface_state.c:1205
#2  0x7fffdc0d3b02 in brw_upload_state (brw=brw@entry=0x403eb30) at 
brw_state_upload.c:498
#3  0x7fffdc0c11a7 in brw_try_draw_prims (max_index=4294967295, 
min_index=4294952344, ib=optimised out, 
nr_prims=optimised out, prim=0x7fffc580, arrays=optimised out, 
ctx=0x403eb30) at brw_draw.c:493
#4  brw_draw_prims (ctx=0x403eb30, prim=0x7fffc580, nr_prims=optimised 
out, ib=optimised out, 
index_bounds_valid=optimised out, min_index=4294967295, 
max_index=4294967295, tfb_vertcount=0x0) at brw_draw.c:589
#5  0x7fffd73a43da in vbo_handle_primitive_restart (ctx=optimised out, 
prim=optimised out, nr_prims=optimised out, 
ib=optimised out, index_bounds_valid=optimised out, 
min_index=optimised out, max_index=4294967295)
at ../../../../../src/mesa/vbo/vbo_exec_array.c:570
#6  0x7fffd73a53b4 in vbo_validated_drawrangeelements 
(ctx=ctx@entry=0x403eb30, mode=mode@entry=4, 
index_bounds_valid=index_bounds_valid@entry=0 '\000', 
start=start@entry=4294967295, end=end@entry=4294967295, 
count=count@entry=39690, type=type@entry=5123, indices=indices@entry=0x0, 
basevertex=basevertex@entry=0, 
numInstances=numInstances@entry=1, baseInstance=baseInstance@entry=0) at 
../../../../../src/mesa/vbo/vbo_exec_array.c:867
#7  0x7fffd73a5724 in vbo_exec_DrawElements (mode=4, count=39690, 
type=5123, indices=0x0)
at ../../../../../src/mesa/vbo/vbo_exec_array.c:997
#8  0x7fffd4c05124 in Ogre::GLRenderSystem::_render(Ogre::RenderOperation 
const) ()
   from /usr/lib/x86_64-linux-gnu/OGRE-1.7.4/RenderSystem_GL.so

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/947544/comments/6


On 2013-03-03T05:10:45+00:00 Mike Gratton wrote:

Created attachment 75816
gazebo client stack trace

Stack trace from Gazebo simulator client crash. Occurs every 2 or 2
program executions.

Ubuntu 13.04:
linux 3.5.0-25-generic
mesa 9.0-0ubuntu1
libdrm 2.4.39-0ubuntu1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/947544/comments/7


On 2013-03-03T05:14:02+00:00 Mike Gratton wrote:

This is on Sandybridge, an i7-2620M/HD3000.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/947544/comments/8


** Changed in: mesa
   Status: Unknown = Confirmed

** Changed in: mesa
   Importance: Unknown = High

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  mesa SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 947544] Re: compiz crashed with SIGSEGV in brw_update_renderbuffer_surface()

2013-03-02 Thread Mike Gratton
Reported upstream, I get this every few times I run the Gazebo simulator
client.

Qantal, amd64, Sandybridge HD3000.


** Bug watch added: freedesktop.org Bugzilla #61724
   https://bugs.freedesktop.org/show_bug.cgi?id=61724

** Also affects: mesa via
   https://bugs.freedesktop.org/show_bug.cgi?id=61724
   Importance: Unknown
   Status: Unknown

** Summary changed:

- compiz crashed with SIGSEGV in brw_update_renderbuffer_surface()
+ mesa SIGSEGV in brw_update_renderbuffer_surface()

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  mesa SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 947544] Re: compiz crashed with SIGSEGV in brw_update_renderbuffer_surface()

2013-01-03 Thread Daniel van Vugt
** Package changed: compiz (Ubuntu) = mesa (Ubuntu)

** Attachment removed: BootLog.gz
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/947544/+attachment/2819520/+files/BootLog.gz

** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/947544

Title:
  compiz crashed with SIGSEGV in brw_update_renderbuffer_surface()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/947544/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp