public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: Jani Nikula <jani.nikula@linux.intel.com>, 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>,
	LaMont Jones <lamont.jones@canonical.com>,
	rodrigo.vivi@intel.com
Subject: Re: [4.4-rc1][Regression] drm/i915: Check live status before reading edid
Date: Mon, 18 Apr 2016 15:46:59 -0400	[thread overview]
Message-ID: <571539B3.6060307@canonical.com> (raw)
In-Reply-To: <56F97A65.3010608@canonical.com>

On 03/28/2016 02:39 PM, Joseph Salisbury wrote:
> On 03/02/2016 04:58 PM, Joseph Salisbury wrote:
>> 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
>>>
>>>
>>>
>>>
> Hi Jani,
>
> Applying the following commit did indeed fix the original bug[0]:
>
> 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
>
>
>
> However, it also introduced a new bug, which is covered in that bug
> report.  The new bug is that after locking/unlocking the screen, all the
> windows get shuffled around in a manner that is consistent with X
> deciding that it's single-headed again, and then back to double headed. 
> This only happens when I build a kernel with both commit 237ed86c AND
> commit 8d409cb3e.  If I revert 237ed86c and keep only 8d409cb3e both the
> original bug and the new bug go away.  Do you think commit 237ed86c is
> still even needed now that 8d409cb3e has landed?  Maybe the new bug is
> due to the interaction between 237ed86c and 8d409cb3e.
>
> Thanks,
>
> Joe
>
> [0] http://pad.lv/1543683
>
>
>
>
>
Hello,

Is there any addition debug data we can collect to debug the new bug
that commit 8d409cb3e introduced?

Thanks,

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

      reply	other threads:[~2016-04-18 19:46 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
2016-03-28 18:39     ` Joseph Salisbury
2016-04-18 19:46       ` Joseph Salisbury [this message]

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=571539B3.6060307@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=lamont.jones@canonical.com \
    --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