From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Nick Bowler <nbowler@draconx.ca>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: PROBLEM: Intel VGA output busticated on 4.3-rc2 (regression)
Date: Wed, 7 Oct 2015 14:58:50 +0300 [thread overview]
Message-ID: <20151007115850.GE26517@intel.com> (raw)
In-Reply-To: <CAN_QmVxmuEgW+mCZorkemW8nq+KjT7kuSZA=oMZ=5Ts9jO3jvg@mail.gmail.com>
On Tue, Oct 06, 2015 at 11:42:33AM -0400, Nick Bowler wrote:
> Hi,
>
> This issue is still present in 4.3-rc4.
>
> On 9/24/15, Nick Bowler <nbowler@draconx.ca> wrote:
> > Testing out 4.3-rc2, first thing I notice is that the VGA output is
> > not working. Specifically, the display is continuously powering on
> > and off -- at no point is any image visible on the screen (I am expecting
> > to see the console output). The display connected to the HDMI output is
> > working fine.
> >
> > Linux 4.2 did not suffer from this problem.
> >
> > In dmesg I see the following messages, which I do not see on a working
> > kernel. Full dmesg from 4.3-rc2 is attached (gzipped).
> >
> > [ 0.115339] [drm:drm_calc_timestamping_constants] *ERROR* crtc
> > 21: Can't calculate constants, dotclock = 0!
> > [ 0.117582] [drm:intel_opregion_init] *ERROR* No ACPI video bus found
> >
> > This is an older machine with Intel G45 graphics.
>
> I was able to identify the commit which fixed my boot crashes, so I
> cherry-picked 80aa93128653 ("drm/i915: disable_shared_pll doesn't
> work on pre-gen5") on top of all otherwise untestable commits. This
> allowed bisection to proceed:
>
> b8afb9113c519a8bd742f7df8c424b0af69a75cd is the first bad commit
> commit b8afb9113c519a8bd742f7df8c424b0af69a75cd
> Author: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Date: Mon Jun 29 15:25:48 2015 +0300
>
> drm/i915: Keep GMCH DPLL VGA mode always disabled
>
> We disable the DPLL VGA mode when enabling the DPLL, but we enaable it
> again when disabling the DPLL. Having VGA mode enabled even in unused
> DPLLs can cause problems for CHV, so it seems wiser to always keep it
> disabled. And let's just do that on all GMCH platforms to keep things
> as similar as possible between them.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Reviewed-by: Sivakumar Thulasimani <sivakumar.thulasimani@intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> :040000 040000 7797d596e73ecf75723375028decd25fbe332ee0
> 9f90a92eec483919853d68563bbb09a71a305532 M drivers
>
> Unfortunately it does not revert cleanly on master.
@@ -1790,13 +1790,13 @@ static void i9xx_disable_pll(struct intel_crtc *crtc)
/* Make sure the pipe isn't still relying on us */
assert_pipe_disabled(dev_priv, pipe);
- I915_WRITE(DPLL(pipe), 0);
+ I915_WRITE(DPLL(pipe), DPLL_VGA_MODE_DIS);
POSTING_READ(DPLL(pipe));
}
That hunk is the only relevant part for your machine. Can you try to revert
just that manually?
But I'm really surprised that would have any effect since we only used
to enable "VGA mode" when the DPLL is off. And when the DPLL is off,
there's nothing on the screen anyway.
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-07 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN_QmVyMaArxYgEcVVsGvsMo7-6ohZr8HmF5VhkkL4i9KOmrhw@mail.gmail.com>
2015-09-25 12:25 ` PROBLEM: Intel VGA output busticated on 4.3-rc2 (regression) Daniel Vetter
[not found] ` <CAN_QmVxmuEgW+mCZorkemW8nq+KjT7kuSZA=oMZ=5Ts9jO3jvg@mail.gmail.com>
2015-10-07 11:58 ` Ville Syrjälä [this message]
2015-10-07 14:29 ` Nick Bowler
2015-10-07 15:32 ` Ville Syrjälä
2015-10-07 15:44 ` Nick Bowler
2015-10-07 15:47 ` Nick Bowler
2015-10-07 18:50 ` Nick Bowler
2015-10-07 19:04 ` Ville Syrjälä
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=20151007115850.GE26517@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbowler@draconx.ca \
/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).