From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Jani Nikula <jani.nikula@linux.intel.com>, sonika.jindal@intel.com
Cc: shashank.sharma@intel.com, rodrigo.vivi@intel.com,
Daniel Vetter <daniel.vetter@ffwll.ch>,
David Airlie <airlied@linux.ie>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [4.4-rc1][Regression] drm/i915: Check live status before reading edid
Date: Wed, 2 Mar 2016 16:58:32 -0500 [thread overview]
Message-ID: <56D76208.7020702@canonical.com> (raw)
In-Reply-To: <87lh63uago.fsf@intel.com>
On 02/29/2016 04:33 AM, Jani Nikula wrote:
> On Wed, 24 Feb 2016, Joseph Salisbury <joseph.salisbury@canonical.com> wrote:
>> 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 for the info. I will have all of these commits tested.
> There are at least the following commits claiming to fix issues in the
> above commit. Please make sure you have them.
>
> BR,
> Jani.
>
>
> commit 8d409cb3e8a24196be7271defafd4638f3e0b514
> Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Date: Wed Feb 10 19:59:05 2016 +0200
>
> drm/i915: Fix hpd live status bits for g4x
>
> commit 3d8acd1f667b45c531401c8f0c2033072e32a05d
> Author: Gary Wang <gary.c.wang@intel.com>
> Date: Wed Dec 23 16:11:35 2015 +0800
>
> drm/i915: increase the tries for HDMI hotplug live status checking
>
> commit 97f9010af05c15e0b7e6b4ef6ff8cb0ebb7e7715
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date: Fri Dec 11 19:44:15 2015 +0100
>
> drm/i915: mdelay(10) considered harmful
>
> commit 0f5a9be15797f78c9a34e432f26c796165b6e49a
> Author: Imre Deak <imre.deak@intel.com>
> Date: Fri Nov 27 18:55:29 2015 +0200
>
> drm/i915: take a power domain reference while checking the HDMI live status
>
>
>
>
next prev parent reply other threads:[~2016-03-02 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 21:38 [4.4-rc1][Regression] drm/i915: Check live status before reading edid Joseph Salisbury
2016-02-25 3:53 ` 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 [this message]
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=56D76208.7020702@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=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=shashank.sharma@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;
as well as URLs for NNTP newsgroup(s).