compiz crashed with SIGABRT in assert() from intel_resolve_map_set() from intel_miptree_slice_set_needs_depth_resolve() from intel_renderbuffer_set_needs_depth_resolve() from brw_postdraw_set_buffers_need_resolve()

Bug #1042034 reported by Rocko
This bug report is a duplicate of:  Bug #1042293: assert in intel_resolve_map_set. Edit Remove
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa (Ubuntu)
New
Medium
Unassigned

Bug Description

Compiz crashed, and X went down with it so I had to log back in. This dump was in /var/crash afterwards.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity 6.2.0-0ubuntu3
Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
Date: Mon Aug 27 10:01:43 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: unity
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6
 intel_resolve_map_set () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
Title: compiz crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

Revision history for this message
Rocko (rockorequin) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __assert_fail_base (fmt=<optimized out>, assertion=0x7fe8084b06c6 "(*tail)->need == need", file=0x7fe8084b06b2 "intel_resolve_map.c", line=<optimized out>, function=<optimized out>) at assert.c:94
 __GI___assert_fail (assertion=assertion@entry=0x7fe8084b06c6 "(*tail)->need == need", file=file@entry=0x7fe8084b06b2 "intel_resolve_map.c", line=line@entry=46, function=function@entry=0x7fe8084b06e0 "intel_resolve_map_set") at assert.c:103
 intel_resolve_map_set (head=<optimized out>, level=0, layer=0, need=need@entry=GEN6_HIZ_OP_DEPTH_RESOLVE) at intel_resolve_map.c:46
 intel_miptree_slice_set_needs_depth_resolve (mt=<optimized out>, level=<optimized out>, layer=<optimized out>) at intel_mipmap_tree.c:890
 intel_renderbuffer_set_needs_depth_resolve (irb=irb@entry=0x17da9b0) at intel_fbo.c:908

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
importance: Undecided → Medium
summary: - compiz crashed with SIGABRT in raise()
+ compiz crashed with SIGABRT in __assert_fail_base()
tags: removed: need-amd64-retrace
visibility: private → public
summary: - compiz crashed with SIGABRT in __assert_fail_base()
+ compiz crashed with SIGABRT in assert() from intel_resolve_map_set()
+ from intel_miptree_slice_set_needs_depth_resolve() from
+ intel_renderbuffer_set_needs_depth_resolve() from
+ brw_postdraw_set_buffers_need_resolve()
affects: unity (Ubuntu) → mesa (Ubuntu)
Revision history for this message
Edward Donovan (edward.donovan) wrote :

I just filed bug 1042092, for gnome-control-center crashing, with a similar trace. I think that might be a dupe of this, but I'd love to get a more experienced opinion. Thanks!

Revision history for this message
Edward Donovan (edward.donovan) wrote :

Well, the retracer duped my bug 1042092 to private bug 1041891. So, for now, instead of learning more, I know less. :(

Thanks anyway.

Revision history for this message
Edward Donovan (edward.donovan) wrote :

Ok! Now bug 1041891 is public, and the stacktrace is much the same. In part:

  intel_resolve_map_set at intel_resolve_map.c:46
  intel_miptree_slice_set_needs_depth_resolve at intel_mipmap_tree.c:890
  intel_renderbuffer_set_needs_depth_resolve at intel_fbo.c:908

I'm still not 100% sure, but confident enough to mark this a dupe, I guess. Thanks.

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.