From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: dann frazier <dannf@dannf.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>, intel-gfx@lists.freedesktop.org
Subject: Re: regression bisected: display sync drops after 7221fc33
Date: Tue, 26 Jan 2016 13:17:01 +0200 [thread overview]
Message-ID: <20160126111701.GW23290@intel.com> (raw)
In-Reply-To: <20160125163526.GA3389@fluid.dannf>
On Mon, Jan 25, 2016 at 09:35:26AM -0700, dann frazier wrote:
> I've got a Lenovo T410 w/ an external display (DisplayPort<->HDMI). After
> upgrading from a 4.2 kernel to a 4.3, I started hitting an issue where
> the display thinks it has lost input for a few moments. Oddly, it
> usually happens when I start typing in a terminal after a short period
> of inactivity.
>
> I see no OS-side symptoms - there are no new messages in dmesg/syslog/Xorg
> log, etc.
Any fifo underrun reports in dmesg in general?
> I reproduced with latest Linus master (@ 3e1e21c7b), and then
> bisected down to the following commit:
>
> commit 7221fc333dbe1743a3dff155b03527fda90d4ec1
> Author: Matt Roper <matthew.d.roper@intel.com>
> Date: Thu Sep 24 15:53:08 2015 -0700
>
> drm/i915: Eliminate usage of pipe_wm_parameters from ILK-style WM (v2)
That's not in 4.3.
As far as currentl Linus tree goes, you may want to try these:
http://patchwork.freedesktop.org/patch/msgid/1452776015-22076-2-git-send-email-ville.syrjala@linux.intel.com
http://patchwork.freedesktop.org/patch/msgid/1452776015-22076-1-git-send-email-ville.syrjala@linux.intel.com
--
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:[~2016-01-26 11:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 16:35 regression bisected: display sync drops after 7221fc33 dann frazier
2016-01-26 11:17 ` Ville Syrjälä [this message]
2016-01-26 15:10 ` dann frazier
2016-01-26 16:40 ` dann frazier
2016-02-02 22:21 ` dann frazier
2016-02-02 22:51 ` Matt Roper
2016-02-03 0:35 ` dann frazier
2016-02-03 2:04 ` Matt Roper
2016-02-04 2:44 ` dann frazier
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=20160126111701.GW23290@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dannf@dannf.org \
--cc=intel-gfx@lists.freedesktop.org \
/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.