compiz crashed with SIGSEGV in brw_upload_state()

Bug #733192 reported by Benjamin Drung
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Mesa
Won't Fix
High
Nux
Invalid
Undecided
Unassigned
Unity
Invalid
Undecided
Unassigned
mesa (Ubuntu)
Won't Fix
High
Unassigned
nux (Ubuntu)
Invalid
Medium
Unassigned
unity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This crash occurs when the GPU has locked up. Since there's no way to gracefully handle 3D when the 3D hardware has crashed, this is marked as Won't Fix in mesa. If you're seeing this crash you should be able to post the information requested in comments #44 & #46 to a new bug.

Original report follows:
I don't know what this crash triggered. I had a bunch of kernel, intel driver, and other crashes.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.32-0ubuntu1
Uname: Linux 2.6.38-997-generic x86_64
Architecture: amd64
Date: Fri Mar 11 11:18:54 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f386e6776d1: mov %rdi,(%rsi)
 PC (0x7f386e6776d1) ok
 source "%rdi" ok
 destination "(%rsi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? () from /usr/lib/dri/i965_dri.so
 brw_upload_state () from /usr/lib/dri/i965_dri.so
 brw_draw_prims () from /usr/lib/dri/i965_dri.so
 ?? () from /usr/lib/dri/libdricore.so
 _mesa_meta_Clear () from /usr/lib/dri/libdricore.so
Title: compiz crashed with SIGSEGV in brw_upload_state()
UpgradeStatus: Upgraded to natty on 2011-03-11 (0 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
XsessionErrors:
 (Do:2179): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
 (<unknown>:2145): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
 (<unknown>:2145): libindicator-WARNING **: Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
---
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
DRM.card0.DP.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.DP.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI.A.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1920x1200 1600x1200 1280x1024 1280x1024 1280x960 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
 edid-base64: AP///////wBMLbYCNDJVSCQSAQOANCCgKlrRp1ZLmyQTUFS/74CpQIGAgUBxTwEBAQEBAQEBKDyAoHCwI0AwIDYABkQhAAAaAAAA/QA4Sx5REQAKICAgICAgAAAA/ABTeW5jTWFzdGVyCiAgAAAA/wBIOVhROTAxMjY0CiAgAJw=
DRM.card0.HDMI.A.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DistUpgraded: Log time: 2011-03-11 00:20:27.564047
DistroCodename: natty
DistroRelease: Ubuntu 11.04
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
InstallationMedia_: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
InstallationMedia__: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
InstallationMedia___: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
InstallationMedia____: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
InstallationMedia_____: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100921.1)
MachineType: System manufacturer System Product Name
Package: unity 3.6.6-0ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=782d30b2-7975-4d00-bf3e-de316d2b96f6 ro quiet splash vt.handoff=7
ProcKernelCmdLine_: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=782d30b2-7975-4d00-bf3e-de316d2b96f6 ro quiet splash vt.handoff=7
ProcKernelCmdLine__: BOOT_IMAGE=/boot/vmlinuz-2.6.38-7-generic root=UUID=782d30b2-7975-4d00-bf3e-de316d2b96f6 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 2.6.38-7.35lp717114v201103180831-generic 2.6.38
ProcVersionSignature_: Ubuntu 2.6.38-7.35lp717114v201103180831-generic 2.6.38
ProcVersionSignature__: Ubuntu 2.6.38-7.35lp717114v201103180831-generic 2.6.38
ProcVersionSignature___: Ubuntu 2.6.38-7.35lp717114v201103180831-generic 2.6.38
ProcVersionSignature____: Ubuntu 2.6.38-7.35lp717114v201103180831-generic 2.6.38
ProcVersionSignature_____: Ubuntu 2.6.38-7.35lp717114v201103180831-generic 2.6.38
Renderer: Unknown
Tags: natty ubuntu compiz-0.9 natty natty ubuntu compiz-0.9 natty natty natty ubuntu compiz-0.9
Uname: Linux 2.6.38-7-generic x86_64
UpgradeStatus: Upgraded to natty on 2011-03-11 (8 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
dmi.bios.date: 02/11/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0806
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd02/11/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8H67-MPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.4-0ubuntu7
version.libdrm2: libdrm2 2.4.23-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu11
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6

Revision history for this message
Benjamin Drung (bdrung) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 upload_vs_state (brw=0x7544a0) at /usr/include/bits/string3.h:52
 brw_upload_state (brw=0x7544a0) at brw_state_upload.c:484
 brw_try_draw_prims (ctx=0x7544a0, arrays=0x7a50e0, prim=0x7fffd5bd5500, nr_prims=0, ib=0x0, index_bounds_valid=<value optimized out>, min_index=0, max_index=3) at brw_draw.c:392
 brw_draw_prims (ctx=0x7544a0, arrays=0x7a50e0, prim=0x7fffd5bd5500, nr_prims=0, ib=0x0, index_bounds_valid=<value optimized out>, min_index=0, max_index=3) at brw_draw.c:447
 vbo_draw_arrays (ctx=0x7544a0, mode=6, start=0, count=<value optimized out>, numInstances=1) at vbo/vbo_exec_array.c:588

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 nux (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Alex Launi (alexlauni) wrote :

This looks like a graphics driver bug

Changed in nux:
status: New → Incomplete
Changed in unity:
status: New → Incomplete
Changed in nux (Ubuntu):
status: New → Incomplete
Alex Launi (alexlauni)
Changed in unity (Ubuntu):
status: New → Incomplete
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi benjamin, please run 'apport-collect 733192' to tack the X logs on this (hmm, thought we'd linked the compiz apport hook to include the X info too).

affects: xserver-xorg-video-intel (Ubuntu) → mesa (Ubuntu)
Changed in mesa (Ubuntu):
status: New → Incomplete
Revision history for this message
Benjamin Drung (bdrung) wrote : BootDmesg.txt

apport information

tags: added: apport-collected compiz-0.9 ubuntu
description: updated
Revision history for this message
Benjamin Drung (bdrung) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : Dependencies.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : GconfCompiz.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : GdmLog.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : GdmLog1.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : GdmLog2.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : Lspci.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : Lsusb.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : ProcCpuinfo_.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : ProcCpuinfo__.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : ProcInterrupts_.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : ProcInterrupts__.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : ProcModules.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : ProcModules_.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : ProcModules__.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : UdevDb.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : UdevLog.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : UdevLog_.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : UdevLog__.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : UnitySupportTest.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : XorgLog.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : XorgLogOld.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : XorgLogOld_.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : XorgLogOld__.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : XorgLog_.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : XorgLog__.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : Xrandr.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : monitors.xml.txt

apport information

Revision history for this message
Benjamin Drung (bdrung) wrote : monitors.xml_.txt

apport information

Bryce Harrington (bryce)
Changed in mesa (Ubuntu):
assignee: nobody → Chris Halse Rogers (raof)
Changed in mesa (Ubuntu):
importance: Undecided → High
Revision history for this message
Chris Halse Rogers (raof) wrote :

Ok. I think I can see what's going wrong here, but I'm not entirely sure how to actually fix it, as mesa's half-way through emitting the render state when this blows up.

I'll send a bug upstream.

Changed in mesa:
importance: Unknown → Medium
status: Unknown → Confirmed
Revision history for this message
Chris Halse Rogers (raof) wrote :

Do you have any idea how frequently you see this crash? This is a failure to properly handle failures elsewhere in the system, so if this happens often enough it would be good to get some details of when it's happening so we can nail down the root-cause.

Revision history for this message
Benjamin Drung (bdrung) wrote :

I experience this crash only a few times.

I don't know if this is related, but sometimes my system freezes when I leave my system for a longer period and power manager blanks the monitor.

Changed in mesa:
importance: Medium → High
Revision history for this message
Prunus dulcis (prunus-dulcis) wrote :

For me the report tool came up after I had had to restart the notebook due to unity-window-decorator crashing due to java applications.

Revision history for this message
Prunus dulcis (prunus-dulcis) wrote :

I am getting this bug about every once a week - sometimes taking document progress with it. I made a video of how it looks for me.

dmesg brought up the following errors:
[drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
[drm:i915_reset] *ERROR* i915_do_wait_request returns -11 (awaiting 5337284 at 5337277, next 5337285)
[drm:i915_reset] *ERROR* Failed to reset chip.
show_signal_msg: 15 callbacks suppressed
compiz[1544]: segfault at 8 ip b712b1b1 sp bfac51e0 error 6 in libc-2.13.so[b7016000+15a000]
[drm:drm_mode_getfb] *ERROR* invalid frambuffer id

Then I tried to ressurect unity-window decorator
unity-window-decorator --replace&disown
[1] 7402
(unity-window-decorarotr:7402): Gtk-WARNING **: cannot open display:
_

I was also using java applications at that time, which also sometimes crash unity-window-decorator but most of the times, just the window-borders and decorations crash and I can recover / replace them with above command. Not when it flashes like in the video though...

Revision history for this message
Bryce Harrington (bryce) wrote : Re: [Bug 733192] Re: compiz crashed with SIGSEGV in brw_upload_state()

On Wed, Jun 22, 2011 at 10:14:53AM -0000, Prunus dulcis wrote:
> I am getting this bug about every once a week - sometimes taking
> document progress with it. I made a video of how it looks for me.
>
> dmesg brought up the following errors:
> [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung

"GPU hung" there is the key bit. It means your GPU has hung. For this
kind of bug, the data you need to be collecting is your 'dmesg' and this
file:

  /sys/kernel/debug/dri/0/i915_error_state

Also, since these types of issues can be hard to troubleshoot, steps to
reproduce the problem are very important. Most of the time they seem
random, but there's usually activities that tend to trigger them more
often and finding out what those activities are can help pinpoint what
section of code is at fault.

Changed in mesa:
status: Confirmed → Won't Fix
Revision history for this message
Chris Halse Rogers (raof) wrote :

This bug has been marked WONTFIX upstream as this can only trigger when the GPU hangs and so there's no way to gracefully recover 3D. Crashing the 3D using program is as good a response as any; it's guaranteed not to function with a hung GPU anyway.

I'm going to mark this bug as invalid. If you run into this bug then the debugging information necessary is that referred to by Bryce in comment #44 - dmesg and i915_error_state, filed as a new bug. The Intel GPU hang apport hook should pop up and attach this information for you when the GPU hangs.

Changed in mesa (Ubuntu):
status: Incomplete → Won't Fix
Changed in nux (Ubuntu):
status: Incomplete → Invalid
Changed in unity (Ubuntu):
status: Incomplete → Invalid
Changed in nux:
status: Incomplete → Invalid
Changed in unity:
status: Incomplete → Invalid
Changed in mesa (Ubuntu):
assignee: Chris Halse Rogers (raof) → nobody
description: updated
To post a comment you must log in.