Bug 91348 - [regression] system fail to boot on kernel 4.2.0-rc2
Summary: [regression] system fail to boot on kernel 4.2.0-rc2
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium blocker
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-15 14:24 UTC by Olivier Berthier
Modified: 2017-07-24 22:46 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features:

Attachments
kernel.log (212.52 KB, text/plain)
2015-07-15 14:24 UTC, Olivier Berthier 		no flags Details
dmesg log (342.92 KB, text/plain)
2015-07-15 14:24 UTC, Olivier Berthier 		no flags Details
View All

Description Olivier Berthier 2015-07-15 14:24:09 UTC 
Created attachment 117137 [details]
kernel.log

Setup:
-------

Hardware
Platform: SKY LAKE Y A0 
CPU : Intel(R) Core(TM) m5-6Y57 CPU @ 1.10GHz (family: 6, model: 78  stepping: 3)
MCP : SKL-Y  D1 2+2 (ou ULX-D1)
QDF : QJK9 
CPU : SKL D0
Chipset PCH: Sunrise Point LP C1       
CRB : SKY LAKE Y LPDDR3 RVP3 CRB FAB2
Reworks : All Mandatories + FBS02,FBS03, F23, O-02 & O-06

Software 
BIOS : SKLSE2R1.R00.X090.B01.1506290657
ME FW : 11.0.0.1158
Ksc (EC FW): 1.15
Linux : Ubuntu 14.04 LTS 64 bits
Kernel : 4.2.0-rc2 drm-intel-nightly: 2015y-07m-15d-12h-31m-14 ( 03c13f4a1010ef1806396b02a0a810cf594fc5eb )

Actual result:
---------------
The system fail to load i915 module and crash.

Expected result:
----------------
No crash.
Comment 1 Olivier Berthier 2015-07-15 14:24:57 UTC 
Created attachment 117138 [details]
dmesg log
Comment 2 cprigent 2015-07-16 10:03:45 UTC 
We tried the following boot option: i915.edp_vswing=2 and i915.edp_vswing=1. It does not solved the problem.
Comment 3 Olivier Berthier 2015-07-17 08:23:34 UTC 
The problem no longer occurs with the commit 984a26bf807c8cae3764e63fadcce74299c2555c on drm-intel-nightly

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.