Xorg crashed with SIGABRT in <unavailable> in ??()

Bug #1126198 reported by David Henningsson
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

nexus7

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-core 2:1.13.2-0ubuntu2
Uname: Linux 3.1.10-9-nexus7 armv7l
.tmp.unity.support.test.0:

ApportVersion: 2.8-0ubuntu4
Architecture: armhf
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu Feb 14 16:49:55 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:

InstallationDate: Installed on 2013-02-04 (11 days ago)
InstallationMedia: Ubuntu Raring Ringtail (development branch) - armhf (20130202-15:21)
Lspci:

Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MarkForUpload: True
ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none
ProcEnviron:

ProcKernelCmdLine: tegra_wdt.heartbeat=30 tegraid=30.1.3.0.0 mem=1022M@2048M android.commchip=0 vmalloc=128M androidboot.serialno=015d2109ab240207 video=tegrafb no_console_suspend=1 console=none debug_uartport=hsport usbcore.old_scheme_first=1 lp0_vec=8192@0xbddf9000 tegra_fbmem=8195200@0xabe01000 core_edp_mv=0 audio_codec=rt5640 board_info=f41:a00:1:44:2 tegraboot=sdmmc gpt gpt_sector=14934015 androidboot.bootloader=3.34 root=/dev/mmcblk0p9 ro console=tty0 access=m2 quiet splash
ProcModules: zram 8348 4 - Live 0xbf000000 (C)
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 ?? () from /lib/arm-linux-gnueabihf/libc.so.6
 raise () from /lib/arm-linux-gnueabihf/libc.so.6
 abort () from /lib/arm-linux-gnueabihf/libc.so.6
 OsAbort ()
 ddxGiveUp ()
Title: Xorg crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

version.compiz: compiz 1:0.9.9~daily13.02.08-0ubuntu1
version.libdrm2: libdrm2 2.4.42-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2
xserver.bootTime: Sat Jan 1 04:37:16 2000
xserver.configfile: None
xserver.devices:
 input gpio-keys KEYBOARD, id 6
 input elan-touchscreen TOUCHSCREEN, id 7
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output HDMI-1 LVDS-1
xserver.version: 2:1.13.2-0ubuntu2
xserver.video_driver: tegra

Revision history for this message
David Henningsson (diwic) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace:
 #0 <unavailable> in ?? ()
 PC not available
StacktraceSource: #0 <unavailable> in ?? ()
StacktraceTop: <unavailable> in ?? ()
ThreadStacktrace: PC not available

Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
summary: - Xorg crashed with SIGABRT in raise()
+ Xorg crashed with SIGABRT in <unavailable> in ??()
tags: removed: need-armhf-retrace
Timo Aaltonen (tjaalton)
information type: Private → Public
tags: added: mobile nexus7
Revision history for this message
Bryce Harrington (bryce) wrote :

Invalid stacktrace. (Yay proprietary drivers?)

Got steps to reproduce? Otherwise shall assume it dupish of bug #1126516

Changed in xorg-server (Ubuntu):
status: New → Incomplete
Revision history for this message
David Henningsson (diwic) wrote :

No, I didn't do any related action or such, just found the dialog box on the screen once.

I mean, the touch interface still hangs at times, but if that's related to this bug I don't know.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.