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

Bug #1126516 reported by Jean Lucas
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Expired
High
Unassigned

Bug Description

When using multi-touch features such as 4-finger dash open, system goes into intensive stress and after ~10 seconds crashes and restarts Xorg, ending up at GDM. Too much stress freezes input (mouse/touch).

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
CrashCounter: 1
Date: Fri Feb 15 13:35:00 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:

InstallationDate: Installed on 2013-02-11 (4 days ago)
InstallationMedia: Ubuntu Raring Ringtail (development branch) - armhf (20130209-15:18)
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=015d24bc7d5c1006 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=4.13 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: Fri Feb 15 13:35:20 2013
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
Jean Lucas (nosebb) 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() (Nexus 7)
+ Xorg crashed with SIGABRT in <unavailable> in ??() (Nexus 7)
tags: removed: need-armhf-retrace
Bryce Harrington (bryce)
Changed in xorg-server (Ubuntu):
importance: Medium → Critical
Revision history for this message
Bryce Harrington (bryce) wrote :

Unfortunately the stack trace is invalid - perhaps the crash is in the tegra driver and so symbols aren't being shown because it is proprietary closed source code.

The Xorg.0.log.old has one hint:

[ 1219.331] (WW) TEGRA(0): LVDS-1: Error querying display modes: No such device.
[ 1362.827] (WW) TEGRA(0): LVDS-1: Error querying display modes: No such device.
[ 1575.289] (EE)
[ 1575.291] (EE) Backtrace:
[ 1575.296] (EE)
[ 1575.296] (EE) Segmentation fault at address 0x70
[ 1575.298]
Fatal server error:
[ 1575.298] Caught signal 11 (Segmentation fault). Server aborting

Address 0x70 looks like an invalid pointer.

Bryce Harrington (bryce)
information type: Private → Public
tags: added: mobile nexus7
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in xorg-server (Ubuntu):
status: New → Confirmed
Timo Aaltonen (tjaalton)
Changed in xorg-server (Ubuntu):
importance: Critical → High
status: Confirmed → New
Revision history for this message
Bryce Harrington (bryce) wrote :

Randomly touching nautilus with four fingers produced a spew of these to Xorg.0.log:

[ 136.919] (EE) BUG: triggered 'if (!(event->device_event.flags & (1 << 5)))'
[ 136.935] (EE) BUG: ../../dix/touch.c:628 in TouchConvertToPointerEvent()
[ 136.936] (EE) Non-emulating touch event
[ 136.937] (EE)

However, the X process isn't crashed or frozen.

Apart from that, I'm not reproducing the crash so far. I'll keep trying for a bit.

Meantime, if anyone else can reproduce the crash, please collect a backtrace manually, or shoot me a core dump.

Changed in xorg-server (Ubuntu):
status: New → Triaged
Revision history for this message
Bryce Harrington (bryce) wrote :

That message correlates to this code.

    BUG_WARN_MSG(!(event->device_event.flags & TOUCH_POINTER_EMULATED),
                 "Non-emulating touch event\n");

Not sure what it implies but seems to be "just" a warning.

Other than that, 4-finger tap appears to work fine for me. Any other suggestions for reproducing with the current code?

Changed in xorg-server (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
bugbot (bugbot) wrote :

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.

Changed in xorg-server (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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