Launchpad has imported 8 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=109583.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2019-02-08T08:04:22+00:00 Alkis Georgopoulos wrote: 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: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/0 ------------------------------------------------------------------------ On 2019-02-08T08:59:14+00:00 Denys-kostin wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/2 ------------------------------------------------------------------------ On 2019-02-08T09:04:12+00:00 Alkis Georgopoulos wrote: 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://termbin.com/kkix systemctl status lightdm: https://termbin.com/ybev lightdm.log: https://termbin.com/ssrb 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/3 ------------------------------------------------------------------------ On 2019-02-08T09:10:38+00:00 Alkis Georgopoulos wrote: The Ubuntu folks uploaded 18.3.3 in their ppa:ubuntu-x-swat/updates PPA for me to test with, and it has the exact same issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/4 ------------------------------------------------------------------------ On 2019-02-08T09:21:41+00:00 Chris Wilson wrote: Can you please: $ echo 0xf > /sys/modules/drm/parameters/debug $ xinit $ echo 0 > /sys/modules/drm/parameters/debug $ dmesg > dmesg.txt # and upload Hopefully we remembered to tag the EINVAL. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/5 ------------------------------------------------------------------------ On 2019-02-08T09:32:05+00:00 Alkis Georgopoulos wrote: I used "/sys/module" instead of "/sys/modules": $ echo 0xf /sys/module/drm/parameters/debug $ 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/drm/parameters/debug $ dmesg | nc termbin.com 9999 https://termbin.com/fb2m I don't see any additional messages though... Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/6 ------------------------------------------------------------------------ On 2019-02-08T09:33:24+00:00 Alkis Georgopoulos wrote: Sorry, I forgot the > Here's the correct log: https://termbin.com/6n12 Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/7 ------------------------------------------------------------------------ On 2019-02-08T09:48:56+00:00 Chris Wilson wrote: (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_MODE_CREATE_DUMB [ 1494.995493] [drm:drm_ioctl [drm]] pid=2746, dev=0xe200, auth=1, DRM_IOCTL_MODE_CREATE_DUMB [ 1494.995584] [drm:drm_ioctl [drm]] pid=2746, dev=0xe200, auth=1, I915_GEM_EXECBUFFER2_WR [ 1494.995595] [drm:drm_ioctl [drm]] ret = -22 That'll be no then. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172/comments/8 ** Changed in: mesa Status: Unknown => Confirmed ** Changed in: mesa Importance: Unknown => Medium -- 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/1815172 Title: Black screen on skylake after 18.0 => 18.2 update To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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
