Created attachment 124707 [details] kernel.log =Bug detailed description== -------------------------------------------------- Trying to boot using the kernel 4.7.0-rc2 on KBL platform rvp3; unable to boot Configuration within KBL platforms: 1 port HDMI - enable 1 port DP - enable ==Attachments== -------------------------------------------------- kernel.log ==Steps to reproduce== -------------------------------------------------- 1- Tried to boot using the kernel 4.7.2-rc2 on KBL rvp3 with 2 video ports enable ==Actual results== -------------------------------------------------- Unable to boot ==Expected results== -------------------------------------------------- Successful boot Software information ============================================ Kernel version : 4.7.0-rc2-nightly+ Linux distribution : Ubuntu 16.04 LTS Architecture : 64-bit Mesa version : 11.1.2 (git-7bcd827 xf86-video-intel version : 2.99.917 Xorg-Xserver version : 1.18.99.1 DRM version : 2.4.68 VAAPI version : Intel i965 driver for Intel(R) Kabylake - 1.7.2.pre1 (1.7.0-50-gbf387bb) Cairo version : 1.15.2 Intel GPU Tools version : Tag [intel-gpu-tools-1.15-29-gc344044] / Commit [c344044] Kernel driver in use : i915 Hardware acceleration : Enabled Bios revision : 7.0 KSC revision : 1.20 Hardware information ============================================ Platform : KBL (RVP7) Motherboard model : Kabylake Client platform Motherboard type : Skylake U DDR3L RVP7 Laptop Motherboard manufacturer : Intel Corporation CPU family : Other CPU information : Genuine Intel(R) CPU 0000 @ 2.60GHz GPU Card : Intel Corporation Device 5916 (prog-if 00 [VGA controller]) Memory ram : 4 GB Maximum memory ram allowed : 16 GB Display resolution : 3200x1800 CPU's number : 4 Hard drive Capacity : 120 GB Firmwares information ============================================ DMC fw loaded : yes DMC version : 1.1 kernel_version=4.7.0-rc2 git_url=git://anongit.freedesktop.org/drm-intel git_branch=drm-intel-nightly git_tag=undefined git_commit=43b42445cb9fe29b01a52bc5f90b360891511bc3 git_describe=drm-intel-next-2016-06-20-139-g43b4244
Maria, please add drm.debug=14 and attached both kernel and xorg logs. Moreover, on your system, in addition to hdmi & dp, do you have also edp connected & working? thanks
(In reply to yann from comment #1) > Maria, please add drm.debug=14 and attached both kernel and xorg logs. > Moreover, on your system, in addition to hdmi & dp, do you have also edp > connected & working? > thanks Hi Yann, i've tested with latest configuration on KBL RVP7 and this issue is gone with the following configuration , also i have to comment that it was tested with all platform ports availables (eDP + microHDMI + DP) Software information ============================================ Kernel version : 4.8.0-drm-intel-nightly-ww42-commit-fc23e80+ Linux distribution : Ubuntu 16.04.1 LTS Architecture : 64-bit Mesa version : Not found << Please see the message at the bottom >> xf86-video-intel version : 2.99.917 Xorg-Xserver version : 1.18.3 DRM version : 2.4.71 VAAPI version : Not found Cairo version : 1.15.2 Intel GPU Tools version : Tag [intel-gpu-tools-1.16-59-g48a9e1e] / Commit [48a9e1e] Kernel driver in use : i915 Bios revision : 50.2 Bios release date : 08/09/2016 KSC revision : 1.20 Hardware information ============================================ Platform : KBL (RVP7) Motherboard model : Kabylake Client platform Motherboard type : Skylake U DDR3L RVP7 Laptop Motherboard manufacturer : Intel Corporation CPU information : Genuine Intel(R) CPU 0000 @ 2.60GHz GPU Card : Intel Corporation Device 5916 (prog-if 00 [VGA controller]) Memory ram : 4 GB Maximum memory ram allowed : 16 GB CPU thread : 4 CPU core : 2 Socket : Other Hard drive capacity : 447GiB (480GB) Kernel parameters ============================================ quiet drm.debug=14 resume=/dev/sda3 so, i'll proceed to close this issue since that does not happen with latest drm-intel-nightly kernel
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.