[Ubuntu-x-swat] [Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.

2020-04-01 Thread Daniel Llewellyn
OK, I've flipped it public. I had a browse through the attachments and
my untrained eye can't see anything glaringly secret, so have at it :-)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1869747

Title:
  Recent changes have caused Xorg to fail to start. Possibly nvidia
  driver related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1869882] Re: Xorg crashed with SIGABRT in __GI_raise()

2020-04-01 Thread Daniel Llewellyn
** Information type changed from Private to Public

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.net/bugs/1869882

Title:
  Xorg crashed with SIGABRT in __GI_raise()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1869882/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.

2020-04-01 Thread Daniel Llewellyn
There are two whoopsies that my system has submitted, too:

https://errors.ubuntu.com/oops/51e0231a-7138-11ea-98c4-fa163e102db1
https://errors.ubuntu.com/oops/5f9c714a-7352-11ea-aaf5-fa163e983629

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1869747

Title:
  Recent changes have caused Xorg to fail to start. Possibly nvidia
  driver related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.

2020-04-01 Thread Daniel Llewellyn
it's the correct reference, but I don't know whether it contains
sensitive info or not.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1869747

Title:
  Recent changes have caused Xorg to fail to start. Possibly nvidia
  driver related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.

2020-04-01 Thread Daniel Llewellyn
Possible smoking gun: removing `intel_iommu=on` from the grub
commandline successfully brings up gui desktop on boot.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1869747

Title:
  Recent changes have caused Xorg to fail to start. Possibly nvidia
  driver related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.

2020-03-31 Thread Daniel Llewellyn
It looks like the stacktrace mentions AMDGPU related functions. For the
record, I have three graphics devices in this box currently, one from
each vendor to allow easily testing apps on each: nVidia, AMD, and
Intel. The displays are currently only connected to the nVidia card's
outputs.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1869747

Title:
  Recent changes have caused Xorg to fail to start. Possibly nvidia
  driver related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1869747] Re: Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.

2020-03-31 Thread Daniel Llewellyn
I've submitted it as bug #1869882

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1869747

Title:
  Recent changes have caused Xorg to fail to start. Possibly nvidia
  driver related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1869747/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1869747] [NEW] Recent changes have caused Xorg to fail to start. Possibly nvidia driver related.

2020-03-30 Thread Daniel Llewellyn
Public bug reported:

I am unsure where the problem stems, but changes since the 25th have
caused my system to fail to initialise the Xorg display. The console
remains operational for debugging. I am currently using ZFS snapshots to
use the system as it was on the 25th of March 2020 because that is the
last snapshot before this issue.

This bug was captured using ubuntu-bug when booted into the broken (i.e.
not working) latest snapshot of my filesystem.

The versions of packages from the not broken (i.e. correctly working)
earlier snapshot of my filesystem are:

libnvidia-cfg1-440:amd64 440.64-0ubuntu2
libnvidia-common-440 440.64-0ubuntu2
libnvidia-compute-440:amd64  440.64-0ubuntu2
libnvidia-compute-440:i386   440.64-0ubuntu2
libnvidia-decode-440:amd64   440.64-0ubuntu2
libnvidia-decode-440:i386440.64-0ubuntu2
libnvidia-encode-440:amd64   440.64-0ubuntu2
libnvidia-encode-440:i386440.64-0ubuntu2
libnvidia-fbc1-440:amd64 440.64-0ubuntu2
libnvidia-fbc1-440:i386  440.64-0ubuntu2
libnvidia-gl-440:amd64   440.64-0ubuntu2
libnvidia-gl-440:i386440.64-0ubuntu2
libnvidia-ifr1-440:amd64 440.64-0ubuntu2
libnvidia-ifr1-440:i386  440.64-0ubuntu2
nvidia-compute-utils-440 440.64-0ubuntu2
nvidia-dkms-440  440.64-0ubuntu2
nvidia-driver-440440.64-0ubuntu2
nvidia-kernel-common-440 440.64-0ubuntu2
nvidia-kernel-source-440 440.64-0ubuntu2
nvidia-prime 0.8.14
nvidia-settings  440.64-0ubuntu1
nvidia-utils-440 440.64-0ubuntu2
xserver-xorg-video-nvidia-440440.64-0ubuntu2

$ lsb_release -rd
Description:Ubuntu Focal Fossa (development branch)
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-3ubuntu1)
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
Date: Mon Mar 30 15:49:12 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 440.64, 5.4.0-18-generic, x86_64: installed
ExtraDebuggingInterest: Yes
InstallationDate: Installed on 2020-03-03 (26 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=linux
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_7176ku@/vmlinuz-5.4.0-18-generic 
root=ZFS=rpool/ROOT/ubuntu_7176ku ro quiet splash intel_iommu=on vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F22g
dmi.board.asset.tag: Default string
dmi.board.name: Z170X-UD5 TH-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22g:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5TH:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5TH-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z170X-UD5 TH
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug champagne focal nvidia regression reproducible ubuntu

** Tags added: champagne

** Tags added: nvidia

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1869747

Title:
  

[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-01-30 Thread Daniel Llewellyn
both changes are now in upstream Xorg's repository, as PR388 was merged
a few hours ago. So the changes in this debdiff are a backport of those
to Bionic, Eoan and Focal (although if Focal were to sync with the
upstream code then the delta won't be necessary going forward).

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-01-30 Thread Daniel Llewellyn
The secondary crash doesn't occur without the first fix. You cannot
reach it until the first fix is applied. However, I suppose it is in a
different bit of code, but it is only reached when you use indirect GLX
and prevents you using indirect GLX which is what this issue is
attempting to fix.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-01-29 Thread Daniel Llewellyn
This debdiff for Focal fixes the follow-on crash (on client close) that
was unearthed by fixing the first crash (on client start).

** Patch added: "refreshed debdiff for focal"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323933/+files/xorg-server_1.20.6-1ubuntu2.debdiff

** Patch removed: "xorg-server-iglx.diff"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323631/+files/xorg-server-iglx.diff

** Patch removed: "debdiff for bionic"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323649/+files/xorg-server_1.19.6-1ubuntu4.4.debdiff

** Patch removed: "debdiff for eoan"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323650/+files/xorg-server_1.20.5+git20191008-0ubuntu2.debdiff

** Patch removed: "debdiff for focal"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323651/+files/xorg-server_1.20.6-1ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-01-29 Thread Daniel Llewellyn
The refreshed patches fix both crashes. The first change is upstream
commit e1fa3be [1] and the second change is from upstream PR 388 [2].

@Sponsors, this is now good to go from my point of view.

[1] 
https://gitlab.freedesktop.org/xorg/xserver/commit/e1fa3beb2fe2519e69f859f0acdc68e5a770de27
[2] https://gitlab.freedesktop.org/xorg/xserver/merge_requests/388

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-01-29 Thread Daniel Llewellyn
This debdiff for Eoan fixes the follow-on crash (on client close) that
was unearthed by fixing the first crash (on client start).

** Patch added: "refreshed debdiff for eoan"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323932/+files/xorg-server_1.20.5+git20191008-0ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-01-29 Thread Daniel Llewellyn
This debdiff for Bionic fixes the follow-on crash (on client close) that
was unearthed by fixing the first crash (on client start).

** Patch added: "refreshed debdiff for bionic"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323931/+files/xorg-server_1.19.6-1ubuntu4.4.debdiff

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-01-29 Thread Daniel Llewellyn
The new crash backtrace:

(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x7fb60370c899 in __GI_abort () at abort.c:79
#2  0x560aacd068c0 in OsAbort () at ../../../../os/utils.c:1351
#3  0x560aacd0c4f9 in AbortServer () at ../../../../os/log.c:879
#4  0x560aacd0d35a in FatalError (f=f@entry=0x560aacd40230 "Caught signal 
%d (%s). Server aborting\n") at ../../../../os/log.c:1017
#5  0x560aacd03c09 in OsSigHandler (unused=, 
sip=0x7ffd89b28470, signo=11) at ../../../../os/osinit.c:156
#6  OsSigHandler (signo=11, sip=0x7ffd89b28470, unused=) at 
../../../../os/osinit.c:110
#7  0x7fb6038ef540 in  () at 
/lib/x86_64-linux-gnu/libpthread.so.0
#8  0x560aacd02cf3 in ResetCurrentRequest 
(client=client@entry=0x560aae67f0c0) at ../../../../os/io.c:560
#9  0x560aacccfa66 in DRI2WaitSwap (client=0x560aae67f0c0, 
pDrawable=) at ../../../../../../hw/xfree86/dri2/dri2.c:1082
#10 0x7fb6033fa5f1 in __glXDRIcontextWait (baseContext=, 
cl=0x560aae67f1d8, error=0x7ffd89b28aa8) at ../../../../glx/glxdri2.c:291
#11 0x7fb6033f29c7 in __glXForceCurrent (cl=0x560aae67f1d8, 
tag=tag@entry=1, error=error@entry=0x7ffd89b28aa8) at 
../../../../glx/glxext.c:621
#12 0x7fb6033ee900 in xorgGlxMakeCurrent (client=0x560aae67f0c0, tag=1, 
drawId=, readId=0, contextId=, newContextTag=0) 
at ../../../../glx/glxcmds.c:616
#13 0x560aaccd378a in GlxFreeClientData (client=0x560aae67f0c0) at 
../../../../glx/vndext.c:168
#14 0x560aacba838c in _CallCallbacks (pcbl=pcbl@entry=0x560aacdb2538 
, call_data=call_data@entry=0x7ffd89b28b50) at 
../../../../dix/dixutils.c:743
#15 0x560aacba2273 in CallCallbacks (call_data=0x7ffd89b28b50, 
pcbl=0x560aacdb2538 ) at ../../../../include/callback.h:83
#16 CloseDownClient (client=0x560aae67f0c0) at ../../../../dix/dispatch.c:3473
#17 0x560aacd045f1 in ospoll_wait (ospoll=0x560aad403a10, 
timeout=) at ../../../../os/ospoll.c:651
#18 0x560aaccfd3b3 in WaitForSomething (are_ready=0) at 
../../../../os/WaitFor.c:208
#19 0x560aacba2ca7 in Dispatch () at ../../../../include/list.h:220
#20 0x560aacba6f94 in dix_main (argc=12, argv=0x7ffd89b299b8, 
envp=) at ../../../../dix/main.c:276
#21 0x7fb60370e1e3 in __libc_start_main (main=0x560aacb90a00 , 
argc=12, argv=0x7ffd89b299b8, init=, fini=, 
rtld_fini=, stack_end=0x7ffd89b299a8)
at ../csu/libc-start.c:308
#22 0x560aacb90a3e in _start ()

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-01-29 Thread Daniel Llewellyn
There are, thankfully, seemingly no regressions in unrelated areas :-)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-01-29 Thread Daniel Llewellyn
I've built this locally and tested it. While it improves matters, it is
still incomplete to get IGLX working fully - there is a new crash at the
point you close the IGLX-using application instead of immediately upon
starting it. This fix is still warranted, however, because it does
improve things. I'm going to go back to bisecting Xorg upstream to see
if I can identify the new crash.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Xorg's Indirect GLX broken from upstream regression

2020-01-28 Thread Daniel Llewellyn
** Summary changed:

- Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash
+ Xorg's Indirect GLX broken from upstream regression

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Xorg's Indirect GLX broken from upstream regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
** Patch removed: "re-rolled debdiff for focal"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323646/+files/xorg-server_1.20.6-1ubuntu2.debdiff

** Description changed:

  [Impact]
  
   * IGLX is a way for an opengl application sending the 3D drawing GLX
  commands to the Xorg server for rendering instead of using the DRI
  infrastructure it is commonplace for High Performance Compute and
  Scientific institutions to use this feature of the Xorg server. (ref:
  https://www.phoronix.com/scan.php?page=news_item=Xorg-IGLX-Potential-
  Bye-Bye)
  
   * The feature is completely broken, currently, and any attempt to use
  it will cause the Xorg server to crash. This feature has been broken
  since a commit upstream in 2016.
  
   * The attached patch is from the revert commit entered into the
  upstream repository on 28 Jan 2020 following a git bisect of the bug
  discovering the offending commit.
  
  [Test Case]
  
   * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the
  following contents:
  
  ```
  Section "ServerFlags"
  Option "IndirectGLX" "on"
  EndSection
  ```
  
   * Log out of your Xorg session
   * Switch to a VT (Ctrl+Alt+F2) and login
   * Run `sudo systemctl restart gdm` to restart Xorg
   * Login to the graphical session
   * If you do not have mesa-utils installed, then install it with the terminal 
command `sudo apt install mesa-utils`
   * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears`
   * If the fix is successful then glxgears should start and remain active 
without the Xorg server or glxgears crashing/segfaulting
  
  [Regression Potential]
  
   * This change is within DRI-related functionality and so might break
  all 3D accelerated applications.
  
   * There is a potential that the change is insufficient to fix the IGLX
  feature and so attempts to use it may still have undesirable and
  undefined results.
  
   * Upstream has run the patch through their CI system, which passed with
  no errors. This does not necessarily mean the patch will achieve the
  desired results, but at least indicates that the code does compile
  cleanly and can start an Xvfb headless instance.
  
  [Other Info]
  
-  * This bug affects Ubuntu releases all the way back to, and including,
- Xenial 16.04.
+  * This bug affects Ubuntu releases all the way back to, and including,
+ Bionic 18.04.
  
   Original Bug Report Follows 
  
  There's already an upstream bug report here:
  
  https://bugs.freedesktop.org/show_bug.cgi?id=99555
  
  Basically, with Option "IndirectGLX" "True" and LIBGL_ALWAYS_INDIRECT=1
  I get immediate crashes e.g. with glxgear:
  
  steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  X Error of failed request:  255
    Major opcode of failed request:  155 (GLX)
    Minor opcode of failed request:  1 (X_GLXRender)
    Serial number of failed request:  42
    Current serial number in output stream:  936
  
  I am trying to run what is effectively a traditional X Terminal, but as
  the hardware I am using has a 3D accelerated chipset it seems sensible
  to try to use it..
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Jun 12 10:09:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
   rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2018-05-31 (11 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: AZW S I
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/xubuntu--vg-root ro noresume
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 00.12
  dmi.board.asset.tag: Default string
  dmi.board.name: AB1
  dmi.board.vendor: IP3 Tech
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 35
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 

[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
** Patch added: "debdiff for focal"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323651/+files/xorg-server_1.20.6-1ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
** Patch added: "debdiff for eoan"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323650/+files/xorg-server_1.20.5+git20191008-0ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
** Attachment added: "debdiff for eoan"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323647/+files/xorg-server_1.20.5+git20191008-0ubuntu1.dsc

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
** Attachment removed: "debdiff for eoan"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323647/+files/xorg-server_1.20.5+git20191008-0ubuntu1.dsc

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
** Patch removed: "debdiff for focal"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323645/+files/xorg-server_1.20.6-1ubuntu2.debdiff

** Patch added: "re-rolled debdiff for focal"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323646/+files/xorg-server_1.20.6-1ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
** Patch added: "debdiff for focal"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323645/+files/xorg-server_1.20.6-1ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
** Description changed:

+ [Impact]
+ 
+  * IGLX is a way for an opengl application sending the 3D drawing GLX
+ commands to the Xorg server for rendering instead of using the DRI
+ infrastructure it is commonplace for High Performance Compute and
+ Scientific institutions to use this feature of the Xorg server. (ref:
+ https://www.phoronix.com/scan.php?page=news_item=Xorg-IGLX-Potential-
+ Bye-Bye)
+ 
+  * The feature is completely broken, currently, and any attempt to use
+ it will cause the Xorg server to crash. This feature has been broken
+ since a commit upstream in 2016.
+ 
+  * The attached patch is from the revert commit entered into the
+ upstream repository on 28 Jan 2020 following a git bisect of the bug
+ discovering the offending commit.
+ 
+ [Test Case]
+ 
+  * Create a new file at /etc/X11/xorg.conf.d/99-IGLX.conf with the
+ following contents:
+ 
+ ```
+ Section "ServerFlags"
+ Option "IndirectGLX" "on"
+ EndSection
+ ```
+ 
+  * Log out of your Xorg session
+  * Switch to a VT (Ctrl+Alt+F2) and login
+  * Run `sudo systemctl restart gdm` to restart Xorg
+  * Login to the graphical session
+  * If you do not have mesa-utils installed, then install it with the terminal 
command `sudo apt install mesa-utils`
+  * Open a terminal and execute `LIBGL_ALWAYS_INDIRECT=1 glxgears`
+  * If the fix is successful then glxgears should start and remain active 
without the Xorg server or glxgears crashing/segfaulting
+ 
+ [Regression Potential]
+ 
+  * This change is within DRI-related functionality and so might break
+ all 3D accelerated applications.
+ 
+  * There is a potential that the change is insufficient to fix the IGLX
+ feature and so attempts to use it may still have undesirable and
+ undefined results.
+ 
+  * Upstream has run the patch through their CI system, which passed with no 
errors. This does not necessarily mean the patch will achieve the desired 
results, but at least indicates that the code does compile cleanly and can 
start an Xvfb headless instance.
+  
+ [Other Info]
+ 
+  Original Bug Report Follows 
+ 
  There's already an upstream bug report here:
  
  https://bugs.freedesktop.org/show_bug.cgi?id=99555
  
  Basically, with Option "IndirectGLX" "True" and LIBGL_ALWAYS_INDIRECT=1
  I get immediate crashes e.g. with glxgear:
  
- steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears 
+ steved@xubuntu:~$ LIBGL_ALWAYS_INDIRECT=true glxgears
  Running synchronized to the vertical refresh.  The framerate should be
  approximately the same as the monitor refresh rate.
  X Error of failed request:  255
-   Major opcode of failed request:  155 (GLX)
-   Minor opcode of failed request:  1 (X_GLXRender)
-   Serial number of failed request:  42
-   Current serial number in output stream:  936
+   Major opcode of failed request:  155 (GLX)
+   Minor opcode of failed request:  1 (X_GLXRender)
+   Serial number of failed request:  42
+   Current serial number in output stream:  936
  
  I am trying to run what is effectively a traditional X Terminal, but as
  the hardware I am using has a 3D accelerated chipset it seems sensible
  to try to use it..
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-core 2:1.19.6-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Tue Jun 12 10:09:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
-  rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
-  rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
+  rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-22-generic, x86_64: installed
+  rtl8812au, 4.3.8.12175.20140902+dfsg, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
-Subsystem: Intel Corporation Device [8086:2212]
+  Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
+    Subsystem: Intel Corporation Device [8086:2212]
  InstallationDate: Installed on 2018-05-31 (11 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: AZW S I
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=/dev/mapper/xubuntu--vg-root ro noresume
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 00.12
  dmi.board.asset.tag: Default string
  dmi.board.name: AB1
  dmi.board.vendor: IP3 Tech
  dmi.board.version: 

[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
This is the upstream patch. It changes the return from
__glXDRIcontextWait from hardcoded -1 to noClientException which will
either be -1 or nothing. This is the pre-2016 behaviour that is being
restored.

** Patch added: "xorg-server-iglx.diff"
   
https://bugs.launchpad.net/xorg-server/+bug/1776447/+attachment/5323631/+files/xorg-server-iglx.diff

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
A fix has now landed upstream. I think this could be a candidate for an
SRU cherry-pick for every supported release back to Xenial. The upstream
commit is
https://gitlab.freedesktop.org/xorg/xserver/commit/e1fa3beb2fe2519e69f859f0acdc68e5a770de27.
It's a very simple one-line change and is merely a revert of a prior
upstream commit.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
** Tags added: disco eoan

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1776447] Re: Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to crash

2020-01-28 Thread Daniel Llewellyn
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #211
   https://gitlab.freedesktop.org/xorg/xserver/issues/211

** Changed in: xorg-server
   Importance: Medium => Unknown

** Changed in: xorg-server
 Remote watch: freedesktop.org Bugzilla #99555 => 
gitlab.freedesktop.org/xorg/xserver/issues #211

** Tags added: focal

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1776447

Title:
  Indirect GLX (LIBGL_ALWAYS_INDIRECT=1) causes opengl programms to
  crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1776447/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1820074] Re: Running glxgears with Indirect GLX crashes Xorg

2019-04-07 Thread Daniel Llewellyn
Also affects Disco

** Tags added: disco

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1820074

Title:
  Running glxgears with Indirect GLX crashes Xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1820074] [NEW] Running glxgears with Indirect GLX crashes Xorg

2019-03-14 Thread Daniel Llewellyn
Public bug reported:

Replication Steps
-

sudo mv /usr/bin/Xorg /usr/bin/Xorg.real
echo 

[Ubuntu-x-swat] [Bug 1820074] Re: Running glxgears with Indirect GLX crashes Xorg

2019-03-14 Thread Daniel Llewellyn
The crash is in XorgLogOld.txt, and the backtrace reproduced here:

[  9027.274] (EE) Backtrace:
[  9027.274] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b9210ba229]
[  9027.275] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) 
[0x7fdf6dcc4e1f]
[  9027.275] (EE) 2: /usr/lib/xorg/Xorg (ResetCurrentRequest+0xb) 
[0x55b9210b92ab]
[  9027.275] (EE) 3: /usr/lib/xorg/Xorg (DRI2WaitSwap+0x56) [0x55b921086716]
[  9027.275] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  9027.275] (EE) 4: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) 
[0x7fdf6c7faa20]
[  9027.276] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  9027.276] (EE) 5: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) 
[0x7fdf6c7f3010]
[  9027.276] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  9027.276] (EE) 6: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) 
[0x7fdf6c7eefd0]
[  9027.276] (EE) 7: /usr/lib/xorg/Xorg (dri3_send_open_reply+0xe2a) 
[0x55b92108b12a]
[  9027.277] (EE) 8: /usr/lib/xorg/Xorg (_CallCallbacks+0x34) [0x55b920f60be4]
[  9027.277] (EE) 9: /usr/lib/xorg/Xorg (CloseDownClient+0x5f) [0x55b920f5acbf]
[  9027.277] (EE) 10: /usr/lib/xorg/Xorg (OsCleanup+0x591) [0x55b9210bb021]
[  9027.277] (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1c3) 
[0x55b9210b3b93]
[  9027.277] (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x10c) 
[0x55b920f5b72c]
[  9027.277] (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x55b920f5f906]
[  9027.278] (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) 
[0x7fdf6daea09b]
[  9027.278] (EE) 15: /usr/lib/xorg/Xorg (_start+0x2a) [0x55b920f4967a]
[  9027.278] (EE) 
[  9027.278] (EE) Segmentation fault at address 0x8
[  9027.278] (EE) 
Fatal server error:
[  9027.278] (EE) Caught signal 11 (Segmentation fault). Server aborting

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1820074

Title:
  Running glxgears with Indirect GLX crashes Xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1820074] Re: Running glxgears with Indirect GLX crashes Xorg

2019-03-14 Thread Daniel Llewellyn
Also crashes with nVidia using nouveau drivers (see attached log)

** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+attachment/5246195/+files/Xorg.0.log.old

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1820074

Title:
  Running glxgears with Indirect GLX crashes Xorg

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1820074/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1752863] [NEW] libgl1 and libgl1-mesa-glx both provide libGL.so.1

2018-03-02 Thread Daniel Llewellyn
Public bug reported:

TJ in #ubuntu+1 suggested filing this as a bug.

libgl1 from source package libglvnd and libgl1-mesa-glx from source
package mesa both provide /usr/lib//libGL.so.1

root@u1804:~# apt-file list libgl1

libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1
libgl1: /usr/lib/x86_64-linux-gnu/libGL.so.1.0.0
libgl1: /usr/share/bug/libgl1/control
libgl1: /usr/share/doc/libgl1/changelog.Debian.gz
libgl1: /usr/share/doc/libgl1/copyright

root@u1804:~# apt-file list libgl1-mesa-glx

libgl1-mesa-glx: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
libgl1-mesa-glx: /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1
libgl1-mesa-glx: /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2.0
libgl1-mesa-glx: /usr/share/bug/libgl1-mesa-glx/control
libgl1-mesa-glx: /usr/share/bug/libgl1-mesa-glx/script
libgl1-mesa-glx: /usr/share/doc/libgl1-mesa-glx/changelog.Debian.gz
libgl1-mesa-glx: /usr/share/doc/libgl1-mesa-glx/copyright
libgl1-mesa-glx: /usr/share/lintian/overrides/libgl1-mesa-glx

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgl1 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  2 12:54:46 2018
InstallationDate: Installed on 2017-12-01 (91 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
SourcePackage: libglvnd
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libglvnd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libglvnd in Ubuntu.
https://bugs.launchpad.net/bugs/1752863

Title:
  libgl1 and libgl1-mesa-glx both provide libGL.so.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1752863/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1752111] Re: Xorg on Bionic doesn't start anymore

2018-03-01 Thread Daniel Llewellyn
*** This bug is a duplicate of bug 1752053 ***
https://bugs.launchpad.net/bugs/1752053

** This bug is no longer a duplicate of bug 1752307
   incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf
** This bug has been marked a duplicate of bug 1752053
   nvidia-390 fails to boot graphical display

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1752111

Title:
  Xorg on Bionic doesn't start anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752111/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

2018-03-01 Thread Daniel Llewellyn
*** This bug is a duplicate of bug 1752053 ***
https://bugs.launchpad.net/bugs/1752053

** This bug has been marked a duplicate of bug 1752053
   nvidia-390 fails to boot graphical display

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1752307

Title:
  incompatible configuration in default nvidia-drm-outputclass-
  ubuntu.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752307/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1752111] Re: Xorg on Bionic doesn't start anymore

2018-03-01 Thread Daniel Llewellyn
*** This bug is a duplicate of bug 1752307 ***
https://bugs.launchpad.net/bugs/1752307

** This bug has been marked a duplicate of bug 1752307
   incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1752111

Title:
  Xorg on Bionic doesn't start anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752111/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

2018-03-01 Thread Daniel Llewellyn
** Tags removed: single-occurrence

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1752307

Title:
  incompatible configuration in default nvidia-drm-outputclass-
  ubuntu.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752307/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

2018-03-01 Thread Daniel Llewellyn
** Description changed:

-  Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
+ Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
  I rebooted and i get a black screen before the login screen I am unable to 
login.
  Thanks.
+ 
+ --
+ Added by diddledan:
+ --
+ From the log file:
+ Parse error on line 5 of section OutputClass in file 
/usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf
+   "Option" is not a valid keyword in this section.
+ 
+ Commenting out this line proceeds to alert about the next line which is
+ also an "Option" line, and commenting that out moves the alert onto the
+ final line before EndSection. Commenting all three offending lines fixes
+ this particular issue.
+ 
+ On diddledan's system, which may be an anomaly, Xorg then complains that 
libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so.
+ --
+ End added by diddledan
+ --
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
-  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
+  NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.25  Wed Jan 24 20:02:43 
PST 2018
+  GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1)
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Wed Feb 28 04:47:12 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.25, 4.15.0-10-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  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]
+  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: Hewlett-Packard h8-1559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=e7617605-fdbe-4cb6-9e67-00f9c8f45de2 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: v8.10
  dmi.board.name: 2AC8
  dmi.board.vendor: Gigabyte
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: MXX30503QF
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvrv8.10:bd12/03/2012:svnHewlett-Packard:pnh8-1559:pvr:rvnGigabyte:rn2AC8:rvr1.2:cvnHewlett-Packard:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: h8-1559
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu1
  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+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Description changed:

  Ubuntu 18.04. After xorg and nvidia proprietary drivers upgrades.
  I rebooted and i get a black screen before the login screen I am unable to 
login.
  Thanks.
  
  --
  Added by diddledan:
  --
  From the log file:
  Parse error on line 5 of section OutputClass in file 
/usr/share/X11/xorg.conf.d/nvidia-drm-outputclass-ubuntu.conf
-   "Option" is not a valid keyword in this section.
+  "Option" is not a valid keyword in this section.
  
  Commenting out this line proceeds to alert about the next line which is
  also an "Option" line, and commenting that out moves the alert onto the
- final line before EndSection. Commenting all three offending lines fixes
- this particular issue.
+ final line, "ModulePath", before EndSection. Commenting all three
+ offending lines fixes this particular issue.
  
  On diddledan's system, which may be an anomaly, Xorg then complains that 
libGL.so.1 is missing while loading /usr/lib/xorg/modules/extensions/libglx.so.
  --
  End added by diddledan
  --
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: 

[Ubuntu-x-swat] [Bug 1752307] Re: incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

2018-03-01 Thread Daniel Llewellyn
** Summary changed:

- xorg
+ incompatible configuration in default nvidia-drm-outputclass-ubuntu.conf

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1752307

Title:
  incompatible configuration in default nvidia-drm-outputclass-
  ubuntu.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752307/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1360997] [NEW] GPU lockup IPEHR: 0x0a200001 IPEHR: 0x01000000

2014-08-24 Thread Daniel Llewellyn
Public bug reported:

occurs more often with a video file playing, such as google-
chrome+youtube or alternatively with a local file in totem.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1
Uname: Linux 3.16.0-10-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
BootLog:
 * Setting up X socket directories...    
[ OK ]
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Aug 25 04:27:44 2014
DistUpgraded: 2014-08-18 04:28:17,817 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.248+bdcom, 3.16.0-10-generic, x86_64: installed
 bcmwl, 6.30.223.248+bdcom, 3.16.0-9-generic, x86_64: installed
DuplicateSignature: GPU lockup  IPEHR: 0x0a21 IPEHR: 0x0100 Ubuntu 14.10
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:0102]
InstallationDate: Installed on 2014-08-05 (19 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
InterpreterPath: /usr/bin/python3.4
MachineType: Apple Inc. MacBookPro10,2
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-10-generic.efi.signed 
root=UUID=eca02eb6-1634-48e4-bf09-356a0e64c873 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.7+1ubuntu8
 libdrm2  2.4.56-1
 xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1
SourcePackage: xserver-xorg-video-intel
SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
Title: GPU lockup  IPEHR: 0x0a21 IPEHR: 0x0100
UpgradeStatus: Upgraded to utopic on 2014-08-18 (7 days ago)
UserGroups:
 
dmi.bios.date: 11/16/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP102.88Z.0106.B03.1211161133
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-AFD8A9D944EA4843
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-AFD8A9D944EA4843
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP102.88Z.0106.B03.1211161133:bd11/16/2012:svnAppleInc.:pnMacBookPro10,2:pvr1.0:rvnAppleInc.:rnMac-AFD8A9D944EA4843:rvrMacBookPro10,2:cvnAppleInc.:ct10:cvrMac-AFD8A9D944EA4843:
dmi.product.name: MacBookPro10,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
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.15.1-0ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Aug 25 02:45:02 2014
xserver.configfile: default
xserver.errors:
 intel: Failed to load module dri3 (module does not exist, 0)
 intel: Failed to load module present (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 286 
 vendor SAM
xserver.version: 2:1.15.1-0ubuntu9

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash compiz-0.9 freeze ubuntu utopic

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1360997

Title:
  GPU lockup  IPEHR: 0x0a21 IPEHR: 0x0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1360997/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1360997] Re: GPU lockup IPEHR: 0x0a200001 IPEHR: 0x01000000

2014-08-24 Thread Daniel Llewellyn
possibly duplicates bug #1358357

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1360997

Title:
  GPU lockup  IPEHR: 0x0a21 IPEHR: 0x0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1360997/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1358357] Re: False GPU lockup IPEHR: 0x0a080001

2014-08-24 Thread Daniel Llewellyn
possibly duplicated by #1360997

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1358357

Title:
  False GPU lockup  IPEHR: 0x0a080001

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1358357/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1358357] Re: False GPU lockup IPEHR: 0x0a080001

2014-08-24 Thread Daniel Llewellyn
reposting the possible duplicate bug number for launchpad to link it:
bug #1360997

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1358357

Title:
  False GPU lockup  IPEHR: 0x0a080001

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1358357/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1358357] [NEW] False GPU lockup IPEHR: 0x0a080001

2014-08-18 Thread Daniel Llewellyn
Public bug reported:

I'm not sure whether this is a false lockup or not. The display became
unresponsive for maybe a second or two and then was back to life again
followed by the apport message.

Not sure what else I can provide information-wise other than this is a retina 
macbook pro early 2013 model with intel IGP 3rd Gen Core processor Graphics 
Controller (rev 09).
I have several usb devices hook-ed up:
- wireless is turned-on and associated with a network
- I have a display-port-to-vga adapter connected to one monitor and an 
hdmi-to-dvi adapter connected to another
- finally I also have a thunderbolt ethernet adapter plugged-in.

(my wireless adapter is the inbuilt broadcom 4331 running with
proprietary drivers.)

There should be plenty of attached debugging information from apport I
hope which might help better diagnose the problem than I can describe
it. It seems to be happening randomly and sporadically. I've had two
such notifications of GPU lockups today in the past 8 hours, which makes
it difficult to understand how one might reproduce the issue on-demand.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.5-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Aug 18 14:51:37 2014
DistUpgraded: 2014-08-18 04:28:17,817 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.16.0-9-generic, x86_64: installed
DuplicateSignature: GPU lockup  IPEHR: 0x0a080001 Ubuntu 14.10
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:0102]
InstallationDate: Installed on 2014-08-05 (12 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
InterpreterPath: /usr/bin/python3.4
MachineType: Apple Inc. MacBookPro10,2
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-9-generic.efi.signed 
root=UUID=eca02eb6-1634-48e4-bf09-356a0e64c873 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.7+1ubuntu8
 libdrm2  2.4.56-1
 xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1
SourcePackage: xserver-xorg-video-intel
SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli'
Title: False GPU lockup  IPEHR: 0x0a080001
UpgradeStatus: Upgraded to utopic on 2014-08-18 (0 days ago)
UserGroups:
 
dmi.bios.date: 11/16/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP102.88Z.0106.B03.1211161133
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-AFD8A9D944EA4843
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-AFD8A9D944EA4843
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP102.88Z.0106.B03.1211161133:bd11/16/2012:svnAppleInc.:pnMacBookPro10,2:pvr1.0:rvnAppleInc.:rnMac-AFD8A9D944EA4843:rvrMacBookPro10,2:cvnAppleInc.:ct10:cvrMac-AFD8A9D944EA4843:
dmi.product.name: MacBookPro10,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.5-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.5-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Aug 18 07:00:03 2014
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 286 
 vendor SAM
xserver.version: 2:1.15.1-0ubuntu9

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash compiz-0.9 false-gpu-hang freeze 
need-duplicate-check ubuntu utopic

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1358357

Title:
  False GPU lockup  IPEHR: 0x0a080001

To manage notifications about this bug go to:

[Ubuntu-x-swat] [Bug 1358357] Re: False GPU lockup IPEHR: 0x0a080001

2014-08-18 Thread Daniel Llewellyn
jsut happened again. Everything remained functional but google-chrome
hung hard and required force-quiting (I was watching the ubuntu-on-air
broadcast at the time)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1358357

Title:
  False GPU lockup  IPEHR: 0x0a080001

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1358357/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1358357] Re: False GPU lockup IPEHR: 0x0a080001

2014-08-18 Thread Daniel Llewellyn
this might be possibly related to flash player being active in chrome.
it certainly seems to happen when I'm actively using chrome (from
google's repo) and often times seems to hang up the chrome process to
the extent that I need to force-quit it.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1358357

Title:
  False GPU lockup  IPEHR: 0x0a080001

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1358357/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1284082] [NEW] False GPU lockup IPEHR: 0x0a200001

2014-02-24 Thread Daniel Llewellyn
Public bug reported:

no apparent visible symptoms.

apport alerted me to the detected problem, so I've uploaded my logs. I
have no idea how to replicate or what may work around the issue.

This is on a retina MacBook Pro from February 2013 stock.

May be relevant - I boot the system using EFI via grub-efi rather than
BIOS emulation mode.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
Uname: Linux 3.13.0-11-generic x86_64
NonfreeKernelModules: wl
.tmp.unity.support.test.0:

ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Feb 24 10:35:55 2014
DistUpgraded: 2014-02-24 09:39:33,948 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.141+bdcom, 3.11.0-17-generic, x86_64: installed
 bcmwl, 6.30.223.141+bdcom, 3.13.0-11-generic, x86_64: installed
DuplicateSignature: GPU lockup  IPEHR: 0x0a21 Ubuntu 14.04
ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. Device [106b:0102]
InstallationDate: Installed on 2014-02-24 (0 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
InterpreterPath: /usr/bin/python3.4
MachineType: Apple Inc. MacBookPro10,2
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-11-generic.efi.signed 
root=UUID=068d2195-2a23-4cf9-82ac-b695a1c8bd21 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 xserver-xorg 1:7.7+1ubuntu8
 libdrm2  2.4.52-1
 xserver-xorg-video-intel 2:2.99.910-0ubuntu1
SourcePackage: xserver-xorg-video-intel
Title: False GPU lockup  IPEHR: 0x0a21
UpgradeStatus: Upgraded to trusty on 2014-02-24 (0 days ago)
UserGroups:

dmi.bios.date: 11/16/2012
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP102.88Z.0106.B03.1211161133
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-AFD8A9D944EA4843
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro10,2
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-AFD8A9D944EA4843
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP102.88Z.0106.B03.1211161133:bd11/16/2012:svnAppleInc.:pnMacBookPro10,2:pvr1.0:rvnAppleInc.:rnMac-AFD8A9D944EA4843:rvrMacBookPro10,2:cvnAppleInc.:ct10:cvrMac-AFD8A9D944EA4843:
dmi.product.name: MacBookPro10,2
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Feb 24 11:53:21 2014
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 286
 vendor SAM
xserver.version: 2:1.15.0-1ubuntu6

** Affects: xserver-xorg-video-intel (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash compiz-0.9 false-gpu-hang freeze trusty ubuntu

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1284082

Title:
  False GPU lockup  IPEHR: 0x0a21

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1284082/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1284082] Re: False GPU lockup IPEHR: 0x0a200001

2014-02-24 Thread Daniel Llewellyn
*** This bug is a duplicate of bug 1274779 ***
https://bugs.launchpad.net/bugs/1274779

** Description changed:

  no apparent visible symptoms.
  
  apport alerted me to the detected problem, so I've uploaded my logs. I
  have no idea how to replicate or what may work around the issue.
+ 
+ This is on a retina MacBook Pro from February 2013 stock.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb 24 10:35:55 2014
  DistUpgraded: 2014-02-24 09:39:33,948 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
-  bcmwl, 6.30.223.141+bdcom, 3.11.0-17-generic, x86_64: installed
-  bcmwl, 6.30.223.141+bdcom, 3.13.0-11-generic, x86_64: installed
+  bcmwl, 6.30.223.141+bdcom, 3.11.0-17-generic, x86_64: installed
+  bcmwl, 6.30.223.141+bdcom, 3.13.0-11-generic, x86_64: installed
  DuplicateSignature: GPU lockup  IPEHR: 0x0a21 Ubuntu 14.04
  ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: Apple Inc. Device [106b:0102]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: Apple Inc. Device [106b:0102]
  InstallationDate: Installed on 2014-02-24 (0 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Apple Inc. MacBookPro10,2
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py
  ProcEnviron:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-11-generic.efi.signed 
root=UUID=068d2195-2a23-4cf9-82ac-b695a1c8bd21 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
-  xserver-xorg 1:7.7+1ubuntu8
-  libdrm2  2.4.52-1
-  xserver-xorg-video-intel 2:2.99.910-0ubuntu1
+  xserver-xorg 1:7.7+1ubuntu8
+  libdrm2  2.4.52-1
+  xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  SourcePackage: xserver-xorg-video-intel
  Title: False GPU lockup  IPEHR: 0x0a21
  UpgradeStatus: Upgraded to trusty on 2014-02-24 (0 days ago)
  UserGroups:
-  
+ 
  dmi.bios.date: 11/16/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP102.88Z.0106.B03.1211161133
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-AFD8A9D944EA4843
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-AFD8A9D944EA4843
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP102.88Z.0106.B03.1211161133:bd11/16/2012:svnAppleInc.:pnMacBookPro10,2:pvr1.0:rvnAppleInc.:rnMac-AFD8A9D944EA4843:rvrMacBookPro10,2:cvnAppleInc.:ct10:cvrMac-AFD8A9D944EA4843:
  dmi.product.name: MacBookPro10,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Feb 24 11:53:21 2014
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id 286 
-  vendor SAM
+  product id 286
+  vendor SAM
  xserver.version: 2:1.15.0-1ubuntu6

** Description changed:

  no apparent visible symptoms.
  
  apport alerted me to the detected problem, so I've uploaded my logs. I
  have no idea how to replicate or what may work around the issue.
  
  This is on a retina MacBook Pro from February 2013 stock.
+ 
+ May be relevant - I boot the system using EFI via grub-efi rather than
+ BIOS emulation mode.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1