intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Meelis Roos <mroos@linux.ee>
Cc: Jani Nikula <jani.nikula@intel.com>,
	dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
	Daniel Vetter <daniel.vetter@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: bisected: i915 modeset broken in ac9b8236551d1177fd07b56aef9b565d1864420d
Date: Mon, 14 Dec 2015 17:08:06 +0200	[thread overview]
Message-ID: <20151214150806.GQ4437@intel.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1512141526430.4425@math.ut.ee>

On Mon, Dec 14, 2015 at 03:31:09PM +0200, Meelis Roos wrote:
> Between 4.4-rc3 and 4.4-rc4, i915 modesetting broke on my i5-2400 PC. 

That would seem to be SNB.

> Instead of seeing the new dense graphics mode, I see the last VGA text 
> lines and no X appears either.

That's a bit weird. SNB has no power power wells, so only runtime PM
could be a factor, but it should not kick in that fast during boot even
if you enable it before loading the driver since we set the delay to 10
seconds.

And in any case the commit you list shouldn't really change anything
for SNB. We used to grab a rpm reference for gmbus via
intel_aux_display_runtime_get() and now we get it via the GMBUS power
domain instead.

I would be more tempted to blame the live status check, except it was
already included in 4.4-rc1 I think. We didn't have a power well
reference for it until
commit 0f5a9be15797 ("drm/i915: take a power domain reference while checking the HDMI live status")
but that's already in v4.4-rc4.

In any case the live status check was already reported to cause failures
(at least on some SNB IIRC). There have been attempts to remedy it since:
http://lists.freedesktop.org/archives/intel-gfx/2015-December/082689.html
http://lists.freedesktop.org/archives/intel-gfx/2015-December/082932.html

So this bisect result is somewhat mysterious. A full dmesg with
drm.debug=0xe with and without the offending patch reverted would be
helpful. And might be best to attach those into a bug report
(https://bugs.freedesktop.org/ -> DRI -> DRM/Intel) so that we don't
lose track of them.

Oh, are we even talking about HDMI/DVI here, or something else?

> 
> I saw something similar on I865G but have not had time to check if it is 
> the same issue.
> 
> ac9b8236551d1177fd07b56aef9b565d1864420d is the first bad commit
> commit ac9b8236551d1177fd07b56aef9b565d1864420d
> Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Date:   Fri Nov 27 18:55:26 2015 +0200
> 
>     drm/i915: Introduce a gmbus power domain
>     
>     Currently the gmbus code uses intel_aux_display_runtime_get/put in an
>     effort to make sure the hardware is powered up sufficiently for gmbus.
>     That function only takes the runtime PM reference which on VLV/CHV/BXT
>     is not enough. We need the disp2d/pipe-a well on VLV/CHV and power well
>     2 on BXT. So add a new power domnain for gmbus and kill off the now
>     unused intel_aux_display_runtime_get/put. And change
>     intel_hdmi_set_edid() to use the gmbus power domain too since that's all
>     we need there.
>     
>     Also toss in a BUILD_BUG_ON() to catch problems if we run out of
>     bits for power domains. We're already really close to the limit...
>     
>     [Patrik: Add gmbus string to debugfs output]
>     
>     Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>     Reviewed-by: Patrik Jakobsson <patrik.jakobsson@linux.intel.com>
>     [Cherry-picked from drm-intel-next-queued f0ab43e6 (Imre)]
>     Signed-off-by: Imre Deak <imre.deak@intel.com>
>     Link: http://patchwork.freedesktop.org/patch/msgid/1448643329-18675-3-git-send-email-imre.deak@intel.com
>     Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> 
> :040000 040000 39379146d7e6dda8a4d5f8781ee3d307cce8c47e f4f09fae0485ad6263d31d425296fa9cd7de343b M     drivers
> 
> 
> -- 
> Meelis Roos (mroos@linux.ee)

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-12-14 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-14 13:31 bisected: i915 modeset broken in ac9b8236551d1177fd07b56aef9b565d1864420d Meelis Roos
2015-12-14 15:08 ` Ville Syrjälä [this message]
2016-01-06 15:41   ` Meelis Roos
2016-01-07  8:52     ` Jani Nikula
2016-01-07 10:30       ` Jani Nikula
2016-01-07 11:10         ` Meelis Roos

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=20151214150806.GQ4437@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=airlied@linux.ie \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=mroos@linux.ee \
    /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).