From: "Jindal, Sonika" <sonika.jindal@intel.com>
To: Nick Bowler <nbowler@draconx.ca>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>,
shashank.sharma@intel.com
Subject: Re: PROBLEM: Intel HDMI output busticated on 4.4 (regression)
Date: Thu, 21 Jan 2016 16:37:48 +0530 [thread overview]
Message-ID: <56A0BC04.9080500@intel.com> (raw)
In-Reply-To: <CADyTPEx6P+8bd3WKZcxeZ7eLMW0C3nzuD592ysgO_oF0WL4cuw@mail.gmail.com>
On 1/21/2016 8:59 AM, Nick Bowler wrote:
> On 1/20/16, Nick Bowler <nbowler@draconx.ca> wrote:
>> Hi,
>>
>> On 2016-01-20, Jindal, Sonika <sonika.jindal@intel.com> wrote:
>>> Can you please check if you have following patch:
>>> "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"
>> Yes, that patch seems to be present in 4.4.
>>
>>> Does the same system works with any other monitor?
>> I'll see if I can find another to try.
> I tried another monitor, and the same problem occurs.
Which make are these monitors?
Do you have any other system other than G45?
Shashank,
Do you suggest anything else which Nick can try?
next prev parent reply other threads:[~2016-01-21 11:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-19 22:26 PROBLEM: Intel HDMI output busticated on 4.4 (regression) Nick Bowler
2016-01-20 4:30 ` Jindal, Sonika
2016-01-20 15:33 ` Nick Bowler
2016-01-21 3:29 ` Nick Bowler
2016-01-21 11:07 ` Jindal, Sonika [this message]
2016-01-21 13:57 ` Nick Bowler
2016-01-28 6:00 ` Nick Bowler
2016-02-09 16:33 ` Nick Bowler
2016-02-09 16:39 ` Sharma, Shashank
2016-02-09 17:03 ` Ville Syrjälä
2016-02-09 17:36 ` Ville Syrjälä
2016-02-09 18:22 ` Ville Syrjälä
2016-02-10 4:43 ` Sharma, Shashank
2016-02-09 18:02 ` Nick Bowler
2016-02-10 9:00 ` Jani Nikula
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=56A0BC04.9080500@intel.com \
--to=sonika.jindal@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@draconx.ca \
--cc=shashank.sharma@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