From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751727AbcGOQgx (ORCPT ); Fri, 15 Jul 2016 12:36:53 -0400 Received: from mga09.intel.com ([134.134.136.24]:2971 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751380AbcGOQgv (ORCPT ); Fri, 15 Jul 2016 12:36:51 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,368,1464678000"; d="scan'208";a="847022482" From: "Bish, Jim" To: "ville.syrjala@linux.intel.com" , "Larry.Finger@lwfinger.net" , "daniel.vetter@ffwll.ch" CC: "torvalds@linux-foundation.org" , "intel-gfx@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , "Shrivastava, Shubhangi" Subject: Re: [Intel-gfx] Critical regression in 4.7-rcX Thread-Topic: [Intel-gfx] Critical regression in 4.7-rcX Thread-Index: AQHR3mYF+7qo9DDaiECJkuCTSjGuFqAaApKAgAAEfACAAA41gIAAEVyA Date: Fri, 15 Jul 2016 16:36:48 +0000 Message-ID: <1468600589.8910.6.camel@intel.com> References: <4f3efccf-5d73-d69f-5d79-2107537a8815@lwfinger.net> <20160715144330.GI4329@intel.com> <9d76da4f-6b5b-9bfc-e3c5-475422696a5f@lwfinger.net> In-Reply-To: <9d76da4f-6b5b-9bfc-e3c5-475422696a5f@lwfinger.net> Reply-To: "Bish, Jim" Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.19.168.11] Content-Type: text/plain; charset="utf-8" Content-ID: <385FCA7CCDDB2946BC744A63AE9A7E15@intel.com> MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u6FGavFU019409 On Fri, 2016-07-15 at 10:34 -0500, Larry Finger wrote: > On 07/15/2016 09:43 AM, Ville Syrjälä wrote: > > > > On Fri, Jul 15, 2016 at 04:27:27PM +0200, Daniel Vetter wrote: > > > > > > On Fri, Jul 15, 2016 at 8:55 AM, Linus Torvalds > > > wrote: > > > > > > > > On Thu, 14 Jul 2016, Larry Finger wrote: > > > > > > > > > > To anyone keeping track of regressions in kernel 4.7, I call > > > > > your attention to > > > > > https://bugs.freedesktop.org/show_bug.cgi?id=96675. > > > > > > > > > > This bug causes driver i915 to fail to connect to the > > > > > display, and results in > > > > > a blank screen as soon as the kernel is loaded. The only way > > > > > to operate with > > > > > kernel 4.7 is to add "nomodeset" to the command line. The > > > > > problem was bisected > > > > > to commit f21a21983ef13a ("drm/i915: Splitting > > > > > intel_dp_detect"). > > > > Daniel? Jani? Time to revert? > > > Yup. Means that I'll get to revert a pile of patches (plus even > > > more > > > in -next), but that's what we get for not handling regressions > > > timely. > > > Dave poked me about the same bug already too. But will take a few > > > days > > > until the pull is in your inbox I guess. > > I attached a oneliner to the bug today, that I *think* should fix > > the > > problem. > After I checked out the problem commit and built that kernel with the > one-line  > patch, the display works; however, mainline still fails. I am > currently  > bisecting to find what other commit fails. At a minimum, we should be > able to  > reduce the number of commits that need reverting. > > Larry I was seeing the same issue Linus reported but very sporadically.  Assumed it was due to my wierd configuration - eDP + usb type c -> MST hub -> DVI KVM -> dual head HDMI.  Checked out the one liner - works for me but I guess there are still other failures. Jim > > > > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx