compiz crashed with SIGSEGV in _wordcopy_fwd_aligned() from __memmove_sse2() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from

Reported by rosn on 2012-02-17
50
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Compiz
High
Unassigned
Compiz Core
High
Unassigned
compiz (Ubuntu)
High
Unassigned
mesa (Ubuntu)
High
Unassigned

Bug Description

12.04 upgrade this afternoon, the system has significant effects, but I'm just a normal visit the website shortly tips are said compiz. I do not know why.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.2.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6
Uname: Linux 3.2.0-16-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Fri Feb 17 17:31:40 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20120109)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=zh_CN:zh
 PATH=(custom, no user)
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f6f3448aac0: mov (%rsi),%rax
 PC (0x7f6f3448aac0) ok
 source "(%rsi)" (0x7d45b270) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 TfpTexture::bindPixmapToTexture(unsigned long, int, int, int) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in TfpTexture::bindPixmapToTexture()
UpgradeStatus: Upgraded to precise on 2012-02-17 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

rosn (rosn) wrote :

StacktraceTop:
 _wordcopy_fwd_aligned (dstp=6455411520, srcp=2101719664, len=7341082) at wordcopy.c:41
 drisw_update_tex_buffer (drawable=<optimized out>, ctx=<optimized out>, res=<optimized out>) at /usr/include/x86_64-linux-gnu/bits/string3.h:58
 dri_set_tex_buffer2 (pDRICtx=<optimized out>, target=3553, format=8409, dPriv=<optimized out>) at dri_drawable.c:230
 GLScreen::setDefaultViewport (this=<optimized out>) at /build/buildd/compiz-0.9.7.0~bzr2995/plugins/opengl/src/screen.cpp:1088
 ?? ()

affects: ubuntu → unity (Ubuntu)
Changed in unity (Ubuntu):
importance: Undecided → Medium
summary: - compiz crashed with SIGSEGV in TfpTexture::bindPixmapToTexture()
+ compiz crashed with SIGSEGV in _wordcopy_fwd_aligned()
tags: removed: need-amd64-retrace
visibility: private → public
affects: unity (Ubuntu) → mesa (Ubuntu)

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

Changed in mesa (Ubuntu):
status: New → Confirmed
summary: - compiz crashed with SIGSEGV in _wordcopy_fwd_aligned()
+ compiz crashed with SIGSEGV in _wordcopy_fwd_aligned() from
+ __memmove_sse2() from drisw_update_tex_buffer() from
+ dri_set_tex_buffer2() from
Changed in compiz-core:
status: New → Confirmed
importance: Undecided → High
Changed in mesa (Ubuntu):
importance: Medium → High
Changed in compiz (Ubuntu):
status: New → Confirmed
importance: Undecided → High
Maarten Lankhorst (mlankhorst) wrote :

This might be a real bug on its own, but why are you using the software rasterizer?

Changed in compiz:
importance: Undecided → High
status: New → Confirmed
Bryce Harrington (bryce) wrote :

I see that the new mesa 8.0.3 bugfix release includes a couple fixes to the drisw code. I wonder if this is the bug you're seeing.

Dave Airlie:
    glx/drisw: avoid segfaults when we fail to get visual
    drisw: fix image stride calculation for 16-bit.

I've posted mesa 8.0.3 to this PPA. Please install it, reboot, and re-test and see if you can still reproduce the crash. If you're able to test it long enough to convince yourself that the crash is gone, please reply here indicating so. We may be able to roll out this fix for precise-proposed as an SRU.

https://launchpad.net/~bryce/+archive/mesa-803

Changed in mesa (Ubuntu):
status: Confirmed → Incomplete
bugbot (bugbot) wrote :

We're closing this bug since there has not been a response from the original reporter. However, the issue still exists please feel free to reopen with the requested information. If you're not the original reporter, we'd prefer you file a new bug report.

Some tips:

  * Report X.org bugs via the command: `ubuntu-bug xorg`

  * Test against the latest development Ubuntu. http://cdimage.ubuntu.com/daily-live/
    Bugs marked as affecting the development version tend to get priority attention.

  * The `xdiagnose` utility has functionality for enabling debugging and
    analyzing a few common X problems.

  * Tag your bugs with the Ubuntu versions you have reproduced the issue in.

  * See https://wiki.ubuntu.com/X/Reporting for tips on writing good bug reports.

Changed in mesa (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers