From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: "Jindal, Sonika" <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>,
"oleksandr@natalenko.name" <oleksandr@natalenko.name>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [4.4-rc1][Regression] drm/i915: Check live status before reading edid
Date: Thu, 25 Feb 2016 13:41:44 -0500 [thread overview]
Message-ID: <56CF4AE8.6020706@canonical.com> (raw)
In-Reply-To: <000C66961D35964B9714611E548C10AD0C3FF620@BGSMSX104.gar.corp.intel.com>
On 02/24/2016 10:53 PM, Jindal, Sonika wrote:
> Hi Joe,
>
> Yes, first thing to try is to increase the tries.
We testing with 300 retries, but the second monitor still did not show
up. However, it did show up in lspci.
> Can you please point me to the bug and provide more details like platform, monitor, cable.
The bug is at: http://pad.lv/1543683 . All the hardware details should
be in the bug report. The cable is a single link dvi-d cable.
Unfortunately the bug reporter does not have a dual link cable to test.
If you need any additional info, we can ask the bug reporter.
> Are you referring to the same issue as Oleksandr reported where a single link dvi/hdmi cable didn’t work and dual link worked?
I'm not sure if this is the exact issue or not. I'll review the other
thread and compare.
>
> Regards,
> Sonika
>
> -----Original Message-----
> From: Joseph Salisbury [mailto:joseph.salisbury@canonical.com]
> Sent: Thursday, February 25, 2016 3:09 AM
> To: Jindal, Sonika <sonika.jindal@intel.com>
> Cc: Sharma, Shashank <shashank.sharma@intel.com>; Vivi, Rodrigo <rodrigo.vivi@intel.com>; Daniel Vetter <daniel.vetter@ffwll.ch>; Jani Nikula <jani.nikula@linux.intel.com>; 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: [4.4-rc1][Regression] drm/i915: Check live status before reading edid
>
> 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
next prev parent reply other threads:[~2016-02-25 18:41 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 [this message]
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=56CF4AE8.6020706@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=oleksandr@natalenko.name \
--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