amdcccle crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Logging in to gnome session
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: fglrx-amdcccle 2:8.881-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-12-
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Wed Sep 28 12:32:49 2011
DistUpgraded: Log time: 2011-08-31 14:26:48.493205
DistroCodename: oneiric
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: Hewlett-Packard HP Compaq dc7600 Small Form Factor
ProcCmdline: amdcccle
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x81cf6b8: cmp 0x8(%ebx),%edx
PC (0x081cf6b8) ok
source "0x8(%ebx)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: fglrx-installer
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: amdcccle crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-09-27 (0 days ago)
UserGroups:
dmi.bios.date: 07/01/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786D1 v01.61
dmi.board.name: 09F8h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Compaq dc7600 Small Form Factor
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.5.
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #647802, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.