gnome-shell crashed with SIGSEGV in brw_update_renderbuffer_surface()

Bug #939365 reported by Alex Rybicki
52
This bug affects 6 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Occurred during gameplay of Team Fortress 2 (Steam) within Wine.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-shell 3.2.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Thu Feb 23 01:40:17 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-shell
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120126)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f839757376e: mov 0x218(%rax),%rbp
 PC (0x7f839757376e) ok
 source "0x218(%rax)" (0x00000218) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () 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: gnome-shell crashed with SIGSEGV in brw_upload_state()
UpgradeStatus: Upgraded to precise on 2012-02-17 (6 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Alex Rybicki (alex-rybicki) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 brw_update_renderbuffer_surface (brw=0x1f42a30, rb=0x2c099e0, unit=0) at brw_wm_surface_state.c:905
 brw_update_renderbuffer_surfaces (brw=0x1f42a30) at brw_wm_surface_state.c:1002
 brw_upload_state (brw=0x1f42a30) at brw_state_upload.c:504
 brw_try_draw_prims (max_index=<optimized out>, min_index=<optimized out>, ib=0x0, nr_prims=1, prim=0x7fffb1f1a4d0, arrays=0x1fb70c8, ctx=0x1f42a30) at brw_draw.c:521
 brw_draw_prims (ctx=0x1f42a30, arrays=0x1fb70c8, prim=0x7fffb1f1a4d0, nr_prims=1, ib=0x0, index_bounds_valid=<optimized out>, min_index=0, max_index=3, tfb_vertcount=0x0) at brw_draw.c:605

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 gnome-shell (Ubuntu):
importance: Undecided → Medium
summary: - gnome-shell crashed with SIGSEGV in brw_upload_state()
+ gnome-shell crashed with SIGSEGV in brw_update_renderbuffer_surface()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Jeremy Bícha (jbicha)
visibility: private → public
tags: added: quantal
Revision history for this message
Heiko Roth (roth-egotec) wrote :

I've got the bug since Ubuntu 12.04 release canditate. I haven't got any such a problem with Ubuntu 12.04 beta or 11.10.
I upgraded now to 12.10. Same problem and I feel, it's getting worse.
Working with Ubtuntu2d desktop, no such problem occurs.

Revision history for this message
Heiko Roth (roth-egotec) wrote :

As I wrote, I use ubuntu 2d right now. No crash, but system halts for a second every now and then (every hour).

Revision history for this message
Jeremy Bícha (jbicha) wrote :

Thank you for reporting this bug to Ubuntu. Ubuntu 12.04 LTS reached End of Life in April. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Please upgrade to Ubuntu 16.04 LTS and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

I apologize that we are not always to respond to bug reports promptly. Do feel free to report any other bugs you may find.

Changed in gnome-shell (Ubuntu):
status: Confirmed → 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.