[bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Mesa |
Fix Released
|
Medium
|
||
| linux (Ubuntu) |
Medium
|
Unassigned | ||
| Bionic |
Medium
|
Timo Aaltonen | ||
| Cosmic |
Medium
|
Unassigned | ||
| mesa (Ubuntu) |
Medium
|
Unassigned | ||
| Bionic |
High
|
Timo Aaltonen | ||
| Cosmic |
Medium
|
Timo Aaltonen |
Bug Description
[Impact]
Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-
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: https:/
* dmesg too: https:/
* 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)
CVE References
Changed in mesa (Ubuntu Bionic): | |
assignee: | nobody → Timo Aaltonen (tjaalton) |
Changed in mesa (Ubuntu Cosmic): | |
assignee: | nobody → Timo Aaltonen (tjaalton) |
Hello Alkis, thank you for the report.
Do you know, what kernel version was used on those machines? It might be helpful also.
I have HD 520 graphic card, quite close to mentioned by you, so can try to reproduce
Thank you Denis,
I tried with the following Ubuntu-built kernels, all having the issue:
4.15.0-45, 4.15.0-44, 4.15.0-20.
It happens on both 32bit and 64bit installations.
The failed units logs are:
systemctl status gpu-manager: https:/
systemctl status lightdm: https:/
lightdm.log: https:/
The weird part is that I don't see xorg segfaults or /var/crash/* reports or anything, the only error I got was that xinit line that I mentioned, "i965: Failed to submit batchbuffer: Invalid argument"
I have the `lspci` results from 4 schools so far, they're all 8086:1912 (HD Graphics 530), although from different vendors, ASUS, Dell etc.
The Ubuntu folks uploaded 18.3.3 in their ppa:ubuntu-
|
#5 |
Can you please:
$ echo 0xf > /sys/modules/
$ xinit
$ echo 0 > /sys/modules/
$ dmesg > dmesg.txt # and upload
Hopefully we remembered to tag the EINVAL.
I used "/sys/module" instead of "/sys/modules":
$ echo 0xf /sys/module/
$ xinit
i965: Failed to submit batchbuffer: Invalid argument
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
$ echo 0 /sys/module/
$ dmesg | nc termbin.com 9999
I don't see any additional messages though...
Sorry, I forgot the >
Here's the correct log:
https:/
|
#8 |
(In reply to Chris Wilson from comment #4)
> Hopefully we remembered to tag the EINVAL.
[ 1494.995482] [drm:drm_ioctl [drm]] pid=2746, dev=0xe200, auth=1, DRM_IOCTL_
[ 1494.995493] [drm:drm_ioctl [drm]] pid=2746, dev=0xe200, auth=1, DRM_IOCTL_
[ 1494.995584] [drm:drm_ioctl [drm]] pid=2746, dev=0xe200, auth=1, I915_GEM_
[ 1494.995595] [drm:drm_ioctl [drm]] ret = -22
That'll be no then.
Changed in mesa: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
I just tried with 4.18.0-14-generic, the same issue happens there as well.
And, another school reported the issue on HD Graphics 630:
root@pc02:~# lspci -nn -k | grep -A 2 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] Kernel driver in use: i915
one theory is that this is related to legacy bios boot
Hello, Alkis.
Could you, please, try to use a kernel not less than v4.19.3?
And could you provide outputs of
/usr/bin/glxinfo -B
file /usr/bin/glxinfo
uname -a
Hello Sergii,
I tried with 4.20.7 and it appears to work fine! Thanks!
Output of the commands:
# uname -a
Linux srv-6gym-chalk 4.20.7-
# file /usr/bin/glxinfo
/usr/bin/glxinfo: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 3.2.0, BuildID[
# glxinfo -B
name of display: :0
display: :0 screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) x86/MMX/SSE2 (0x1912)
Version: 18.3.3
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) x86/MMX/SSE2
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.3
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL version string: 3.0 Mesa 18.3.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.3.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
< I tried with 4.20.7 and it appears to work fine! Thanks!
You are welcome :)
So closing?
I don't know the software stacks involved:
If I understood it correctly,
mesa 18.3.3 doesn't work with older kernels while 18.0 did work,
and so I'll do a bisection to see which kernel commit fixes the issue,
and then distro kernel maintainers may cherrypick it for older kernels.
If there's no need for mesa to work with older kernels without the cherrypicked commit, then I guess yes, this issue should be closed, in which case please close it for me or tell me to close it.
Thanks again!
Most likely mesa were broken with commit:
commit a363bb2cd0e2a14
Author: Kenneth Graunke <email address hidden>
Date: Tue Apr 10 01:18:25 2018 -0700
i965: Allocate VMA in userspace for full-PPGTT systems.
In the kernel (especially 32-bit) it requires such commits (all of them are present from kernel 4.19.3):
1. commit 0014868b9c3c1dd
Author: Chris Wilson <email address hidden>
Date: Fri Nov 2 16:12:09 2018 +0000
drm/i915: Mark pin flags as u64
2. commit 085603287452fc9
Author: Chris Wilson <email address hidden>
Date: Thu Oct 25 10:18:23 2018 +0100
drm/i915: Compare user's 64b GTT offset even on 32b
3. commit c58281056a8b26d
Author: Chris Wilson <email address hidden>
Date: Thu Oct 25 10:18:22 2018 +0100
drm/i915: Mark up GTT sizes as u64
4. commit 83b466b1dc5f0b4
Author: Chris Wilson <email address hidden>
Date: Fri Nov 2 16:12:09 2018 +0000
drm/i915: Mark pin flags as u64
5. commit 6fc4e48f9ed46e9
Author: Chris Wilson <email address hidden>
Date: Thu Oct 25 10:18:23 2018 +0100
drm/i915: Compare user's 64b GTT offset even on 32b
So its question to Chris if he could propagate such commits into kernel. Because looks like even 4.15 is commonly used still.
I tried a small kernel bisection using the ubuntu kernel binaries,
4.19.2-
4.19.3-041903=works
this is caused by enabling softpin in mesa, which is supported in kernel 4.5 and up but is still somewhat buggy as seen here.. we need these commits backported to the kernel:
9125963a9494253
6fc4e48f9ed46e9
but since 18.04.2 is about to be released, it's best to revert enabling softpin in mesa, and enable it again for 18.04.3.
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
4.15 is EOL upstream, but Canonical does pull patches from stable to the distro kernel in 18.04, I'm not sure why these never got in.. probably didn't apply cleanly.
anyway, I'll make sure they get applied eventually, but for now will disable softpin from mesa so that 32bit 18.04.2 image will work on gen8+
closing again, thanks!
FWIW, I am not able to reproduce this issue on Arch Linux with Mesa 18.3.3 and kernel 4.18.16.
Hello Alkis, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in mesa (Ubuntu Bionic): | |
status: | New → Fix Committed |
tags: | added: verification-needed verification-needed-bionic |
Changed in mesa (Ubuntu Cosmic): | |
status: | New → Fix Committed |
tags: | added: verification-needed-cosmic |
Adam Conrad (adconrad) wrote : | #11 |
Hello Alkis, or anyone else affected,
Accepted mesa into cosmic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
tags: | added: bjf-tracking |
I verify that the bionic-proposed package addresses the issue.
Tested in:
# lspci -nn -k | grep -A 2 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev 04)
Subsystem: Gigabyte Technology Co., Ltd HD Graphics 630 [1458:d000]
Kernel driver in use: i915
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Launchpad Janitor (janitor) wrote : | #13 |
This bug was fixed in the package mesa - 18.2.2-
---------------
mesa (18.2.2-
* i965-revert-
issues on 32bit installs. (LP: #1815172)
-- Timo Aaltonen <email address hidden> Fri, 08 Feb 2019 19:12:58 +0200
Changed in mesa (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
Adam Conrad (adconrad) wrote : Update Released | #14 |
The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
Changed in mesa: | |
status: | Confirmed → Fix Released |
Hello Alkis, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in mesa (Ubuntu Bionic): | |
status: | Fix Released → Fix Committed |
tags: |
added: verification-needed-bionic removed: verification-done-bionic |
Just correcting a wrong comment (#2) I made:
> It happens on both 32bit and 64bit installations.
I asked the school that reported the issue on 64bit to check again, and they said they have a 32bit installation after all.
So the problem has only been reported in 32bit installations; I don't know if it happened on 64bit. And btw everything is fixed now, thanks again to all. :)
disco has 4.19.x
Changed in mesa (Ubuntu): | |
status: | New → Invalid |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Released |
Timo Aaltonen (tjaalton) wrote : | #29 |
please test the new mesa on bionic/cosmic
Changed in mesa (Ubuntu): | |
status: | Invalid → Fix Released |
Changed in mesa (Ubuntu Cosmic): | |
importance: | Undecided → Medium |
Changed in mesa (Ubuntu Bionic): | |
importance: | Undecided → High |
Changed in mesa (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Bionic): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu Cosmic): | |
importance: | Undecided → Medium |
Timo Aaltonen (tjaalton) wrote : | #30 |
Alkis, please test 18.2.8 for bionic and if possible, cosmic
Changed in linux (Ubuntu Bionic): | |
assignee: | nobody → Timo Aaltonen (tjaalton) |
tags: |
added: verification-done verification-done-bionic verification-done-cosmic removed: verification-needed verification-needed-bionic verification-needed-cosmic |
Timo Aaltonen (tjaalton) wrote : | #31 |
actually, bionic was already tested earlier, and the tested fix is a one-line change to mesa which is still the same on 18.2.8 so marking bionic verified.. and also cosmic since it's the exact same version there, and cosmic kernel was also tested to be buggy
Timo Aaltonen (tjaalton) wrote : | #32 |
bionic was already fixed earlier by 18.2.2-
cosmic got the exact same oneliner in 18.2.8-
Alkis, please correct me if I'm wrong..
description: | updated |
Alkis Georgopoulos (alkisg) wrote : | #33 |
Exactly. I did the "verification-
Thanks a lot Timo!
Launchpad Janitor (janitor) wrote : | #34 |
This bug was fixed in the package mesa - 18.2.8-
---------------
mesa (18.2.8-
* Backport to bionic.
mesa (18.2.8-
* i965-revert-
issues on 32bit installs. (LP: #1815172)
mesa (18.2.8-
* Backport to bionic.
* intel-whl-
mesa (18.2.8-
* 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 <email address hidden> Sat, 09 Feb 2019 00:02:44 +0200
Changed in mesa (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
Launchpad Janitor (janitor) wrote : | #35 |
This bug was fixed in the package mesa - 18.2.8-
---------------
mesa (18.2.8-
* i965-revert-
issues on 32bit installs. (LP: #1815172)
mesa (18.2.8-
* 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 <email address hidden> Fri, 08 Feb 2019 19:12:58 +0200
Changed in mesa (Ubuntu Cosmic): | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu Cosmic): | |
status: | New → Won't Fix |
summary: |
- Black screen on skylake after 18.0 => 18.2 update + [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa |
Timo Aaltonen (tjaalton) wrote : | #36 |
Reopening mesa for bionic, because the revert needs to be dropped once the kernel is fixed, otherwise Ice Lake is broken because it needs softpin for the DRI driver to work.
Changed in mesa (Ubuntu Bionic): | |
status: | Fix Released → In Progress |
Timo Aaltonen (tjaalton) wrote : | #37 |
could you please test with ppa:canonical-
apparently I don't have hw which can install 32bit ubuntu and reproduce this
Timo Aaltonen (tjaalton) wrote : | #38 |
Nevermind, I used a thinkpad t470s plus an external ssd which I could wipe out and install ubuntu mate 18.04 32bit on it. To reproduce I enabled the HWE ppa and upgraded mesa, then installed linux-generic and booted 4.15.0-55. It ended up with a mostly blank screen but keyboard had no effect other than the power button.
Then I installed 'linux-
Changed in linux (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in mesa (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in mesa (Ubuntu Bionic): | |
status: | Fix Committed → In Progress |
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/
tags: | added: verification-needed-xenial |
Hello Alkis, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be available at https:/
Please help us by testing this new package. See https:/
If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-
Further information regarding the verification process can be found at https:/
N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.
Changed in mesa (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-needed verification-needed-bionic removed: verification-done verification-done-bionic |
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (mesa/19.0.8-0ubuntu0~18.04.2) | #41 |
All autopkgtests for the newly accepted mesa (19.0.8-
The following regressions have been reported in tests triggered by the package:
vtk6/unknown (armhf)
kf5-messagelib/
firefox/
openjdk-
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUp
https:/
[1] https:/
Thank you!
Launchpad Janitor (janitor) wrote : | #42 |
This bug was fixed in the package linux - 4.15.0-60.67
---------------
linux (4.15.0-60.67) bionic; urgency=medium
* bionic/linux: 4.15.0-60.67 -proposed tracker (LP: #1841086)
* [Regression] net test from ubuntu_
compilation issue (LP: #1840935)
- SAUCE: Fix "bpf: relax verifier restriction on BPF_MOV | BPF_ALU"
* [Regression] failed to compile seccomp test from ubuntu_
(LP: #1840932)
- Revert "selftests: skip seccomp get_metadata test if not real root"
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
linux (4.15.0-59.66) bionic; urgency=medium
* bionic/linux: 4.15.0-59.66 -proposed tracker (LP: #1840006)
* zfs not completely removed from bionic tree (LP: #1840051)
- SAUCE: (noup) remove completely the zfs code
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* [18.04 FEAT] Enhanced hardware support (LP: #1836857)
- s390: report new CPU capabilities
- s390: add alignment hints to vector load and store
* [18.04 FEAT] Enhanced CPU-MF hardware counters - kernel part (LP: #1836860)
- s390/cpum_cf: Add support for CPU-MF SVN 6
- s390/cpumf: Add extended counter set definitions for model 8561 and 8562
* ideapad_laptop disables WiFi/BT radios on Lenovo Y540 (LP: #1837136)
- platform/x86: ideapad-laptop: Remove no_hw_rfkill_list
* Stacked onexec transitions fail when under NO NEW PRIVS restrictions
(LP: #1839037)
- SAUCE: apparmor: fix nnp subset check failure when, stacking
* bcache: bch_allocator_
timeout for bcache removal causes spurious failures (LP: #1796292)
- SAUCE: bcache: fix deadlock in bcache_allocator
* bcache: bch_allocator_
- bcache: never writeback a discard operation
- bcache: improve bcache_reboot()
- bcache: fix writeback target calc on large devices
- bcache: add journal statistic
- bcache: fix high CPU occupancy during journal
- bcache: use pr_info() to inform duplicated CACHE_SET_
- bcache: fix incorrect sysfs output value of strip size
- bcache: fix error return value in memory shrink
- bcache: fix using of loop variable in memory shrink
- bcache: Fix indentation
- bcache: Add __printf annotation to __bch_check_keys()
- bcache: Annotate switch fall-through
- bcache: Fix kernel-doc warnings
- bcache: Remove an unused variable
- bcache: Suppress more warnings about set-but-not-used variables
- bcache: Reduce the number of sparse complaints about lock imbalances
- bcache: Fix a compiler warning in bcache_
- bcache: Move couple of string arrays to sysfs.c
- bcache: Move couple of functions to sysfs.c
- bcache: Replace bch_read_
* linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
(LP: #1838115)
- x86/mm: Check for pfn instead of page in vmalloc_sync_one()
- x86/mm: Sync also unmappings in vmalloc_sync_all()
- mm/vmalloc.c: add priority threshold to __purge_
Changed in linux (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
There's a follow up fix for bionic/linux which needs to be applied:
https:/
So I'm going to reset the task.
Changed in linux (Ubuntu Bionic): | |
status: | Fix Released → In Progress |
status: | In Progress → Fix Committed |
Launchpad Janitor (janitor) wrote : | #44 |
This bug was fixed in the package linux - 4.15.0-60.67
---------------
linux (4.15.0-60.67) bionic; urgency=medium
* bionic/linux: 4.15.0-60.67 -proposed tracker (LP: #1841086)
* [Regression] net test from ubuntu_
compilation issue (LP: #1840935)
- SAUCE: Fix "bpf: relax verifier restriction on BPF_MOV | BPF_ALU"
* [Regression] failed to compile seccomp test from ubuntu_
(LP: #1840932)
- Revert "selftests: skip seccomp get_metadata test if not real root"
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
linux (4.15.0-59.66) bionic; urgency=medium
* bionic/linux: 4.15.0-59.66 -proposed tracker (LP: #1840006)
* zfs not completely removed from bionic tree (LP: #1840051)
- SAUCE: (noup) remove completely the zfs code
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* [18.04 FEAT] Enhanced hardware support (LP: #1836857)
- s390: report new CPU capabilities
- s390: add alignment hints to vector load and store
* [18.04 FEAT] Enhanced CPU-MF hardware counters - kernel part (LP: #1836860)
- s390/cpum_cf: Add support for CPU-MF SVN 6
- s390/cpumf: Add extended counter set definitions for model 8561 and 8562
* ideapad_laptop disables WiFi/BT radios on Lenovo Y540 (LP: #1837136)
- platform/x86: ideapad-laptop: Remove no_hw_rfkill_list
* Stacked onexec transitions fail when under NO NEW PRIVS restrictions
(LP: #1839037)
- SAUCE: apparmor: fix nnp subset check failure when, stacking
* bcache: bch_allocator_
timeout for bcache removal causes spurious failures (LP: #1796292)
- SAUCE: bcache: fix deadlock in bcache_allocator
* bcache: bch_allocator_
- bcache: never writeback a discard operation
- bcache: improve bcache_reboot()
- bcache: fix writeback target calc on large devices
- bcache: add journal statistic
- bcache: fix high CPU occupancy during journal
- bcache: use pr_info() to inform duplicated CACHE_SET_
- bcache: fix incorrect sysfs output value of strip size
- bcache: fix error return value in memory shrink
- bcache: fix using of loop variable in memory shrink
- bcache: Fix indentation
- bcache: Add __printf annotation to __bch_check_keys()
- bcache: Annotate switch fall-through
- bcache: Fix kernel-doc warnings
- bcache: Remove an unused variable
- bcache: Suppress more warnings about set-but-not-used variables
- bcache: Reduce the number of sparse complaints about lock imbalances
- bcache: Fix a compiler warning in bcache_
- bcache: Move couple of string arrays to sysfs.c
- bcache: Move couple of functions to sysfs.c
- bcache: Replace bch_read_
* linux hwe i386 kernel 5.0.0-21.22~18.04.1 crashes on Lenovo x220
(LP: #1838115)
- x86/mm: Check for pfn instead of page in vmalloc_sync_one()
- x86/mm: Sync also unmappings in vmalloc_sync_all()
- mm/vmalloc.c: add priority threshold to __purge_
Changed in linux (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
Changed in linux (Ubuntu Bionic): | |
status: | Fix Released → Fix Committed |
Timo Aaltonen (tjaalton) wrote : | #45 |
Alkis, could you double-check if your setup is fine now with the current 4.15 kernel and mesa from proposed? Mine is, but I'd rather not rely on that test alone.
Alkis Georgopoulos (alkisg) wrote : | #46 |
Hi Timo,
if I remember correctly, there were some schools that were affected by this issue, but I wasn't able to reproduce it in the office due to lack of similar hardware.
Unfortunately it's not easy to check which were those schools; but I can keep an eye on this issue, in case I hear about black screens in the near future....
Timo Aaltonen (tjaalton) wrote : | #47 |
I asked another user to test this on a duplicate bug (from a newer mesa backport, where the original revert was missing), and it's indeed fixed now
https:/
tags: |
added: verification-done verification-done-bionic removed: verification-needed verification-needed-bionic verification-needed-xenial |
Launchpad Janitor (janitor) wrote : | #48 |
This bug was fixed in the package mesa - 19.0.8-
---------------
mesa (19.0.8-
* i965-revert-
broke Ice Lake which needs softpin. (LP: #1815172)
* rules: Force -DNDEBUG, meson < 0.47 is buggy and doesn't set it even
if we have b_ndebug=true. (LP: #1841412)
-- Timo Aaltonen <email address hidden> Tue, 27 Aug 2019 09:42:44 +0300
Changed in mesa (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
Launchpad Janitor (janitor) wrote : | #49 |
This bug was fixed in the package linux - 4.15.0-65.74
---------------
linux (4.15.0-65.74) bionic; urgency=medium
* bionic/linux: 4.15.0-65.74 -proposed tracker (LP: #1844403)
* arm64: large modules fail to load (LP: #1841109)
- arm64/kernel: kaslr: reduce module randomization range to 4 GB
- arm64/kernel: don't ban ADRP to work around Cortex-A53 erratum #843419
- arm64: fix undefined reference to 'printk'
- arm64/kernel: rename module_
- [config] Remove CONFIG_
* CVE-2018-20976
- xfs: clear sb->s_fs_info on mount failure
* br_netfilter: namespace sysctl operations (LP: #1836910)
- net: bridge: add bitfield for options and convert vlan opts
- net: bridge: convert nf call options to bits
- netfilter: bridge: port sysctls to use brnf_net
- netfilter: bridge: namespace bridge netfilter sysctls
- netfilter: bridge: prevent UAF in brnf_exit_net()
* tuntap: correctly set SOCKWQ_
- tuntap: correctly set SOCKWQ_
* Bionic update: upstream stable patchset 2019-08-30 (LP: #1842114)
- HID: Add 044f:b320 ThrustMaster, Inc. 2 in 1 DT
- MIPS: kernel: only use i8253 clocksource with periodic clockevent
- mips: fix cacheinfo
- netfilter: ebtables: fix a memory leak bug in compat
- ASoC: dapm: Fix handling of custom_
- bonding: Force slave speed check after link state recovery for 802.3ad
- can: dev: call netif_carrier_off() in register_candev()
- ASoC: Fail card instantiation if DAI format setup fails
- st21nfca_
- st_nci_
- ASoC: ti: davinci-mcasp: Correct slot_width posed constraint
- net: usb: qmi_wwan: Add the BroadMobi BM818 card
- qed: RDMA - Fix the hw_ver returned in device attributes
- isdn: mISDN: hfcsusb: Fix possible null-pointer dereferences in
start_
- netfilter: ipset: Fix rename concurrency with listing
- isdn: hfcsusb: Fix mISDN driver crash caused by transfer buffer on the stack
- perf bench numa: Fix cpu0 binding
- can: sja1000: force the string buffer NULL-terminated
- can: peak_usb: force the string buffer NULL-terminated
- net/ethernet/
- NFSv4: Fix a potential sleep while atomic in nfs4_do_reclaim()
- HID: input: fix a4tech horizontal wheel custom usage
- SMB3: Kernel oops mounting a encryptData share with CONFIG_
- net: cxgb3_main: Fix a resource leak in a error path in 'init_one()'
- net: hisilicon: make hip04_tx_reclaim non-reentrant
- net: hisilicon: fix hip04-xmit never return TX_BUSY
- net: hisilicon: Fix dma_map_single failed on arm64
- libata: have ata_scsi_rw_xlat() fail invalid passthrough requests
- libata: add SG safety checks in SFF pio transfers
- x86/lib/cpu: Address missing prototypes warning
- drm/vmwgfx: fix memory leak when too many retries have occurred
- perf ftrace: Fix failure to set cpuma...
Changed in linux (Ubuntu Bionic): | |
status: | Fix Committed → Fix Released |
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: /termbin. com/6l2b /termbin. com/ip4e
* systemctl --failed says "gpu-manager" and "lightdm" have failed
* Xorg.log is clean: https:/
* dmesg too: https:/
* 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