public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: sonika.jindal@intel.com
Cc: David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	rodrigo.vivi@intel.com
Subject: [4.4-rc1][Regression] drm/i915: Check live status before reading edid
Date: Wed, 24 Feb 2016 16:38:35 -0500	[thread overview]
Message-ID: <56CE22DB.6050108@canonical.com> (raw)

Hi Sonika,

A kernel bug report was opened against Ubuntu [0].  After a kernel
bisect, it was found that reverting the following commit resolved this bug:

commit 237ed86c693d8a8e4db476976aeb30df4deac74b
Author: Sonika Jindal <sonika.jindal@intel.com>
Date:   Tue Sep 15 09:44:20 2015 +0530

    drm/i915: Check live status before reading edid



The regression was introduced as of v4.4-rc1.

I was hoping to get your feedback, since you are the patch author.  Do
think increasing the number of tries in intel_hdmi_detect() is worth
trying?  Do you think gathering any additional data will help diagnose
this issue, or would it be best to submit a revert request?
    

Thanks,
    
Joe

[0] http://pad.lv/lp1543683

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2016-02-24 21:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-24 21:38 Joseph Salisbury [this message]
2016-02-25  3:53 ` [4.4-rc1][Regression] drm/i915: Check live status before reading edid Jindal, Sonika
2016-02-25 18:41   ` Joseph Salisbury
2016-02-26  6:08     ` Jindal, Sonika
2016-02-29  9:33 ` Jani Nikula
2016-03-02 21:58   ` Joseph Salisbury
2016-03-28 18:39     ` Joseph Salisbury
2016-04-18 19:46       ` Joseph Salisbury

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56CE22DB.6050108@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=sonika.jindal@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox