[nexus7] Xorg crashed with SIGABRT in <unavailable> in ??()

[Jean-Baptiste Lallement]

While running browsing tests (https://wiki.ubuntu.com/Nexus7/BrowsingSimulation), for the 3rd time in a row, X suddenly stopped responding and the display of the device froze.

The device is still alive though and usable through ssh.

(duplicate of bug 1111431 but with trace)

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: xserver-xorg-core 2:1.13.2-0ubuntu1
Uname: Linux 3.1.10-9-nexus7 armv7l
ApportVersion: 2.8-0ubuntu3
Architecture: armhf
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Thu Jan 31 14:02:05 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExecutableTimestamp: 1359553047
ExtraDebuggingInterest: Yes
GraphicsCard:

InstallationDate: Installed on 2012-12-07 (54 days ago)
InstallationMedia: Ubuntu Raring Ringtail (development branch) - armhf (20121207-15:18)
Lspci:

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

ProcKernelCmdLine: tegra_wdt.heartbeat=30 tegraid=30.1.3.0.0 mem=1022M@2048M android.commchip=0 vmalloc=128M androidboot.serialno=015d172c7308140c 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=30535679 androidboot.bootloader=3.34 root=/dev/mmcblk0p9 ro console=tty0 fbcon=rotate:1 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.01.25-0ubuntu1
version.libdrm2: libdrm2 2.4.41-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-0ubuntu1
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: Thu Jan 31 14:03:18 2013
xserver.devices:
 input gpio-keys KEYBOARD, id 6
 input elan-touchscreen TOUCHSCREEN, id 7
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output HDMI-1 LVDS-1
xserver.version: 2:1.13.2-0ubuntu1

[Apport retracing service (apport)]

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

[Launchpad Janitor (janitor)]

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

[Bryce Harrington (bryce)]

The EQ overflowing just means the GPU wasn't taking commands, that's a pretty generic error message when the display system fails.

Unfortunately the retracer isn't providing symbols to tell us where it crashed. Perhaps the next action for this is to repro the crash and connect to it with gdb manually to collect a stack trace. Install -dgb packages until all the stack symbols are shown, so probably xserver-xorg-core-dbg, libdrm*-dbg, maybe mesa dbg. If the error is in the video driver, you'd need tegra dbg symbols but since that's proprietary I don't think we have them.

[Jean-Baptiste Lallement (jibel)]

I've let the browser test run for half a day and excepted heavy rendering corruptions, no X crash so far. I'm setting the status of this report to 'Incomplete' until I can reproduce.

[bugbot (bugbot)]

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.

[Bryce Harrington (bryce)]

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1126516 is a similar (possibly dupe?) bug.