Created attachment 127994 [details] crash We were facing some problems with Ubuntu 16.10, i think that the problem is related to Unity since i was having some crashes pointing to the hud-service. I tried on different platforms facing same behavior but showing different messages. Fresh installation, Ubuntu 16.10, upgraded. Flickering: xscreensaver 1920x1080. Games: open arena and extremetuxracer crashes We are pointing to Unity since 16.10 introduces some changes. Configuration (example): Software information ============================================ Kernel version : 4.8.0-27-generic Linux distribution : Ubuntu 16.10 Architecture : 64-bit Kernel driver in use : i915 Bios revision : 144.10 Bios release date : 06/27/2016 KSC revision : 1.6 Hardware information ============================================ Platform : BXT-P Motherboard model : BroxtonP Motherboard type : NOTEBOOK Hand Held Motherboard manufacturer : IntelCorp. CPU family : Other CPU information : 06/5c GPU Card : Intel Corporation Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Integrated Graphics Controller (rev 0a) (prog-if 00 [VGA controller]) Memory ram : 16 GB Maximum memory ram allowed : 16 GB CPU thread : 4 CPU core : 4 Socket : Other Hard drive capacity : 55GiB (60GB) Firmwares information ============================================ DMC fw loaded : yes DMC version : 1.7 Attaching Crashes and Dmesg
Created attachment 127995 [details] Dmesg
Created attachment 127996 [details] apport
The way to reproduce this behavior is simple: 1. Login with your user and password. 2. Execute xscreensaver, openarena or extremetuxracer All of these programs should run smoothly without flickering or issues. Actual behavior: xscreensaver shows a lot of flickering not matter if we try with other resolutions or frequency. Mentioned game just crash , open arena shows segmentation fault and extreme tuxracer only goes over last video layer not showing actual game.
The problem persists with following configuration over BDW ubuntu 64 and 32bits configuration for 64bits xf86-video-intel : xorg-x11-drv-intel-2.99.917-24.20160712.fc24.x86_64 mesa : mesa-libgbm-12.0.3-2.fc24.x86_64 cairo : cairo-1.15.2-24.intel20162 drm : libdrm-2.4.71-2.fc24.x86_64 libva : libva-intel-driver:x86_64 (1.7.2-24.intel20162) configuration for 32bits xf86-video-intel : xorg-x11-drv-intel-2.99.917-24.20160712.fc24.i686 mesa : mesa-libgbm-12.0.3-2.fc24.i686 cairo : cairo-1.15.2-24.intel20162.i686 drm : libdrm-2.4.71-2.fc24.i686 libva : libva-intel-driver 1.7.2-24.intel20162.i686
the issue still occurs with the following configuration on SKL ====================================== Software ====================================== kernel version : 4.8.0-34-generic architecture : x86_64 os version : Ubuntu 16.10 os codename : yakkety kernel driver : i915 bios revision : 5.6 bios release date : 09/29/2016 ====================================== Graphic drivers ====================================== mesa : 12.0.3 xorg-xserver : 1.18.4 libva : 1.7.3-2 vaapi (intel-driver) : 1.7.3 intel-gpu-tools : 1.16-1 xserver-xorg-video-intel :2:2.99.917-git20160706
This component is (was) for tracking the release process itself; this bug is not about that.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.