amdcccle crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
fglrx-installer (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
when changing resolution and changing to dual monitor display, amdcccle crashes and disappears.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: fglrx-amdcccle 2:8.881-0ubuntu3
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelMo
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Sep 30 20:19:25 2011
DistUpgraded: Log time: 2011-09-17 10:24:23.152028
DistroCodename: oneiric
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110910)
MachineType: System manufacturer System Product Name
ProcCmdline: amdcccle
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x5886f4: cmp 0x10(%rbx),%r12d
PC (0x005886f4) ok
source "0x10(%rbx)" (0x00000010) not located in a known VMA region (needed readable region)!
destination "%r12d" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: fglrx-installer
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: amdcccle crashed with SIGSEGV
UpgradeStatus: Upgraded to oneiric on 2011-09-17 (13 days ago)
UserGroups:
dmi.bios.date: 11/17/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS P5N32-E SLI ACPI BIOS Revision 1903
dmi.board.name: P5N32-E SLI
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.6+
version.ia32-libs: ia32-libs N/A
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.