From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Subject: Re: [REGRESSION] i915: No HDMI output with 4.4 Date: Thu, 11 Feb 2016 11:26:39 +0200 Message-ID: <20160211092639.GX23290@intel.com> References: <7a014cef15d5c99ef7ff33f11968d02c@natalenko.name> <20160209101136.GR11240@phenom.ffwll.local> <20160211082105.GC11240@phenom.ffwll.local> <4a6e01cc374f7a120b5baab7b41f1951@natalenko.name> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Content-Disposition: inline In-Reply-To: <4a6e01cc374f7a120b5baab7b41f1951@natalenko.name> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Oleksandr Natalenko Cc: Daniel Vetter , intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Daniel Vetter List-Id: dri-devel@lists.freedesktop.org T24gVGh1LCBGZWIgMTEsIDIwMTYgYXQgMTA6NTQ6MDhBTSArMDIwMCwgT2xla3NhbmRyIE5hdGFs ZW5rbyB3cm90ZToKPiBEYW5pZWwsCj4gCj4gSSd2ZSBhbHJlYWR5IHRyaWVkIFZpbGxlJ3MgcGF0 Y2ggeW91J3ZlIG1lbnRpb25lZCB3aXRoIG5vIGx1Y2suCj4gCj4gS2luZGx5IGZpbmQgdW5wYXRj aGVkIHY0LjUtcmMzIGRtZXNnIHdpdGggZHJtIGRlYnVnIGVuYWJsZWQgaGVyZTogWzFdCj4gCj4g WzFdIGh0dHBzOi8vZ2lzdC5naXRodWIuY29tL2VmYjQ0YjdjNmJjMzI1OTc4YjgwCgpUaGF0J3Mg YW4gSVZCLiBTbyBubyB3b25kZXIgbXkgcGF0Y2ggZG9lc24ndCBoZWxwLgoKQ2FuIHlvdSBncmFi IGFub3RoZXIgZG1lc2cgYWZ0ZXIgZGlzY29ubmVjdGluZyBhbmQgcmVjb25uZWN0aW5nIHRoZQpI RE1JIGNhYmxlPwoKPiAKPiAxMS4wMi4yMDE2IDEwOjIxLCBEYW5pZWwgVmV0dGVyIHdyb3RlOgo+ ID4gUGxlYXNlIGJvb3Qgd2l0aCBkcm0uZGVidWc9MHhlIGFuZCBhdHRhY2ggdGhlIGRtZXNnLiBB bHNvIHBsZWFzZSB0ZXN0IAo+ID4gdGhlCj4gPiBwYXRjaCBsYXRlciBvbiBpbiB0aGlzIHRocmVh ZDoKPiA+IAo+ID4gaHR0cHM6Ly9sa21sLm9yZy9sa21sLzIwMTYvMi85LzU4Nwo+ID4gCj4gPiBW aWxsZSBpcyB3b3JraW5nIG9uIGEgcHJvcGVyIGZpeCBmb3IgdGhpcyBzcGVjaWZpYyBjYXNlLiBC dXQgY291bGQgYmUgCj4gPiB0aGF0Cj4gPiB5b3UncmUgaGl0dGluZyB5ZXQgYW5vdGhlciBpc3N1 ZS4KCi0tIApWaWxsZSBTeXJqw6Rsw6QKSW50ZWwgT1RDCl9fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fCmRyaS1kZXZlbCBtYWlsaW5nIGxpc3QKZHJpLWRldmVs QGxpc3RzLmZyZWVkZXNrdG9wLm9yZwpodHRwczovL2xpc3RzLmZyZWVkZXNrdG9wLm9yZy9tYWls bWFuL2xpc3RpbmZvL2RyaS1kZXZlbAo= From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751687AbcBKJ0q (ORCPT ); Thu, 11 Feb 2016 04:26:46 -0500 Received: from mga14.intel.com ([192.55.52.115]:42881 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751427AbcBKJ0n (ORCPT ); Thu, 11 Feb 2016 04:26:43 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,430,1449561600"; d="scan'208";a="912947031" Date: Thu, 11 Feb 2016 11:26:39 +0200 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= To: Oleksandr Natalenko Cc: Daniel Vetter , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Daniel Vetter Subject: Re: [REGRESSION] i915: No HDMI output with 4.4 Message-ID: <20160211092639.GX23290@intel.com> References: <7a014cef15d5c99ef7ff33f11968d02c@natalenko.name> <20160209101136.GR11240@phenom.ffwll.local> <20160211082105.GC11240@phenom.ffwll.local> <4a6e01cc374f7a120b5baab7b41f1951@natalenko.name> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4a6e01cc374f7a120b5baab7b41f1951@natalenko.name> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 11, 2016 at 10:54:08AM +0200, Oleksandr Natalenko wrote: > Daniel, > > I've already tried Ville's patch you've mentioned with no luck. > > Kindly find unpatched v4.5-rc3 dmesg with drm debug enabled here: [1] > > [1] https://gist.github.com/efb44b7c6bc325978b80 That's an IVB. So no wonder my patch doesn't help. Can you grab another dmesg after disconnecting and reconnecting the HDMI cable? > > 11.02.2016 10:21, Daniel Vetter wrote: > > Please boot with drm.debug=0xe and attach the dmesg. Also please test > > the > > patch later on in this thread: > > > > https://lkml.org/lkml/2016/2/9/587 > > > > Ville is working on a proper fix for this specific case. But could be > > that > > you're hitting yet another issue. -- Ville Syrjälä Intel OTC