Xorg crashed with SIGABRT in glamor_make_current()

Bug #1742612 reported by Chris Halse Rogers
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
xorg-server (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

X crashes when logging into a KDE or GNOME Shell session; the SDDM greeter doesn't tickle the relevant codepath. Similarly, starting X and running xterm against works fine.

It seems that glamor_priv is being unset somewhere?

This is entirely reproducible, and didn't occur in 17.10.

This system is somewhat weird, in that it's got both a Radeon and an NVIDIA card active in it, with displays connected to both.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: xserver-xorg-core 2:1.19.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0+bcachefs.git20180105.67e9882d-1-generic 4.13.13
Uname: Linux 4.13.0+bcachefs.git20180105.67e9882d-1-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
Date: Wed Jan 10 17:23:11 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn XT [Radeon HD 7870 GHz Edition] [1002:6818] (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Pitcairn XT [Radeon HD 7870 GHz Edition] [1458:2554]
 NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GM107 [GeForce GTX 750 Ti] [1043:84bb]
MachineType: System manufacturer System Product Name
ProcCmdline: /usr/lib/xorg/Xorg -nolisten tcp -auth /var/run/sddm/{d1b73357-b856-41a6-8073-0a4d2de13cc3} -background none -noreset -displayfd 17 vt7
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0+bcachefs.git20180105.67e9882d-1-generic root= ro quiet splash vt.handoff=7 break=mount
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 glamor_make_current (glamor_priv=0x0) at ../../../../glamor/glamor_utils.h:726
 glamor_block_handler (screen=0x55f93f2b9140) at ../../../../glamor/glamor.c:258
 radeon_cs_flush_indirect (pScrn=0x55f93f2bcb90) at ../../src/radeon_kms.c:108
 redisplay_dirty (dirty=0x55f93f3a3570, region=0x55f93f873220) at ../../src/radeon_kms.c:585
 radeon_dirty_update (scrn=0x55f93f2bc1f0) at ../../src/radeon_kms.c:884
Title: Xorg crashed with SIGABRT in glamor_make_current()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/05/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1904
dmi.board.asset.tag: Default string
dmi.board.name: Z170 PRO GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1904:bd07/05/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.89-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

Revision history for this message
Chris Halse Rogers (raof) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007f1c0ea8f0bb in ?? ()
 #1 0x000000000a392400 in ?? ()
 #2 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for perl-base
no debug symbol package found for perl-base

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Chris Halse Rogers (raof) wrote :

Oh, ignore the retracer. It's just complaining that the stacktrace is from my -O0 nostrip build. The attached stacktrace is fully symbolic.

Changed in xorg-server (Ubuntu):
status: Invalid → New
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
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.