From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752723AbcBKIUn (ORCPT ); Thu, 11 Feb 2016 03:20:43 -0500 Received: from mail-wm0-f41.google.com ([74.125.82.41]:37420 "EHLO mail-wm0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750905AbcBKIUm (ORCPT ); Thu, 11 Feb 2016 03:20:42 -0500 Date: Thu, 11 Feb 2016 09:21:05 +0100 From: Daniel Vetter To: Oleksandr Natalenko Cc: Daniel Vetter , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Daniel Vetter , Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Subject: Re: [REGRESSION] i915: No HDMI output with 4.4 Message-ID: <20160211082105.GC11240@phenom.ffwll.local> Mail-Followup-To: Oleksandr Natalenko , Daniel Vetter , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, Ville =?iso-8859-1?Q?Syrj=E4l=E4?= References: <7a014cef15d5c99ef7ff33f11968d02c@natalenko.name> <20160209101136.GR11240@phenom.ffwll.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: Linux phenom 4.3.0-1-amd64 User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 11, 2016 at 09:45:17AM +0200, Oleksandr Natalenko wrote: > Daniel, > > I do confirm that this hacky patch: > > https://lkml.org/lkml/2016/1/19/637 > > works around my issue. I understand that this is improper fix, so let me > know how could I debug my issue further. 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. Thanks, Daniel > > Thanks. > > 09.02.2016 12:11, Daniel Vetter wrote: > >Can you please retest with latest -rc? There's been some bugs in the HDMI > >detection changes, which should be fixed now. > > > >If that doesn't help please try to bisect which exact change caused the > >regression. > > > >Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch