Xorg crashed with SIGSEGV

Bug #1371973 reported by Lafa on 2014-09-20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)

Bug Description

I have a lenovo yoga pro 2 with intel chipset 3200x1800.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-core 2:1.16.0-1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2
Uname: Linux 3.16.0-16-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sat Sep 20 12:46:54 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xorg
ExtraDebuggingInterest: Yes, if not too technical
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3978]
InstallationDate: Installed on 2014-08-23 (28 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140822)
MachineType: LENOVO 20266
ProcCmdline: /usr/bin/X :0 -background none -noreset -verbose -auth /var/run/gdm/auth-for-gdm-9kac4P/database -seat seat0 -nolisten tcp vt7
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-16-generic.efi.signed root=UUID=38139456-4a6f-40d7-9a9d-1d58b22f9474 ro quiet splash vt.handoff=7
 Segfault happened at: 0x7fcf98b888ec: mov 0x10(%rdi),%rax
 PC (0x7fcf98b888ec) ok
 source "0x10(%rdi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xorg-server
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: Xorg crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)

dmi.bios.date: 10/31/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 76CN31WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Yoga2
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 Pro
dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
dmi.product.name: 20266
dmi.product.version: Lenovo Yoga 2 Pro
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
xserver.bootTime: Sat Sep 20 12:47:39 2014
xserver.configfile: default

xserver.logfile: /var/log/Xorg.0.log
 product id 16970
 vendor SDC
xserver.version: 2:1.16.0-1ubuntu1

Lafa (luis-alves) wrote :

 present_set_tree_pixmap (window=0x0, pixmap=0x7fcf9af421a0) at ../../present/present.c:378
 present_set_abort_flip (screen=0x7fcf9ad0e7d0) at ../../present/present.c:398
 present_flip_destroy (screen=screen@entry=0x7fcf9ad0e7d0) at ../../present/present.c:937
 present_close_screen (screen=0x7fcf9ad0e7d0) at ../../present/present_screen.c:60
 CursorCloseScreen (pScreen=0x7fcf9ad0e7d0) at ../../xfixes/cursor.c:187

Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Launchpad Janitor (janitor) wrote :

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

Changed in xorg-server (Ubuntu):
status: New → Confirmed
Jose Gómez (adler-dreamcoder) wrote :

My computer is a XPS 15, also with a resolution of 3200x1800.

Tim Ryder (ryder-tim) wrote :

I have the yoga pro 2 with the same issue. Is there a work around for this issue to avoid the lockups?

Chris Wilson (ickle) wrote :


Section "Device"
  Identifier "igfx"
  Option "DRI" "2"

Tim Ryder (ryder-tim) wrote :

Thank you.

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

Duplicates of this bug

Other bug subscribers