This bug was fixed in the package mesa - 18.2.8-0ubuntu0~18.04.2

mesa (18.2.8-0ubuntu0~18.04.2) bionic; urgency=medium

  * Backport to bionic.

mesa (18.2.8-0ubuntu0~18.10.2) cosmic; urgency=medium

  * i965-revert-enabling-softpin.diff: Don't enable softpin, causes
    issues on 32bit installs. (LP: #1815172)

mesa (18.2.8-0ubuntu0~18.04.1) bionic; urgency=medium

  * Backport to bionic.
  * intel-whl-aml-cfl-ids.diff: Dropped, upstream.

mesa (18.2.8-0ubuntu0~18.10.1) cosmic; urgency=medium

  * New upstream bugfix release. (LP: #1811225)
    - add missing gpu-id's. (LP: #1789924)
  * Cherry-picked from disco:
    Move KHR/khrplatform.h from libegl1-mesa-dev to mesa-common-dev
    because GL/glcorearb.h and GL/glext.h started to depend on this
    header too (Closes: #914167).

 -- Timo Aaltonen <>  Sat, 09 Feb 2019 00:02:44 +0200

** Changed in: mesa (Ubuntu Bionic)
       Status: Fix Committed => Fix Released

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06)         Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]    Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean:
   * dmesg too:
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to