Xorg crashed with SIGABRT

[Florian Hars]

I tried the 14.04 beta on a brand new Thinkpad E145 with an AMD E1 CPU and the corresponding Radeon HD graphics.
I suspended the machine (just to see what would happen) and it came back up, but I got this crash report.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-core 2:1.15.0-1ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
Uname: Linux 3.13.0-19-generic x86_64
.tmp.unity.support.test.0:

.tmp.unity.support.test.1:

ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CasperVersion: 1.339
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Mar 30 17:15:08 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8240] [1002:9838] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:510c]
LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
MachineType: LENOVO 20BC0006GE
ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron:

ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity
Renderer: Software
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/11/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: HSET20WW (1.03 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BC0006GE
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrHSET20WW(1.03):bd07/11/2013:svnLENOVO:pn20BC0006GE:pvrThinkPadEdgeE145:rvnLENOVO:rn20BC0006GE:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20BC0006GE
dmi.product.version: ThinkPad Edge E145
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.04.20140320.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sun Mar 30 17:15:24 2014
xserver.configfile: default
xserver.errors: AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.0-1ubuntu7
xserver.video_driver: radeon

[Florian Hars (hars)]

The first resume took a bit longer than I expected (probably because of the crash), and I was greeted with a login screen. I tried another suspend and resume cycle, and it came back immediately, with the browser window with this bug report still open.

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1283736, 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.