compiz crashed with SIGSEGV in intel_renderbuffer_tile_offsets()

Bug #821258 reported by Christopher Patrick
104
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
Invalid
Undecided
Unassigned
mesa (Ubuntu)
Expired
High
Unassigned
unity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

i dragged the gnome-terminal to the top pf the screen to make it full screen and it showed wired picture then compliz crashes

#0 0x00007fe3d86e1c0e in intel_renderbuffer_tile_offsets () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#1 0x00007fe3d8722717 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#2 0x00007fe3d870bffa in brw_upload_state () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#3 0x00007fe3d86f9c40 in brw_draw_prims () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
#4 0x00007fe3d83721fb in ?? () from /usr/lib/x86_64-linux-gnu/dri/libdricore.so
#5 0x00007fe3d8991b27 in GLWindow::glDrawGeometry() () from /usr/lib/compiz/libopengl.so
#6 0x00007fe3d899421e in GLWindow::glDrawTexture(GLTexture*, GLFragment::Attrib&, unsigned int) () from /usr/lib/compiz/libopengl.so

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.6.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
Date: Thu Aug 4 22:52:05 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
ProcCmdline: compiz
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe3d86e1c0e <intel_renderbuffer_tile_offsets+14>: mov 0xc(%rax),%r10d
 PC (0x7fe3d86e1c0e) ok
 source "0xc(%rax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%r10d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 intel_renderbuffer_tile_offsets () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 brw_upload_state () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 brw_draw_prims () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/libdricore.so
Title: compiz crashed with SIGSEGV in intel_renderbuffer_tile_offsets()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Christopher Patrick (cpatrick08) wrote :
visibility: private → public
visibility: public → private
visibility: private → public
bugbot (bugbot)
tags: added: crash
Bryce Harrington (bryce)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi cpatrick, this looks like a mesa bug. A new mesa 7.11 was uploaded the day you filed this. I can't tell whether you had that installed at the time since this bug was filed without the usual xorg log files, however from the report it looks like you installed fresh on 8/3 and hadn't updated on the 4th when you placed the report.

I'm guessing you haven't reproduced this crash since the 4th, is that correct? If so, I think we can close this as fixed. If you're still able to reproduce it, would you mind reproducing it and then running 'apport-collect 821258' to attach the X logs?

affects: xserver-xorg-video-intel (Ubuntu) → mesa (Ubuntu)
Changed in mesa (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 intel_renderbuffer_tile_offsets () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 brw_upload_state () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 brw_draw_prims () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/libdricore.so

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in mesa (Ubuntu):
importance: High → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi cpatrick,

Thanks for that; sadly the retracer is not giving us any further information than was originally posted.

Would you be willing to try again and collect a manual full backtrace using gdb? Directions for doing this are available at http://wiki.ubuntu.com/X/Backtracing (skip down past the apport directions and look at the gdb directions.)

Changed in mesa (Ubuntu):
importance: Medium → High
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Omer Akram (om26er)
Changed in unity:
status: New → Incomplete
Changed in unity (Ubuntu):
status: New → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.

Changed in mesa (Ubuntu):
status: Incomplete → Expired
Omer Akram (om26er)
Changed in unity (Ubuntu):
status: Incomplete → Invalid
Changed in unity:
status: Incomplete → Invalid
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.