From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [REGRESSION] i915: No HDMI output with 4.4
Date: Thu, 11 Feb 2016 11:26:39 +0200 [thread overview]
Message-ID: <20160211092639.GX23290@intel.com> (raw)
In-Reply-To: <4a6e01cc374f7a120b5baab7b41f1951@natalenko.name>
On Thu, Feb 11, 2016 at 10:54:08AM +0200, Oleksandr Natalenko wrote:
> Daniel,
>
> I've already tried Ville's patch you've mentioned with no luck.
>
> Kindly find unpatched v4.5-rc3 dmesg with drm debug enabled here: [1]
>
> [1] https://gist.github.com/efb44b7c6bc325978b80
That's an IVB. So no wonder my patch doesn't help.
Can you grab another dmesg after disconnecting and reconnecting the
HDMI cable?
>
> 11.02.2016 10:21, Daniel Vetter wrote:
> > Please boot with drm.debug=0xe and attach the dmesg. Also please test
> > the
> > patch later on in this thread:
> >
> > https://lkml.org/lkml/2016/2/9/587
> >
> > Ville is working on a proper fix for this specific case. But could be
> > that
> > you're hitting yet another issue.
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [REGRESSION] i915: No HDMI output with 4.4
Date: Thu, 11 Feb 2016 11:26:39 +0200 [thread overview]
Message-ID: <20160211092639.GX23290@intel.com> (raw)
In-Reply-To: <4a6e01cc374f7a120b5baab7b41f1951@natalenko.name>
On Thu, Feb 11, 2016 at 10:54:08AM +0200, Oleksandr Natalenko wrote:
> Daniel,
>
> I've already tried Ville's patch you've mentioned with no luck.
>
> Kindly find unpatched v4.5-rc3 dmesg with drm debug enabled here: [1]
>
> [1] https://gist.github.com/efb44b7c6bc325978b80
That's an IVB. So no wonder my patch doesn't help.
Can you grab another dmesg after disconnecting and reconnecting the
HDMI cable?
>
> 11.02.2016 10:21, Daniel Vetter wrote:
> > Please boot with drm.debug=0xe and attach the dmesg. Also please test
> > the
> > patch later on in this thread:
> >
> > https://lkml.org/lkml/2016/2/9/587
> >
> > Ville is working on a proper fix for this specific case. But could be
> > that
> > you're hitting yet another issue.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2016-02-11 9:26 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 10:17 [REGRESSION] i915: No HDMI output with 4.4 Oleksandr Natalenko
2016-02-09 10:11 ` Daniel Vetter
2016-02-09 10:11 ` Daniel Vetter
2016-02-09 15:56 ` Oleksandr Natalenko
2016-02-11 7:45 ` Oleksandr Natalenko
2016-02-11 7:45 ` Oleksandr Natalenko
2016-02-11 8:21 ` Daniel Vetter
2016-02-11 8:21 ` Daniel Vetter
2016-02-11 8:54 ` Oleksandr Natalenko
2016-02-11 8:54 ` Oleksandr Natalenko
2016-02-11 9:26 ` Ville Syrjälä [this message]
2016-02-11 9:26 ` Ville Syrjälä
2016-02-11 11:16 ` Oleksandr Natalenko
2016-02-11 11:16 ` Oleksandr Natalenko
2016-02-11 14:01 ` Ville Syrjälä
2016-02-12 7:52 ` Oleksandr Natalenko
2016-02-12 7:52 ` Oleksandr Natalenko
2016-02-12 23:23 ` Ville Syrjälä
2016-02-15 7:57 ` Oleksandr Natalenko
2016-02-15 7:57 ` Oleksandr Natalenko
2016-02-15 8:55 ` Oleksandr Natalenko
2016-02-15 8:55 ` Oleksandr Natalenko
2016-02-15 14:42 ` Ville Syrjälä
2016-02-15 14:42 ` Ville Syrjälä
2016-02-15 15:42 ` Daniel Vetter
2016-02-15 15:42 ` Daniel Vetter
2016-02-16 10:58 ` Oleksandr Natalenko
2016-02-16 10:58 ` Oleksandr Natalenko
2016-02-16 12:54 ` Daniel Vetter
2016-02-16 12:54 ` Daniel Vetter
2016-02-16 13:21 ` Oleksandr Natalenko
2016-02-16 13:21 ` Oleksandr Natalenko
2016-02-16 15:51 ` Oleksandr Natalenko
2016-02-16 15:51 ` Oleksandr Natalenko
2016-02-22 12:32 ` Oleksandr Natalenko
2016-02-22 12:32 ` Oleksandr Natalenko
2016-02-23 15:08 ` Ville Syrjälä
2016-02-23 15:08 ` Ville Syrjälä
2016-02-24 4:40 ` Jindal, Sonika
2016-02-24 4:40 ` Jindal, Sonika
2016-02-24 14:12 ` Oleksandr Natalenko
2016-02-24 14:12 ` Oleksandr Natalenko
2016-02-24 6:07 ` Sharma, Shashank
2016-02-29 15:13 ` Daniel Vetter
2016-02-29 15:13 ` Daniel Vetter
2016-02-29 15:16 ` Sharma, Shashank
2016-02-29 15:16 ` Sharma, Shashank
2016-02-29 15:41 ` Daniel Vetter
2016-02-29 15:41 ` Daniel Vetter
2016-02-29 15:41 ` Sharma, Shashank
2016-02-29 17:01 ` Daniel Vetter
2016-02-29 17:01 ` Daniel Vetter
2016-02-24 14:09 ` Oleksandr Natalenko
2016-02-24 14:09 ` Oleksandr Natalenko
-- strict thread matches above, loose matches on Subject: below --
2016-05-01 10:42 Alessandro Capogna
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=20160211092639.GX23290@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleksandr@natalenko.name \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.